Terminal Service restart – Windows 2003 Server

0 pts.
Tags:
Desktops
Management
Microsoft Windows
OS
Security
Servers
SQL Server
Terminal service (administrative mode) in one of our file servers time to time has problems. The server is a Windows 2003 server with SP1. When the problem occures, RDP attends to the server get: "Remote Desktop Disconnected. The client could not establish a connection to the remote computer..." error The server has no resource problem. Ping is fine. "Terminal Service" is started. No obvious terminal service related error/warning events. Does anyone know a way to restart the terminal service without reboot the server?
ASKED: October 9, 2006  2:29 AM
UPDATED: October 11, 2006  10:16 AM

Answer Wiki

Thanks. We'll let you know when a new response is added.

Hello,

Here are a couple of general possibilities for this error, 1. Network problems preventing connectivity with the terminal server.
2. Terminal server service is not running.
3. More than two consecutive RDP connections are established with the terminal server. Remember TS in Administrative Mode only supports a max of two concurrent sessions.
4. Problem resolving the DNS name of the Terminal server.

Good luck!

Discuss This Question: 2  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Eddychen
    We had checked and almostly ruled out those possibilities. 1. Network problems preventing connectivity with the terminal server. Pings' were ok. Telneting to port 3389 got reactions (abnormlly though) 2. Terminal server service is not running. Windows service management console shows that Terminal service is started. 3. More than two consecutive RDP connections are established with the terminal server. Remember TS in Administrative Mode only supports a max of two concurrent sessions. Terminal service manager shows that no active connections 4. Problem resolving the DNS name of the Terminal server. Pings to DNS name are successful. It looks like during a patching the service had been stopped or corrupted. A restart of the service is very likely to solve the problem. However, terminal servic could not be restart directly through service management console. If we can not find a way to restart the service, we will have to reboot the server.
    0 pointsBadges:
    report
  • Petroleumman
    Hello, At this point I would reboot the server first and if your problem persists, try uninstalling the most recent patch or patches to the server that you suspect may be the cause and reboot again. When working with patches I would remove each patch one at a time in the reverse order they were installed until the problem is resolved testing after each successful removal. This way you can identify the problem patch and make a record of it. Good luck!
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following