So, it’s straight connection over WiFi like shown on image below. I have some machines connected to network over WiFi as there is no cabling to rooms where the machines are located. Interesting thing is that also WiFi adapters can be problem although when sitting at machines we don’t notice anything. I have come machines connected to network over WiFi as cables doesn’t reach these machines. It doesn’t work for all applications on remote servers but most of applications I need there are well usable after this little hack. Save file and connect to some remote server again.Check if there is file called and if file doesn’t exist create it.Open Windows Explorer and move to c:\windows\system32\.Tech crowd needs different solution usually. There is RDP client available at Windows Store and usually end users are okay with it. Everything is very small and sometimes it’s almost impossible to read the screen. Modern laptops come with damn good displays and it can be problematic to use remote machine with lower screen resolution. Connecting from high-resolution to low-resolution machines Run the following command: netsh interface tcp set global autotuninglevel=highlyrestrictedįor me things worked out without restarting machines.Open command prompt in administrative permissions.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.įor me it worked when I ran the command on both Windows 10 machines. It doesn’t matter if connection is made from local network or over internet – when’ it’s slow, it’s just slow. It doesn’t seem to happen with all machines but there are always some with issue. RDP connection to remote machine is very slowĪnother show-stopper is slow connection to Windows 10 machines over RDP. Find WIndows Explorer from processes list.Solution is simple – we need to restart Windows Explorer. It’s possible to see remote machine taskbar only if RDP window is not maximized. RDP is opened full screen but what local taskbar is shown instead of remote machine one. Nothing special but I hope I save some people hours of time on trying out different tricks found in internet.įull screen RDP shows local taskbar in foreground I decided to write up some tricks I need pretty often when RDP is going crazy on some Windows 10 box. When tested there are no bandwidth/latency issues in between these three systems.Remote Desktop is great thing when it works but with Windows 10 I usually see one problem after another. PC-1 at Home -(SSL VPN and RDP)->PC-2 at Office-(Internet and Horizon Client)->PC3 at Customer siteĪ) Very slow/ freezes and mouse cursor hang while accessing PC-3 from PC-1ī) Good performance while accessing PC-3 from PC-2Ĭ) Good performance while accessing PC-2 from PC-1 The scenario is as below: (All systems are windows 10) from office, the horizon connection to PC-3 work fine without any issues. But if the user directly work from PC-2 console, ie. In this scenario the connection to PC-3 is very slow, mouse cursor jumps and hangs frequently, but connection from PC-1 to PC-2 is fine. The user connects to his office windows PC (PC-1) through windows RDP from his laptop (PC-2) at home, and then the user connect to customer PC (PC-3) using Horizon Client from Office PC.
0 Comments
Leave a Reply. |