windows server 2012 remote desktop freezes

Some organizations configure their corporate firewall to block outbound RDP traffic, thereby preventing connectivity to remote systems. This setting is especially common for Wi-Fi networks found in some hotels, airports and coffee shops.įirewall service issues also may come into play when you use RDP to access a home computer while at work. For example, the client and the server may both run Windows Defender Firewall, and there will probably be one or more hardware firewalls between the two systems. You may need to configure multiple firewalls. Remote Desktop Protocol (RDP)-based tools use RDP port 3389 by default. To avoid firewall problems, ensure that the port your remote desktop software uses is open on any firewalls residing between client computers and the server they connect to. It's easy to dismiss the notion that a firewall could contribute to a remote desktop not working, but it's quite common. Likewise, you may discover the problem is unique to VPN traffic or a particular subnet.

In doing so, you might discover that the problem affects wireless connections but not wired ones.

If you suspect the network might be to blame, try to narrow down the scope of the issue to find the root cause. The goal is to find out if the problem is specific to an individual client, the network or a terminal server/Windows server. The easiest way to diagnose this issue is through the process of elimination.įirst, try to establish a session from a client that has been able to successfully connect in the past. Network failureĪ lack of a valid communications path can prevent a client from connecting to a remote desktop session. There are many remote desktop connection problems that administrators may encounter, including network failure, Secure Sockets Layer certificate issues, authentication troubles and capacity limitations.Īs a desktop admin, you can prevent and solve common remote desktop problems by using these tips.

Windows server 2012 remote desktop freezes