×
注意!页面内容来自https://hostman.com/tutorials/how-to-fix-rdp-errors/,本站不储存任何内容,为了更好的阅读体验进行在线解析,若有广告出现,请及时反馈。若您觉得侵犯了您的利益,请通知我们进行删除,然后访问 原网页
Connecting to a remote desktop using RDP is a common task. It is often used in a corporate environment so that employees can work remotely on a corporate computer within the company network. This is especially true in cases where work requires a large amount of computing resources that may not be available on a home PC.
In this article we will look at several common problems with RDP and how to solve them.
Choose your server now!
Here's an example of a common RDP error you might receive when trying to connect to a remote desktop.
In some casesthere might be no reasons provided at allwith the notification window simply informing you that “an internal error has occurred”.
Typicallythe RDP connection errors have similar causes and solutionsso in this article we will look at several ways to troubleshoot connection problems that might work for most of those RDP errors.
Here are a few reasons that can lead to problems with connecting via RDP:
incorrect connection settings;
problem of matching the domain name and IP address of the remote computer;
DNS server cache;
RDP cache;
RDP port being used by another application;
the firewall is blocking the connection;
Windows updates.
Let's look closer at how to fix these issues.
By the waywith Hostmanyou can run your workloads on efficient NL VPS that support low latency for EU-based users. Check this outwe have plenty of budget VPS hosting options for your projects.
One of the reasons why there may be a problem with connecting via RDP is incorrect connection settings. Below are a few settings that may affect RDP connectivity:
If you enter incorrect login information on the remote computerconnecting via RDP will not be possible. Make sure you enter the correct credentials and that they have sufficient permissions to connect.
If you enter an incorrect computer name to connect via RDPthe client will not be able to find it and will display the error "Remote Desktop could not find the computer." To find out the name of the remote computer to connect tofollow these steps:
Open File Explorer on the remote computer and go to the This PC tab.
Right-click in the work area and select Properties.
After thisthe System page will open. In the Computer namedomain nameand workgroup settings sectionfind the connection information.
If the problem is not resolvedcontinue to the next section.
When connecting to a remote computerthe address is usually its domain name associated with a specific IP address. Domain names and their corresponding IP addresses are stored on a DNS server. Sometimesthe domain name in the DNS server is assigned an incorrect address; in this caseyou will not be able to connect to the server via the domain. To fix this issuetry to connect to a remote computer using its IP address.
Did you know?
Hostman offers cost efficient tariffs for Cloud Servers! Check it yourself and start deploying now!
To find out the IP address:
On the remote computerlaunch cmd (Win+Renter cmd and press Enter).
Type the ipconfig command and press Enter.
In the IPv4 Address field you will find the computer's IP address.
Nowtry connecting to a remote computer via RDP using the IP address instead of the domain name.
Sometimes clearing the DNS cache helps. To do this:
Launch cmd as described above.
Run the command ipconfig / flushdns.
The hosts file in Windows is a text file that maps domain names to IP addresses. Your computer uses this file as the primary source of hostname information before it queries the DNS server.
If you suspect there is an error in the DNS server informationyou can add an entry to the hosts file with the domain name and IP address of the remote computer.
To do thisopen the hosts file using Notepad. The file is located in the C:\Windows\System32\drivers\etc\ directory. Add a new line to it with the IP address of the remote computer and its domain name and save the changes.
By defaultRDP uses port 3389. If any other application on the computer uses the same portan error will occur when connecting. Let's try changing the port to 3388 and see if we can connect via RDP. To do this:
Open Registry Editor and navigate to the RDP-Tcp directory.
Find the PortNumber entry.
Right-click on it and select Edit.
Enter another port number in the value data field.
If you are unable to resolve the RDP connection problem using a Microsoft clienttry using its alternativessuch as AnyDesk or Remote Utilities.
You may sometimes encounter RDP connection errors after a Windows update because one of the newly installed files may interfere with RDP functionality. If your operating system has been updated recentlytry performing a rollback.
Choose your server now!
Disabling your firewall is an easy way to check if it is causing RDP errors. If the problem disappears when the firewall is turned offyou need to reconfigure it or leave it disabled. The last option is not entirely safeso let's configure the firewall.
Open Windows Defender Firewall and click Allow an app or feature through Windows Defender Firewall in the left menu.
Click Change settings.
In the list of programsfind Remote Desktop and check the Private and Public checkboxes next to it.
Close the window and try to connect. If the problem was with the firewallyou should now be able to connect to the remote computer.