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

Windows 2003 remote desktop connection issue

Hi Experts,

I tried to reboot a few servers remotely using remote desktop. Some how the reboot command failed and i am not able to access the servers using remote desktop anymore. I know rebooting the servers resovles the issue but the servers are running critical applications which do not allow me to reboot the servers as and when I want. I tried to kill svchost.exe listening to port 3389 and restart Terminal Services. But it still doesnt allow me to connect. Your help is greatly appreciated. Thanks.

FYI, the servers are IIS servers which must be up and running all the time.
0
chenshy
Asked:
chenshy
1 Solution
 
gregwestmorelandCommented:
If you can log into the server, try disabling IPSEC and Windows Firewall upon boot up, by going into the properties of each service and setting on boot up to disable. . Reboot. Once system has rebooted, then try a remote reboot.
0
 
chenshyAuthor Commented:
Greqestmoreland,

As mentioned, i am not able to reboot the servers as they are hosting critical applications.... do you have other ways to resolve this issue?
0
 
Jay_Jay70Commented:
you have no option other than rebooting twice with terminal services most of the time, especially after windows updates......unless you have a remote access card available for remote management....

when i do server reboots i now cater for enough time to take it out twice!
0
 
65tdRetiredCommented:
When you get a chance to reboot, follow the procedure in the MS article, has fixed RDP issues on our network even though we did not get the exact error listed, got server could not be on the network or busy.


http://support.microsoft.com/kb/323497
0
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.

Join & Write a Comment

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

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