February 9, 2009 at 9:15 am
We have two quad-core Dell PowerEdge servers with Windows Server 2003 and SQL Server 2005. The servers (at a customer location) are managed via remote desktop connection. When either of these servers is rebooted, it is down for a very long time, typically 13 minutes, before a remote desktop connection can be re-established. Other similar servers, that are not running SQL Server, come back within a couple of minutes. The event log indicates that some services start up within two minutes or so of the reboot on these SQL Servers, but remote desktop connection is not possible for much longer.
In addition, even though we have configured all servers to auto login to a specific domain account, these two servers do not.
Any suggestions?
February 9, 2009 at 9:58 am
I would check the terminal services connectivity to the rebooted system. Also to check how long your server that was rebooted takes to come back online.
You can ping the server to see if it is slow while restarting by doing this
go to cmd and type ping--> ip of the server -t
when you get reply back this is when the server is back on, press Ctrl+C to exit.
Thanks!!
The_SQL_DBA
MCTS
"Quality is never an accident; it is always the result of high intention, sincere effort, intelligent direction and skillful execution; it represents the wise choice of many alternatives."
February 9, 2009 at 10:37 am
Thanks for your suggestion. The ping response came back in just over two minutes after rebooting the server, but terminal services and remote desktop connections were not present until eleven minutes later (total of 13 minutes after the reboot). What next?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply