henrychang99
asked on
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.
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
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.
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
ASKER
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.
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.
ASKER
The reboot worked. We have no clue what went wrong with the first reboot.
Thanks guys.
Thanks guys.
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
Cheers!