Problem with RDP

sinizter

Member
Messages
3
Reaction score
0
Points
1
Hello,
Recently I bought RDP for the first time and I have issues with f.vision leaks.
On my main PC I dont have any leaks, only on RDP and I dont know what the problem is.

I changed UserAgent by 911 settings (auto change UA) -> problem still exists
I changed UserAgent by Firefox UserAgent Switcher and Manager -> problem still exists
I changed UserAgent by 911 settings + Firefox UserAgent Switcher and Manager at the same time -> problem still exists

Look for screenshots


photo_2021-07-27_16-14-17.jpg
photo_2021-07-27_16-14-27.jpg



Any ideas what can I do?
 
RDP Guide
The range of actions with this tool is huge, if you want brute, spam, carding - please. In general, for those operations that require a long-term computer turned on and its load, a good plus will also be that you do not fire your computer at the same time. And this is a plus for anonymity.

So, what is it, and what it is eaten with.
This is a type of hosting in which a separate physical machine is provided to the client. They usually have fairly powerful network interfaces and good hardware configuration.

1) How to connect to RDP? Everything is very simple: press "start" "execute", enter the command mstsc. In the window that appears, enter the name of the computer - i.e. given to you ah pi address, then click on additional (or parameters), enter the username, and then click on the connection. The login to the remote desktop will open, where you will need to enter the password and click "ok". Actually, in front of you there will be a server desktop, where you will create.
When connecting, it is advisable to use a VPN connection or a soxifier for example - freecap_setup.exe

2) How to upload software to RDP? Also, there is nothing difficult. If it (software) is on the Internet - then you do everything as on your computer - open the browser and download, if it is on your computer - then first you need to upload it to any file hosting service and then using the received link from the RDP browser - again download it.
You can also connect your local disk to the RDP using the mstsc options.

3) After purchase, we recommend that you change the password to any of your own (this applies to servers from the plate, where there is already a separately created account; you cannot change the granted access on XP, you should create an account for yourself and put a patch for multi-use from the XP page). How do I change my password? On the RDP press "start" "run" cmd. Enter: net user user password and enter.

4) How to create a new user on the RDP? (when buying an admin RDP from a plate on the site, nobody needs to do this, since you are given a ready-to-use account, you can only change the password. If you bought an XP / Win7 RDP System, then the accounting must be done by you).
For example:
Click: "start" "run" write cmd and enter:
Code:
net user sql 1234567 / add
net localgroup Administrators sql / add

In this case, an sql account will be created with the password 1234567

Do not forget that the group of administrators is called Administrators only on English-language Dedicated computers, on other language varieties of Windows - the Administrators group is called differently. The name of the admin group can be found in compmgmt.msc or (if the domain is on the RDP) - dsa.msc

It should be borne in mind that on new versions of Windows Server (for example, 2008), when you create a new account or change the password, you may receive a response from the system about insufficient rights to perform these operations. There is no need to rush to be indignant that you were sold a RDP without admin rights. This is the specificity of the security settings and everything is perfectly solved - you just need to run the command line from the start - through the right mouse button - "run as administrator", after which everything will work. Similarly, you may need to launch your software in the same way, through the right mouse button.

5) what to do if, when connecting, it displays the message: terminal exeeded the maximum connections? In this case, in 99% of cases, the so-called console connection, or connection through a zero session, will help. To do this, in start-run, we type:
mstsc /vternet.0.0.0 / admin and hit ENTER or: mstsc /v 0.0.0.0 / f -console (of course, instead of zeros, type the IP of the RDP);

If your RDP shows after loggin the message: terminal exeeded the maximum connections you can login there by next way:
- go to your "start" button, than choose "run" (or Win + R)
- paste there all this: (as example) mstsc /v:67.1.5.36 / admin
- type the login and password in fields end push Enter

6) When entering the RDP, it is impossible to change the layout to enter the username / password. The solution is as easy as shelling pears: after dialing the IP, we do not press the connection to the RDP, but go to the "additional" option, where we enter the login on the desired layout and just stomp on to the RDP and enter the password (it will be entered on the same layout as the login;

7) it happens that when buying a RDP with limited rights, it occurs when the browser, due to security settings, does not allow anything to download or enable Java, Active-X, etc. There is also a simple way out of this situation. We read and do carefully:
First download the opera portable to your computer: opera-usb.com/operausben.htm, from the off site, for example, you have it yourself, not your grandfather ...
Before connecting to the RDP, go to the connection parameters (mstsc)
There will be a section called local resources, or local disks, or something like that (depending on Windows, it can be called differently), find there the connection of your local disks (all or select one if available) and only then connect to the RDP.
Already on the RDP, open "my computer" and there will be your disk, from it just drag the previously downloaded opera and that's it ... there will be no problems with Java or downloading anything.

8) What does the sign "login to local computer" mean? In this case, when entering the RDP, after entering the password, you need to select another line in the field that is UNDER the password, the one where it says" (this computer)" and after that we already enter the server.

