Windows server 2003 cannot connect rdp

If you keep trying you will eventually connect to the other server and all the apps will work. What I noticed was a hidden device would not load its driver. You have to right click on "Device Manager" and select "Show hidden devices" for it to show up. To continue this discussion, please ask a new question. Get answers from your peers along with millions of IT pros who visit Spiceworks. Any advice will be highly appreciated. Spiceworks Help Desk. The help desk software for IT. Track users' IT needs, easily, and with only the features you need.

Learn More ». Ghost Chili. Bottman Oct 17, at UTC. Stu Oct 17, at UTC. Thanks to all Thnxz anywayz.. Any further suggestions :. Hakim, If it is still being used through the day then it would be best to leave until after working hours. Just for clarification - is it the case that desktops can't login into the terminal server?

It was not even listed in commands output. It was in vain as usual. Any other advice before I make my mind to reinstall OS.

Tim Oct 17, at UTC. Let us know what you find. B-C This person is a verified professional. Verify your account to enable IT peers to see that you are a professional. Usually a video driver issue RDP almost always on servers gets jammed up with some driver - and usually a few reboots resolves for me is this an older Dell Server by chance?

I wouldn't even do a repair install on a server I also toggled "Allow remote connection" off and on as well as re-activated Terminal license server Users using RDP on this box? I also toggled "Allow remote connection" off and on as well as re-activated Terminal license server Using RDP to work not just for administration.

Thai Pepper. Richard Wright This person is a verified professional. Sign in to vote. Hello, I have a server which no one can RDP into and would like to hopefully find a solution.

Message that users get when trying to remote desktop to a Windows R2 server: "The client could not connect to the remote computer. Wednesday, June 9, PM. This problem is now fixed. We loaded windows updates and then rebooted the server, not expecting this to fix the rpd issue.

But After the reboot we are able to RDP in normally. Marked as answer by 4ndrew Monday, June 28, PM. Monday, June 28, PM. Checked if port is listening! Thanks very much for the reply! I tried the following command from another system telnet servername Connecting To Could not open connection to the host, on port Connect failed I checked in device manager as you recommended.

Hello, From the Terminal Server, can you telnet the localhost with Port ? Wednesday, June 16, AM. Hi Lionel, Thanks for the reply. Here are the results of the netstat Microsoft Windows [Version 5. Thursday, June 17, PM. Hello, On the server side, please run services. Friday, June 18, AM. Friday, June 18, PM. Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account. Version: 2. I think the culprit is license. The text was updated successfully, but these errors were encountered:. Sorry, something went wrong. Unfortunately, this issue is still in effect. I've restarted the licensing service and now I'm able to connect with mstsc client, but not with remmina, same errors in console.

Do I still need to compile anything? Sorry for bothering you with the ancient Win by the way.