Windows Server 2003 RDP server stoped working

[ghandi62]

We have a web server that is running Server 2003 Standard, and previously we were able to RDP into it for remote administration, but recently installed .Net 3.5 and made some settings changes in IIS, and now we are unable to connect via RDP anymore.



When attempting to connect to the RDP server, it just comes back as cannot connect to remote computer. Also to test if the port was being blocked somehow, tried to tried to RDP to "localhost" while on the server itself, and same error occured.



This is a very weird and big issue, because I don't see how a .Net install could affect Terminal Services. Please offer any assistance that you are able to.



Thank you.

 

[AaronBeau]

I would verify that installing .NET 3.5 didn't change your Remote Desktop settings.

To check:
1) System Properties (Win + Pause-Break)
2) Remote tab
3) Verify the Remote Desktop is enabled

 

[58sniper]

You can use portqry to verify it's listening on that port, and sc.exe to make sure the service is running (I'm referring to checking it remotely).

I have heard of some servers not responding to RDP after a reboot, and a follow up reboot fixed the problem.

Pat Richard
Microsoft Exchange MVP
Contributing author Microsoft Exchange Server 2007: The Complete Reference

 

[ghandi62]

I still cannot find a solution to the issue. Here is what i've done to try to fix the issue so far.

Troubleshooting steps already taken:
1.) Terminal Service is up and running in services.mgr
2.) I have run netstat -a -n. Port 3389 is definitely NOT listening or established. As a double check, I have also tried to telnet to the machine and it fails on a connection error.
3.) There is no firewall on the machine or on my internal network. In fact, this machine has worked in the past and I have multiple Windows 2003 machines on the network that i can RDP to.
4.) I have insured that no filters are running on my network connection
that might prohibit entry through this port.
5.) I have tried changing the port that Terminal Services use.
6.) I have tried connecting to "localhost" while logged into the machine to ensure there is not filter or firewall outside the system and got the same connection error.
7.) I have definately ensured that the Remote Admin box is checked in System Properites.
8.) I have restared the machine multiple times with no effect.
9.) I have tried exporting and importing Terminal Services Registry settings from a working machine to this one with no effect.


If there is anyone that can offer any more advice. Please HELP.

 

[pgaliardo]

You say you can't telnet into the server either. Can you ping it from the network. Have you determined if this is just an RDP issue or a networking issue?

 

[ghandi62]

I cannot telnet to port 3389. You can ping the server from anywhere else on the network. So it is not a networking issue. Also, this is a web server, and all other services are working to spec.

 

[ghandi62]

They problem was with the RDP-TCP Listener. I had to remove the existing one and then create a new one and then restart the Server. All is working to spec now. Thanks for your suggestions.