As simple as it is, most of the time the issue will be with a machine on DHCP connecting to one with a static IP and the last one using a different DNS server than the one on DHCP. Hence, running an ipconfig /flushdns sometimes will work. Now, how do you solve the issue?, To resolve the problem, make sure that the correct network adapter is bound to RDP-TCP connection. To do it, follow these steps: On the server, sign in to the server locally (not using Remote Desktop/Terminal Client)., When you try to connect to a Windows computer or virtual machine by using Remote Desktop Protocol (RDP), you receive a message that resembles one of the following messages: Access is denied. User is not authorized. The most common "access denied" messages, and the most likely causes or circumstances of each, are as follows: Access is denied., If you can connect using RDP directly but not through the web, the issue may lie in the RDWeb configuration, not the gateway itself. Double-check the RDS deployment configuration to ensure that your published applications are not accidentally misconfigured., Terminal Server Client (Remote Desktop Client) connection failures such as "Unable to RDP, "Remote Desktop Disconnected," or "Unable to Connect to Remote Desktop (Terminal server)" are common problems that we have seen in product support. This article summarizes the various causes for such failures., Because of a security error, the client could not connect to the remote computer. Verify that you are logged onto the network and then try connecting again. When the Remote Desktop client reconnects, the RDSH server reconnects the client to a new session instead of the original session..