Take the 2-minute tour ×
Super User is a question and answer site for computer enthusiasts and power users. It's 100% free, no registration required.

I can access the machine via RDP from another client, from exactly the same network, through exactly the same forwarded port.

What might be causing remote desktop client to hang today? It usually works.

The TCP connection is made, and I'm prompted for credentials. Then, hang ...

share|improve this question

4 Answers 4

Alas, very soon after posting the question, I found what seems to be the root cause. The RDP client seems to be oblivious to a server side socket close, due to bad credentials. When I put in the correct password, it succeeds!

I hope other people benefit from this Q&A. A case of what looks like a connection problem is actually stupidity in the RDP client.

Here are the last two packets from a tcpdump trace:

09:29:05.977126 IP server.3389 > client.65355: F 1292:1292(0) ack 1438 win 7965
09:29:05.978195 IP client.65355 > server.3389: . ack 1293 win 16229

The server (actually a port forwarding server, not the Windows machine) has send a FIN packet, indicated by the F. The client TCP stack acks it, but the application remains oblivious to the one-way close and keeps displaying the connection attempt dialog box.

I have reproduced it several times. When I disconnect and try to reconnect with the wrong password, it hangs. Right password, and it proceeds. Maybe in another ten years they will get RDP right.

P.S. the other client not displaying the behavior is a free app for Android.

share|improve this answer

I faced similar issue today. I was first time trying to access machine using tunneling through putty.

It turned out to be issue with completeness of credentials. I missed domain name before user name which we normally don't add while connecting.

share|improve this answer

If you are on a LAN that does not have internet access, you'll have to disable the computers from trying to phone home and get certificate updates (this causes a delay when initializing RDP sessions)

Guide: http://www.batchworks.de/remote-desktop-client-hanging-at-securing-remote-connection/

share|improve this answer

The way I finally solve this problem is uninstall the Remote Desktop Connection Broker. It waste my whole day to eventually figure out it. There must some setting to configure this hanging in Broker, but I don't have enough time to dig in, so I just simple uninstalled it. Hope someone can find the way to change it~

share|improve this answer

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.