Fix 0XC00A0026 RDP Client Query Timeout in 5 Minutes

Cause #1: Firewall or Security Software Blocking RDP

The most common reason for 0XC00A0026 is something on the client side silently dropping the RDP traffic. It's almost always a third-party firewall or antivirus with network protection. The Windows built-in firewall rarely causes this, but I've seen it happen after a feature update reset the rules.

Fix: Temporarily disable any third-party security software and try the connection. If it works, add an exception for mstsc.exe and port 3389. For the Windows Defender Firewall, make sure the inbound rule for Remote Desktop is enabled:

netsh advfirewall firewall set rule group="remote desktop" new enable=Yes

Then test with:

Test-NetConnection target-server -Port 3389

If you see TcpTestSucceeded : True, the port is open. If not, you've found your problem.

Cause #2: DNS or Hostname Resolution Problems

Another frequent culprit is the client trying to resolve the server's hostname and getting a slow or wrong answer. The RDP client sends a query and waits for a response. If DNS takes too long or sends back a stale IP, the server never gets the ACK and times out.

Fix: ping the target by hostname and by IP. Compare response times. If the IP responds instantly but the hostname is slow, fix DNS. A quick workaround is to connect via IP address, but that's not a permanent solution.

Check the DNS servers in your adapter settings and make sure they're reachable:

ipconfig /all | findstr "DNS Servers"

If you're using a VPN, the DNS might be pointing to the old network. Flush the resolver cache and re-register:

ipconfig /flushdns && ipconfig /registerdns

Also, check the hosts file for any stale entries. I can't tell you how many times someone had an old IP in there causing this exact error.

Cause #3: Network Congestion or MTU Issues

Less common but still worth checking, especially over Wi-Fi or satellite links. If there's heavy packet loss, the initial RDP handshake packets can get dropped. The client waits for a response that never arrives, and you get 0XC00A0026.

Fix: Run a packet loss test:

ping -n 100 target-server

Anything above 1% loss is suspect. If you're in a corporate environment, check if there's a QoS policy messing with RDP. Also, try lowering the MTU on the client's network adapter:

netsh interface ipv4 set subinterface "YourAdapterName" mtu=1400 store=persistent

This fixes the issue when your ISP or VPN tunnel has a smaller MTU than the default 1500. I've seen this with DSL and some VPN clients.

Quick Reference Summary

Start with the firewall test—it's the most common and the easiest to rule out. Then move to DNS. Don't bother restarting the server or reinstalling the RDP client unless you've exhausted these three, because it's not a server-side issue 95% of the time.