Remote Desktop is great thing when it works but with Windows 10 I usually see one problem after another. I decided to write up some tricks I need pretty often when RDP is going crazy on some Windows 10 box. Nothing special but I hope I save some people hours of time on trying out different tricks found in internet.
Full screen RDP shows local taskbar in foreground
This is one of the most annoying bugs. RDP is opened full screen but what local taskbar is shown instead of remote machine one. It’s possible to see remote machine taskbar only if RDP window is not maximized. Solution is simple – we need to restart Windows Explorer.
- Open Task Manager on local machine
- Find WIndows Explorer from processes list
- Right-click on it
- Select Restart
- Connect to remote machine again
RDP connection to remote machine is very slow
Another show-stopper is slow connection to Windows 10 machines over RDP. It doesn’t seem to happen with all machines but there are always some with issue. It doesn’t matter if connection is made from local network or over internet – when’ it’s slow, it’s just slow. Based on John D’s Tech Site article Remote Desktop slow problem solved it’s an old bug haunting around in Windows from version to version since Windows Vista.
For me it worked when I ran the command on both Windows 10 machines.
- Open command prompt in administrative permissions
- Run the following command: netsh interface tcp set global autotuninglevel=highlyrestricted
- Close command prompt
For me things worked out without restarting machines. The effect was immediate.
Connecting from high-resolution to low-resolution machines
Modern laptops come with damn good displays and it can be problematic to use remote machine with lower screen resolution. Everything is very small and sometimes it’s almost impossible to read the screen. There is RDP client available at Windows Store and usually end users are okay with it. Tech crowd needs different solution usually.
- Open Windows Explorer and move to c:\windows\system32\
- Check if there is file called mstsc.exe.manifest and if file doesn’t exist create it
- Paste the following XML to this file:
false
- Save file and connect to some remote server again.
It doesn’t work for all applications on remote servers but most of applications I need there are well usable after this little hack.
Solution for poor WiFi adapters
I have come machines connected to network over WiFi as cables doesn’t reach these machines. Interesting thing is that also WiFi adapters can be problem although when sitting at machines we don’t notice anything. I have some machines connected to network over WiFi as there is no cabling to rooms where the machines are located. So, it’s straight connection over WiFi like shown on image below.
With some of these machines I had issues also after applying fixes described above. Not always but sometimes RDP connections got slow and then dropped. Few times I was not able to connect to those machines until I restarted RDP service. Sometimes WiFi connection went down and adapter started work again when I restarted machine.
These issues made me think about possibility of low quality WiFi adapters in machines. Okay, one machine has also expensive one but still ran into adapter issues. Working solution was short in the dark – I just thought maybe it works as routers have usually more stable hardware due to different network work loads. I connected problematic machines to my old WRT-54G with cables. Then I configured old router as wireless client bridge that connects to main router over WiFi. Viola! My problems got solved.
Network slow-down! Router-to-router wireless connection doesn’t come for free. Connection speed drops twice. Before client bridge I had 40 Mbps connection between machines and main router. After setting up client bridge connection speed went down to 20 Mbps.
Use client bridge and other router-to-router wireless solution only when anything else doesn’t work.
If you use Remote Desktop [RDP] to connect to other computers on your network, you’ll want to speed up the process. Here’s how to configure optimal settings for a faster RDP experience.
Note: This should work with other versions of Windows and other operating systems you’re working with. Keep in mind your results will vary depending on the speed of your network and internet connection.
Speed Up Remote Desktop Session on Windows
After you have Remote Desktop enabled. Start a new RDP session and click Options.
Next, click the Display tab. Slide the Display Configuration to a smaller size. Under Colors, select High Color [16 bit].
Now click the Experience tab. Uncheck all of the settings to optimize performance. Or select Modem [56 Kbps] from the dropdown menu.
Select the computer you want to remote into and click Connect.
Your Remote Desktop session won’t look as glamorous as having the display settings turned up, but it will make for a faster and more fluid, and responsive experience.
This is especially handy on slower networks and older Windows systems.
Microsoft, remote-desktop, Windows, Windows 10, Windows 7
52 minutes ago, matrixmodulator said:
Using the computer name, not the ip, Is by ip works better? Both computers are 10 feets away and the router is not that far, even when the router was really close to the computers it was behaving the same way.
If you have problems using Remote Desktop [RDP] with your Windows server, there are a couple of things you can fix. This troubleshooting guide aims to help rule out some of the most common causes for poor functionality.
Try UpCloud for free! Deploy a server in just 45 seconds
Problems connecting
Even while you might have trouble connecting using Windows Remote Desktop, you should always be able to log in to the web console at your UpCloud control panel, or by VNC connection, which settings are at your server details.
Once you’ve connected to your server, through either of the methods mentioned above, you should be greeted by Windows lock screen. Sign into your server with an account that has administrator privileges to continue troubleshooting.
If the connection shows something other than the lock screen, try if the server seems responsive. If it does not react to commands you might have to restart your server.
Windows Remote Desktop settings
When you are logged in and the server seems to be working, but Remote Desktop still cannot connect, make sure a remote connection is allowed. The easiest way to get to the option is to open sysdm.cpl by searching for it on the start menu. Then move to the Remote tab.
The Remote Desktop needs to allow connections from other computers for the feature to work. If your server was set to allow remote control with Network Level Authentication, make sure your own computer supports this or select to allow any connection. You can find more information about Network Level Authentication at Microsoft’s TechNet.
While still at the RDP settings, check the allowed users by clicking the Select Users or by pressing S. All users with administrator access are automatically permitted to connect. All normal users must be added to this list. If you were trying to connect with user credentials that do not have admin rights, add the username you wish to connect with to the list of allowed users.
Firewall
The Windows Firewall might be a little restrictive at times, for example, inbound ICMP protocol that ping connections use are disabled by default. Open the Windows Firewall with Advanced Security by searching for “firewall” in the start menu. Move to the Inbound Rules list and scroll down to Remote Desktop rules by pressing R.
Windows Server 2008 should show two rules: Remote Desktop [TCP-In] and Remote Desktop - RemoteFX [TCP-In]. Both of these would in most cases be enabled as long as the server still uses the standard 3389 TCP port for RDP connections.
With 2012 Windows Servers the rules are split between Domain and Private, or Public profiles as well as TCP and UDP protocols, which translates to 4 separate Remote Desktop - User Mode rules, all of which would usually be enabled.
Optionally while at the firewall settings, you may wish to enable ICMP for ping. Press F to find the rules, called File and Printer Sharing [Echo Request - ICMPv4 - In] and v6 for both IP versions.
When you are certain that the Windows Firewall allows Remote Desktop connections, also check the server specific firewall settings at your UpCloud control panel. If you have set the default incoming rule to reject, remember to add a rule to permit traffic to the port Remoter Desktop server is listening to, 3389 by default. Find out more about the UpCloud firewall at the tutorials.
Network connection
Test the internet connection on your server to make sure all your network resources work as they should. Start to ping out from your server. Open the Command Prompt and type cmd in the start menu search. Press enter then use the command below.
ping 8.8.8.8If you enabled the echo requests from Windows Firewall, you can also attempt to ping your server from your own computer. Find the server’s public IP address on your UpCloud Control Panel under Network and Public Network.
In case the internet connection does not seem to work, check your IP configuration on Command Prompt with the following command.
ipconfigThe output will list all of your servers network connections, you should see 3 Ethernet adapters: the private network, public IPv4 and public IPv6. Check that these match with the network information in your server details under Network tab at your UpCloud control panel.
If you see differences in the ipconfig output and your server network details page, check that all network interfaces are set to obtain the IP addresses automatically. To do this, search for Network Connections in the start menu and press enter to open it. Open the Properties for one of the Ethernet adapters, select Internet Protocol Version 6 or 4 and click on Properties button underneath. Make sure both radial buttons are set to automatic and press OK to save. Check through all of the network adapters on the server the same way.
Slow connection
If your Remote Desktop connection works, but feels slow or disconnects at times, you should try updating the network drivers. Download the latest Virtio drivers for Windows.
After downloading the ISO file on your server, with Windows Server 2008 you will need to have a program like 7zip to unpack it. On Server 2012 you can simply mount the file as a disk.
With the files available, open the Device Manager simply by searching for it by name in the start menu and pressing enter. Browse down to Network adapters, select each adapter one by one and run the Update Driver Software. In the update wizard, select Browse my computer for driver software, enter the driver location to the search field and press next. Note to keep the Include subfolders selected.
If you were connected through Remote Desktop while updating the network drivers, you’ll probably get disconnected for a moment. The client should be able to restore the connection automatically after the drivers have been installed successfully.
Port conflict
In some cases, it is possible that another application unintentionally uses the same port as Remote Desktop. This can cause connection issues or prevent Remote Desktop from connecting.
Check the ports used by programs. Enter the command below on Command Prompt.
netstat -a -oNetstat will print out a list of IP addresses and port numbers they use. Look for rows with your Remote Desktop port number [3389 by default] and check the program ID [PID] at the end of these lines. One PID will belong to the RDP service. If you see another PID that uses the same port, these will conflict with one another.
To find out which programs the PIDs belongs to, use the following on Command Prompt.
tasklist /svcRemote Desktop is listed as svchost.exe TermService, any other PID that uses the same port number causes issues.
Change RDP port number
If there is a port conflict, you can resolve it by changing the port used by one of the applications. Microsoft recommends to ideally change the port used by any other applications. If this is not possible, the port number Remote Desktop listen to can be changed with a couple of steps.
Change the port number because it can also help to reduce intrusion attempts through obfuscation. This should not be your only method of security.
To change the port number, you’ll first need to choose a free port not used by anything else on your server. Check the ports currently in use with netstat -a -o as described previously. The new port number can be anything from 1024 through 49151.
Add the port number you’ve selected to the Windows Firewall Inbound rules by creating a new rule. In the New Inbound Rule Wizard, select the following
- Rule Type: Port
- Protocol and Ports: TCP, Specific local ports,
- Action: Allow the connection
- Profile: all options ticked
- Name: Remote Desktop – TCP
In the steps above the is the new port you wish RDP to listen to. Make sure your new firewall rule is set up correctly. Once you change the RDP port you’ll need it to work to be able to connect again.
The port number for Remote Desktop was not designed to be changed, and the only way to do so is through editing registry. We highly recommend that you make a backup of your server before making any changes.
Open the editor by searching for regedit in the start menu and pressing enter.
Locate the following key in the registry file system.
HKEY_LOCAL_MACHINESYSTEMCurrentControlSetControlTerminal SErverWinStationsRDP-TcpPortNumberOpen the PortNumber registry key for edit, change the display to Decimal, enter your new port number and click OK to save the changes.
For the changes to get applied, you will need to restart the RDP service. Open Services again by searching for it in the start menu and pressing enter to run the program.
In the Services [Local] list, scroll down to find Remote Desktop Service, and restart it. A confirmation popup asks to restart other related services as well, click Yes to continue.
You will get disconnected if you were using RDP to make these changes. Afterwards just reconnect to your new port by defining it in the Computer field on RDP connection.
windows.server.example.com:34567With the new port, you should get uninterrupted reliable remote access.
Getting help
If you ran into deeper trouble or need help with something else, don’t hesitate to ask. When you contact UpCloud Support, try to explain the problem to the best of your ability. Include any steps you’ve already taken together with their results when you troubleshooted the issue. It will help our support team to solve your problem.