RDP cannot connect after server restarts. Server is performing fine just cant connect via RDP
Hi Everyone,
First time post. Basically, most of my sites I look after I have to update servers remotely due to COB. I have noticed lately with a few of my sites after I perform the updates and schedule a restart, that I cannot get back into the server via RDP. I then travel to the site the next morning to make sure everything is running fine for the users, and it all is. All data shares, networked software, everything that the server needs to do is fine, except for RDP. I can VNC or use the console, to restart the server and after a restart the RDP service comes good again.
The servers it has been happening on are Windows Small Business Servers, 2003, R2. All updated with the most recent critical updates. It does not have the latest Remote desktop software but everything else is up to date.
The thing I have also noticed is that, even if its not a windows update, for example completing backup exec updates, it still happens. The only common factor I can see is that Im trying to restart during a terminal session of the console. Whether or not this is the issue. I havent been able to test a restart after updates whilst Im physically onsite.
Any Advice would be great on this subject.
First time post. Basically, most of my sites I look after I have to update servers remotely due to COB. I have noticed lately with a few of my sites after I perform the updates and schedule a restart, that I cannot get back into the server via RDP. I then travel to the site the next morning to make sure everything is running fine for the users, and it all is. All data shares, networked software, everything that the server needs to do is fine, except for RDP. I can VNC or use the console, to restart the server and after a restart the RDP service comes good again.
The servers it has been happening on are Windows Small Business Servers, 2003, R2. All updated with the most recent critical updates. It does not have the latest Remote desktop software but everything else is up to date.
The thing I have also noticed is that, even if its not a windows update, for example completing backup exec updates, it still happens. The only common factor I can see is that Im trying to restart during a terminal session of the console. Whether or not this is the issue. I havent been able to test a restart after updates whilst Im physically onsite.
Any Advice would be great on this subject.
Asked:
Who is Participating?
Though I have never heard of it with non-Microsoft updates, it is a very well known issue. After several different Windows updates that require a reboot, but not all updates, all services work fine, except RDP. It seems that service is not re-initialized until after a second reboot. I have yet to hear of an explanation or solution. It doesn't usually happen that often. If it did you could schedule a reboot for 15 minutes later, or create a back door with VNC, LogMeIn, or through a second server/PC and use the shutdown command.
Hi RobWill,
cheers for the reply. I have read a post that said to schedule the same restart via a shutdown command. I will use this as a last resort but it just seems like a pain of a workaround. Do you think there is a chance that the server actually isnt restarting? Could it be possible that because I am on the console remotely that the RDP session/service is crashing and the server sits there performing normally?
cheers for the reply. I have read a post that said to schedule the same restart via a shutdown command. I will use this as a last resort but it just seems like a pain of a workaround. Do you think there is a chance that the server actually isnt restarting? Could it be possible that because I am on the console remotely that the RDP session/service is crashing and the server sits there performing normally?
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
-
Course of the Month7 days, 10 hours left to enrollMonitoring and Operating a Private Cloud with System Center 2012 R2 273 lessons
Definitely a possibility, but it is easy to check. Look at the "system" event logs at the time after the reboot should have taken place. You should see the various services starting up.
I agree it is a pain in the neck. It will not happen very often. I find never more than 2 times a year on a given server, but it always happens when you least expect it. Jay_Jay70, a master of Server 2003 and AD here on Experts-Exchange, pointed out this problem to me a year ago. He manages hundreds of servers and says it is quite common.