9) Sometimes it happens that after entering the login and password, the server desktop is not shown, because any program will auto-start. This issue is easily solved in the following way - we log into the RDP, after which we press the key combination Ctrl + Alt + End, which will call the task manager (RDP! And not yours), after which we go to the File menu, new task, and type explorer, after which Click OK and the further loading of the RDP interface will go.

10) The clipboard does not work on the RDP, I cannot copy anything to it. First, do the logoff again and log back to the RDP. If it does not help, then we do the following: on the RDP we start "start-run", write the command gpedit.msc.
Click ok, do Logoff from grandfather and go back, check the buffer.

11) After a while I go to the RDP and it seems to have rebooted, a new login is in progress, all programs are closed. If there was no physical reboot of the RDP, then the session is automatically terminated, which can be configured. On the RDP, start "start-run", write the command tscc.msc
Click ok, ok again and do Logoff from RDP and go back, the problem is fixed.

12) what if I see other "left" users in the purchased RDP? you should definitely be sure that these are NOT local users of the grandfather (so to speak, the owners). Secondly, getting rid of unwanted neighbors is pretty easy and with this request you should contact a consultant

13) I can not switch the layout in the RDP to enter the login and password. Like everything else, it is very simple to solve. After entering the IP, go to the connection parameters
We enter the login there without any problems, in the language we need, click to connect to the RDP and, without touching (!!!) the keyboard layout (regardless of what it is signed there, inside the Dedicated Server) - enter the password and log in.

14) How to "work correctly"? The main thing here will be:
  • hide your software deeper in system folders, such as c: / windows / system32;
  • do not create many additional accounts. in addition to what was given to you upon purchase;
  • rename your executables by analogy with system ones, for example svchost.exe;
  • warn antivirus alerts - immediately configure them to work together with your software;
  • do not touch accounts already existing on the server;
  • do not overload the server unless absolutely necessary;
  • avoid heavy load on the processor (up to 50% dangerous maximum);
  • in case of installing programs - make sure that no shortcuts appear on the desktop and in the start menu, or manually delete them from the All users profile;

15) When trying to login to RDP, we see the message No available licenses for the terminal server (Remote session was disconnected because there are no Remote Desktop client access licenses). Treatment: press "start", "execute" on your computer and insert the reg delete "HKLM \ SOFTWARE \ Microsoft \ MSLicensing" / f command there. After that, we connect to the RDP.

16) Well, and the most important question that probably worries buyers - "I bought a deed in automatic mode, but it is inoperative. Force majeure / technical difficulties take place here. After finding the above point, you should write and wait for the caliper to appear.
A very common situation is when Internet Explorer "refuses" to download files from the Internet.
Fortunately, 99.99% of this is easily configurable via the browser properties.
Go to the "security" tab, select the "Internet" icon, click on the "Custom level" button
In the list that appears, we scroll to the items in which permission to download files is set, in fact, we allow it:
Then click OK. we confirm this decision in the window that appears, once again OK and that's it, rubbing our hands pretty - let's go download whatever our heart desires
By the way, through the same menu, Java is turned on if IE "swears" at it (by finding the appropriate items in the list and turning them on).
An equally important question - what kind of Dedicated Server is with "direct IP"? (synonyms - "white IP", "external IP")?
In this case, it is assumed that a RDP IP address is NOT assigned and there is no NAT (router) between it and the Internet space, or the latter is configured in such a way that the connection to the RDP through almost all ports goes smoothly.

How to check for the presence of this very direct IP?
The first criterion is "start" - "run" - "ipconfig" - we must observe that the IP adress line contains an explicit (not local) IP address (like the one to which we connect to the RDP).
The second criterion is checking the port's openness. It is convenient to use icqmsgloger.exe for this.
Run it on RDP, click Start.
After that, from our working machine we type.
And if the IP is direct, then we observe the following picture (or a similar set of symbols and smiles).
In all other cases, IP is NOT.
Do not forget that the group of administrators is called Administrators only on English-language RDP computers, on other language varieties of Windows - the Administrators group is called differently. The name of the admin group can be found in compmgmt.msc or (if the domain is on the RDP) - dsa.msc

It should be borne in mind that on new versions of Windows Server (for example, 2008), when you create a new account or change the password, you may receive a response from the system about insufficient rights to perform these operations. There is no need to rush to be indignant that you were sold a RDP without admin rights. This is the specificity of the security settings and everything is perfectly solved - you just need to run the command line from the start - through the right mouse button - "run as administrator"
 
Possible reasons for your problem:

1. RDP works on a standard port through which leaks occur
Solution:
It is necessary to change the port of the RDP to another

2. Leaks occur through the operating system, programs and browser plugins installed on the RDP
Solution:
Change identifiers of devices and programs installed on the RDP

3. The fingerprint of the RDP device is not original, which allows it to be detected as fake
Solution:
Change device fingerprint to original

4. The leak occurs through the installed browser on the RDP
Solution:
Change the browser to another, disable anonymization plugins, do not use the portable version.

5. RDP is in the black or spam list or marked as a bot machine
Solution:
Replace the RDP or install a proxy (socks5), ssh tunnel or vpn on the RDP.
 
Top