You run DCDiag and it returns a failure that names can not be resolved.

testing server: default-first-site-name\mydomain
starting test: connectivity
the host 7397e120-1c8d-4f2d-b8cb-d829d16d949a._msdcs.mydomain.local could not be resolved to an
ip address. check the dns server, dhcp, server name, etc
although the guid dns name
(7397e120-1c8d-4f2d-b8cb-d829d16d949a._msdcs.mydomain.local) couldn’t be
resolved, the server name (myhost.mydomain.local) resolved to the ip
address (192.168.1.5) and was… Continue reading

Many WAN connections can vary in quality and latency, and often times these two characteristics will manifest themselves in disconnected terminal services sessions. By doing two relatively easy registry hacks, you can reduce these disconnects and improve the overall experience of your users.

Keep Alives:

In the registry at HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server, create or edit the DWORD value of KeepAliveEnable and set it to 1. This will… Continue reading