Remote Desktop not Responding after Reboot

[itsp1965]

Hi guys, I have recently built a couple of Win2K3 servers one Sun v20z and the other Proliant DL380G3. I have noticed some strange behavior after installation of SQL Server 2005 w/the .NET Framework 2.0 (I am just guessing here that this is the prob). Upon rebooting the server, I cannot connect via Remote Desktop. The Event log shows nothing out of the ordinary, Terminal Services is running, and the TS mgmt console shows the server in a TS listening state with no connections. The server responds fine after rebooting it, but I am somewhat perplexed at this behaviour. Has anybody run into this? Thanks.

Regards

Terry

 

[NJForensics]

Terry-

Has the RDP listening port been changed? Can you not rdp internally / externally or both? Is the firewall on (i know, stupid question, but it will prevent RDP if exceptions are not configured while on.)

Chris Clancy, EnCE
Miles Technologies
clancy@4miles.com

 

[itsp1965]

No these are good questions Chris
1. I thought at first it could be firewall related, but connected to another server on the same segment and ran remote desktop from there and still no dice
2. The RDP port it is listening has not been modified (uses default 3389)

I found this article on MS KB site, although I haven't run into these scenarios specifically, it might need further investigation (usually users would contact me immediately after reboot)

http://support.microsoft.com/kb/826139/en-us

 

[NJForensics]

I would try telnetting to the internal ip address of the server on 3389 to establish if it is a traffic flow problem or if it a MSTSC problem.

Chris Clancy, EnCE
Miles Technologies
clancy@4miles.com