• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 615
  • Last Modified:

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.
1 Solution
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.
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.
Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

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.

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now