Remote desktop not working after a reboot on Windows 2003 Server

Has anyone seen this?  I have several Windows 2003 Server machines with remote desktop enabled on them.  After a windows update and a reboot remote desktop will no longer connect.  Another reboot and everything starts working.  This is bad for the developers working from home that need to reboot a server and then they can't get back in.  Any ideas?  Widnows 2003 with SP2
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

zephyr_hex (Megan)DeveloperCommented:
do the servers have static ip addresses?
sometimes windows updates re-enable the windows firewall.  you might want to verify the firewall services is disabled.
have you checked Event Viewer to see if there are related errors?
ewest111Author Commented:
yes they all have static ip's.  If the firewall was being re-enabled by the update, why would another reboot allow remote desktop connections to start working again?
I've had this problem for ages and I've tried everything that I can think of to get it to not function.

To put it simply we've made a "Rule" in the office that no one is allowed to reboot a server unless there is  someone here to manually reboot if RDP fails to start back up.

Introducing Cloud Class® training courses

Tech changes fast. You can learn faster. That’s why we’re bringing professional training courses to Experts Exchange. With a subscription, you can access all the Cloud Class® courses to expand your education, prep for certifications, and get top-notch instructions.

ewest111Author Commented:
I'm quite sure that's not the answer the apps folks want to hear.  I was thinking about remote boot power strips to be able to reboot again remotely but those are so expensive.
Your right -- A work around solution that I've thought of but haven't implemented:

Create a Scheduled Task that Reboots the Server.

RDP to Another Local Server that has share access with the Non-Responding Server and run the Reboot App.  

If you need source code I think I have some around here somewhere for C#.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ewest111Author Commented:
yeah I would appreciate that.
This isn't exactly what you need -- but this is the logoff function that I use to log off users that leave work without logging off their PC's.

System.Diagnostics.Process.Start("shutdown -f -s -t 0");
I was looking for a solution for quite a long time - here it is:

Solution: Problem is not ISA Server it is the Terminal Services configuration on the ISA Server.
1. Open Terminal services configuration.
2. Hightlight Connections.
3. Right hand Pane right click default connection and select properties.
4. Select the network adapter Tab.
5. Make sure that Network Adapter that is selected is the Internal NIC.  It should not be configured to listen on all adapters.
6. Change and click on apply and OK
Close terminal Services manager and test RDP.

I had the same exact problem - I had to manually select the proper internal network card (one of two) - rebooted again using remote desktop - and issue resolved. Good luck.
Well, I tried the above solution (TS configuration) and now I can't get into the server with either RDC or VNC. VNC was working fine before this change.

Any reason why this would have started up all of a sudden across our network? This never happened before until about 2 weeks ago and it's affected at least 3 of our servers.
You can also do a remote shutdown from another server on the network.

shutdown /r /m \\computername /t 0
We have experienced that doing Windows updates and rebooting from a non-console RDP session can result in RDP not working upon reboot.  If you use a console session it seems to work reliably.

I have the same problem.
If I reboot the server using RDP session, after that RDP does not work, but when I reboot the server SECOND time using shutdown command (I run it from the SQL session), the RDP starts work&
It is really pain in the ass&.
This server is not running ISA. It is just Database server.

Please advice.
I found one other solution which people may wish to try.
Control Panel - Add/remove programs- Add/remove Windows components.
Find the Internet Explorer Enhanced Security Configuration.
Click Details and untick the For Administrator Groups
Thanks BPiotrowski!

I recently updated our Windows 2003 with latest patches and our Citrix PS 4.5 intermittently failed RDC after the scheduled reboot.

Terminal services configuration's Network Adapter was set to all NIC so I changed it to use the internal NIC and seem to have fixed the problem.

It's probably one of security patch that triggered this since I never had any issue prior to recent MS updates.

Thanks again for sharing!

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.

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.