Question Locked

RDP Stopped Working

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Ok, I'm hoping this is a simple one.

I have a network of 30 or so PCs, with a Windows Server 2003 running everything as Domain Controller.

I often need to access this DC from a client PC to carry out work, and this has always worked perfectly.

A few days ago, and there were no changes made to either the client PCs or my server, I found whenever I punched the server IP address (or name) into RDP, I get a failure, with a box saying that I might not have Remote Connections enabled, or there might be too many connections, or there is a network problem.

Ok, firstly, there is no network problem. The client PC can see, ping, and access the server just fine. Remote connections ARE enabled. they were a few days ago when it worked perfectly and they still are.

Secondly, I can log into another client PC - using the exact same login credentials - and RDP to my server just fine.

Ergo, the problem is with the individual PC that is trying to connect; not the user.

The problem is that I don't see where the problem is. Terminal Services manager on the server shows only 1 user logged in (administrator), which is exactly right. I can confirm no other user sessions are in operation.

What the hell is wrong!?

4 replies

by peconet tietokoneet

Can you print out a log of your network?
You should be able to, then look at any errors. You should be able to trace (hopefully) the culprit. Or shut down the computer that you think might be the culprit and see about its link on the log that you have printed out. It is hard to say on here what could be the problem because of your network setup. The best port of call would be the error log, print this out and see if you can trace it back, sometimes it is not an easy task, but then again it could be staring you right in your face. You could try and re-boot the computer that you think is the culprit and see if the error comes back, if not you have your answer. It might be that the network nic needs replacing, or too many connections all at once trying to log on at the sametime

by arujammer

I got this problem once, after server update after rebooting the server for the second time RDP finally works.

Went looking for explanation on internet, but rebooting was the asnwere.
It worked for me, give it a try , maybe it will work for you too...

by smokingmirror

Hmm...I obviously tried rebooting once when I was eliminating the Usual Suspects (firewall, NIC, blah, blah, etc.), but will try a second reboot.

I've obviously rebooted the client PC in question (XP Pro SP2, BTW), to no avail.

I've subsequently noticed this behaviour from anothe rclient PC - regardless of the user logged in - so I'm content this is not a user issue at all, but a problem with the Server communicating with these two clients. I don't think there's an inherant or even serious network issue, however, as all other connection types run fine, I can access the server from these two clients by non-RDP methods, and I can access the server via RDP from all other client machines.

*sigh* I really didn't want to have to do this, but I think I'm going to have to start crawling through the logs. Arse!

***EDIT*** Ok, found the problem, but thought I'd post it here in case anyone else finds themselves in a similar situation.

It would appear from careful investigation of my server logs that I had a Terminal Services issue, which manifests as a level 50 error, TermDD, and states "The RDP protocol component "DATA ENCRYPTION" detected an error in the protocol stream and has disconnected the client."

This is caused because my Temrinal services on the server is running as FIPS Compliant for added security. It would appear that older XP Pro systems have a problem with this and are unable to connect as a result.

Solution: Upgrade SP to SP3 and everything now works again.

This discussion is closed to new replies.