Monday, February 11, 2013 10:50 PM
The title seems a bit ambiguous, but that's about the best way I can describe it. RDP aint workin' is another potential subject but I didn't think that would help much. :)
Basically, after performing a round of windows updates, the server isn't accepting RDP connections. RDP is enabled, all the settings in HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\WinStations\RDP-TCP are identical to other servers in the same cluster, and the firewall is disabled entirely.
When I do a 'netstat -an', there is nothing listening on 3389. I cannot telnet to 3389, as of course there is nothing listening on that port. I can restart the Remote Desktop services, and there are no errors in the event logs showing anything wrong. I've performed an 'sfc /scannow' and rebooted, and no love. I even ran the Fixit tool from the following link:
And left it at 3389, rebooted, still nothing. If you can't tell, I've been searching around for a fix for this, and have been unsuccessful so far.
Gabriel Matthews Systems Engineer - QServices Co.
Monday, February 11, 2013 11:54 PM
What's the port number in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber? Also you may try this command: SLMGR /REARM if you did upgraded recently. This post may help:
Bob Lin, MVP, MCSE & CNE Networking, Internet, Routing, VPN Troubleshooting on
- Marked As Answer by Clarence ZhangModerator Thursday, February 28, 2013 9:46 AM