Until it times out and then your RDP connection proceeds. Since the machine cannot get out to the internet, it sits there

The reason that this lag occurs on machines that cannot access the internet is because remote desktop actually reaches out to the internet to check for root certificates that may have been revoked. This is why if you try to connect from a Win7 or Server 2008 machine to a XP or ServerĢ003 box you do not see the long lag at 'securing remote connection'. Windows XP and Windows Server 2003 there were the last operating systems to use the older RDP client that didn't use secure encyrption via Network Level Authentication (NLA). I manage several different networks that are 'dark sites' with no connectivity to the internet due to the highly critical and sensitive nature of them. This is an issue on networks that do not have access to the internet. The next thing is to find out what exactly RDP is looking for and how to disable it (without disabling entire CredSSP authentication, since this also disables stored credintals). I need someone with same problem to test connecting to the RDS with only TCPv4, only 4 minimal parameters (ip/mask/gate/dns), with DNS doesn't resolving Internet addresses and Gate doesn't allowing Internet connections.

I noticed that the problem appeared after some Windows update.ĪFAIK clean Windows 7 (no SP) installation doesn't have this problem. I think credintals prompt is linked to inavailable domain controller (no DNS = no AD). The connections open faster, though 'Securing remote connection' still hangs for 5-7 seconds, always ending up with credintals prompt, despite credintals are saved and proved to be valid.Īs all DNS servers in our enterprise resolve Internet addresses, I cannot test it with DNS server. When no DNS server is available, RDSC doesn't make any requests.

Terminal server manager windows 10