Remote Desktop Cannot Connect To Windows Server 2003 After Server Reboot

The RD won't connect after the server got rebooted.  We just updated the server with security updates from MS yesterday...

The Terminal server service is started.
I have checked the remote setting in my computer's property is checked.
My user name is in the allowed user list.
The listening port did not change.
No error log in system.

It just happened after reboot.  Anything I missed checking?

This happened before.  we managed to make the RD work by calling the on site support person to log into the server physically/directly and then the RD will work after the support person logged in.  BUT it didn't work this time.
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.

Hi henrychang99,

windows firewall isnt enabled is it? no ther firewalls etc installed

how is terminal services installed   admin or remote mode   do you have licensing set up

Reboot one more time.  I had this happen to me after some patching a while back.

If you still have problems let us know.

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
brwwigginsIT ManagerCommented:
I did all the security updates from MS this week on some of my servers and didn't have any problems with RD...if that helps any.
Cloud Class® Course: Python 3 Fundamentals

This course will teach participants about installing and configuring Python, syntax, importing, statements, types, strings, booleans, files, lists, tuples, comprehensions, functions, and classes.

Security updates can sometime turn on the windows firewall. As Jay Jay said turn of the firewall and see if you can term into it
henrychang99Author Commented:
I did not install this server, so I don't know what mode the Terminal Service is in installed.  Is there a way to check it?  

The Terminal Server itself is not installed (checked from the control panel).

The windows firewall is not running.  (When I try to check from the control panel, a message says some other app may be using NAT translate or some sort...)

We are rebooting it again now.
henrychang99Author Commented:
The reboot worked.  We have no clue what went wrong with the first reboot.  

Thanks guys.
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
Windows Server 2003

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.