Windows 10 RDP Freezes Intermittently
Hello,


Want to know if anyone have faced the Windows 10 RDP connection freeze issue during lockdown period?


Users are logged into personal windows 10 laptop and connected to network on VPN, then from laptop they are remotely logging into workstations at office, they are using high end design application for rendering etc.


Steps check till now:


1. Compared different machines of same model and some are facing issue and some are not, but there is no difference in terms of softwares, patches, hardware specs etc., graphics card etc.
2. Checked if antivirus is causing issue , but CPU and memory are at low when issue occurs.
3. Disconnecting and reconnecting same machine on RDP works.
4. Same department users when at office,connected to network  and RDP remote machine there is no issue at all.


Next action plan:


1. There is one known issue highlighted at different forums that it can be due to mstsc client on windows 10 machine as something has changed in transmission protocol to use UDP packets , need to disable a registry key so that it falls to use TCP protocol.
2. Try to see if user is getting same issue when using Remote control viewer of sccm by providing them access to test.
3. Change the Display ‘ chose color depth of remote session’ to 16 or 32 bit in the RDP option.
4. Try RDP client from Microsoft store and see if still issue is there.


Any other suggestion or any one faced same issue can highlight the point.
After doing different troubleshooting steps and at the end only finding solution that enabling UDP client off settings in local group policy , Microsoft has also confirmed that this is a known big on which Microsoft is still working and tentative date to release fix is April 2021 and till now only workaround available is to enable this setting.
We currently have all our machines still on Windows XP and have only just upgraded some with Office 2007.


Budget dollars just have been too cost prohibitive to upgrade all 1,000 of our workstations. At some point due to licensing and availability we will be forced to upgrade. 


The one thing I’ve noticed difficulty with right off the bat has been the ability to connect via RDP to a Windows Server 2008 box. Without some registry hacks/mods in XP this can be problematic if the server is set to the newest (and more secure) RDP protocol. Windows 7 doesn’t have this issue. in this case you can try simply rebooting your home router, if not at home please contact your network administrator.

failing this try using alternative dns -

[image]

[how to enable faster dns resolution on windows 10](https://www.000webhost.com/forum/t/how-to-enable-faster-dns-resolution-on-windows-10/118671) [tutorials](/forum/c/tutorials)

this is a windows based tutorial so if you r… Dear Jay Nelish


Your Question is incomplete


is the specific system is not on Network? its might be a problem discovered last year, that system ping but not share any data, or cannot access the system


you click on start menu and then click on run  

type serivces.msc  

and run the computer browser service, Remote Procedure call service, Server, and Client service


and your problem will resolved  

but actually this is because of virus change your antivirus program and scan your system wtih updated A/V This is because Exchange Server 2010 does not issue UDP notifications to Outlook. So, Outlook could not register to receive UDP notifications from Exchange Server 2010. This is why u face the problem. To overcome this, please try out this….


1. Install Update Rollup 1 for Exchange Server 2010, ([for download here](http://www.microsoft.com/downloads/en/details.aspx?FamilyId=371add31-d7a0-4c8b-8325-a6fced2d05e6&displaylang=en).) After doing this….
2. Open REGEDIT and locate for the registry key (u can press ctrl+F to search)


HKEY\_LOCAL\_MACHINE\System\CurrentControlSet\Services\MSExchangeRPC\ParametersSystem


NOTE: The “ParametersSystem” registry subkey is needed to create


Now add the following registry data to the server:  

a) Value type: REG\_DWORD  

b) Value name: Maximum Polling Frequency  

c) Value data: any integer between 5000 and 100000  

Now quit regedit and restart the computer.


Remember, generally the default polling interval for Outlook is about 60 seconds.  

This is based on Outlook 2003, if you use Outlook 2007, the procedure is almost same, only care about the registry key.  

Important: Before doing anything in REGEDIT, it is safe to take necessary back up of registry (File > Export) and your important data.


Thanks– i assume your new router is wireless?

limited access with wireless usually means you don't have a valid ip address assigned. you need two things for a working internet connection. 1. you need a physical connection, known as layer 1 and layer 2. 2. you need a logical connection known as layer 3.

if you've got the limited access message that means your laptop has a working wireless connection at layers 1 and 2. what you don't have is the layer 3 connection i.e. an ip address.

there could be a number of reasons why this is happening. i would suggest that you start by powering your pc down - shut it off completely not just hibernate it or just shut the lid. next power down the router, pull the power cord out of it. let the router sit unplugged for about 2 minutes. power the router back up......wait about 2 min more. power your pc back up.

learn how to use the command line command "ipconfig". you access the command line via the accessories folder on windows. when you get the c:/> prompt - enter the command "ipconfig" hit enter. in the group of stuff on the screen you want to see an ip addess assigned to the wireless interface. when you get the limited access message the first thing you want to do is check to see if you have an ip address assigned.

if the above trick doesn't work, then i suspect there is something wrong with your network configuration on your pc. if you take your laptop to a starbucks does it work there? you can try a factory reset. push and hold the reset button for 15 seconds and then release. the button should be located on the back of your gateway/modem/router, and you will need a ballpoint pen or toothpick. you should then be able to access your gateway using the standard means with the passwords listed on the label on the gateway.  \_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_how can you be in two places at once, when your not anywhere at all?i really want to become a procrastinator, but i keep putting it off.there are three kinds of people, those that can count, and those that can't.'our great democracies still tend to think that a stupid man is more likely to be honest than a clever man, and our politicians take advantage of this prejudice by pretending to be even more stupid than nature has made them.' :bertrand russell pat, sorry to read about your notebook issue.  be assured that i have been monitoring this post and see that you have received very helpful input.  if you're not able to duplicate the memtest86 hit, you may want to scan for "infections" as andre s. recommends.  however, along with malwarebytes, i would also run tdsskiller and combofix.   after doing this and the laptop still freezes, you may want to contact hp's excellent elite premier support team at 866 625-1175, especially if this model is still under warranty.  you also may want to pm me with the product number, serial number so i can get a case started for you or so we can discuss some hp options if out of warranty. that is where i'd start as well. osi...
so:
1. physical link (maybe check the patch panel and the cabling that's involved in connecting to the computer, maybe swap cables and try a usb to ethernet adapter to rules the nic out.
2. data link - check the switches and switchports on the way. maybe try to use different portts
3. network - most likely not an issue if all the other computers are working fine...
etc.
but this is pretty much it: just a heads up. i believe we found the solution. as far as we could tell, these issues began to happen after we moved everything to windows 7. however, one of the helpdesk people said they thought they remembered it happening once before that while the computers were still all xp. 
i looked into the av, which was moved to a different server and upgraded shortly before our windows 7 project began. evidently, trend's migration tool that was used did not migrate over port exceptions in the firewall. after adding a few recommended exceptions to the firewall, everything started to work. 
it seems that the client firewall was blocking return snmp traffic from the printer which was keeping the computer from realizing that printing had completed. this was keeping the connection open to the printer preventing anything else from printing on that computer or any others connected to it. 
the ports added as exceptions were: udp 161(probably the only one needed), tcp 9100, 9220, 9500. sometimes one or both of these patches help, especially if the system is showing high ram and/or cpu usage when checking updates:
https://support.microsoft.com/en-us/kb/3050265




https://support.microsoft.com/en-us/kb/3102810﻿﻿
﻿