John smith 2007-07-10 17:52:20
I have a Windows 2003 server with SP1 that used to run Remote Desktop just
fine. We rebooted it yesterday and after the reboot, Remote Desktop won’t
1. We don’t have any firewalls (windows or third party) running
2. When I do a netstat -an, port 3389 doesn’t show up.
3. When I check the services, terminal services is running, but cannot be
stopped or started
4. I deleted and tried recreating the rdp connection under Terminal services
configuration but no help
5. I had checked the registry and am sure the port 3389 is configured
6. I am sure Remote Desktop is checked in the Remote property
7. “RDP-Tcp (listener)” does not show up under the TerminalServices Manager
Any suggestion? Thanks.
Vera noest [mv 2007-07-10 17:52:53
This problem has been reported here quite a number of times the past
Have you tried a second reboot? Most posters have reported that that
fixes the problem (until the next reboot, that is).
MCSE, CCEA, Microsoft MVP – Terminal Server
TS troubleshooting: http://ts.veranoest.net
*———– Please reply in newsgroup ————-*
Ramon niese 2007-08-13 17:33:47
We had a similar problem. Problem was solved by selecting the correct NIC
under terminalservices configuration.
“Vera Noest [MVP]”
Pvledoux 2007-08-28 15:40:02
we had exactly the same problem with one server.
I also tried to delete and recreate the rdp-tcp listener because it was
no visible any more in the Terminal Services Manager. But when I
recreated it, I named it “TCP”, not ‘RDP-Tcp’. I don’t know if it was
the problem, but I delete the ‘TCP’ listener and recreate a ‘RDP-Tcp’.
Then I bind it to only one nic interface (like mention in the previous
quote), I rebooted, and now it works.
I think that RDP still sorcelery!
Ramon Niese a crit :