Windows Forum

Ask something
Discussion Locked

After reboot no Terminal Sessions

0 helpful
3 replies

by yadavshashi

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,

We are running 2 Windows 2003 Terminal servers with Windows load balancing. Of course it is running application like office, Adobe reader, Macromedia etc. When ever servers gets reboot they do not accept any terminal session unless you give them again a remote reboot. You can ping the servers all services are running nothing in event viewer but it simply does not except any terminal session.
The standard reasons:
1.Remote connection might not be enables.
2.Computer too busy to accept connections.
3.Network problems are preventing the connection.

Does anybody know what is the problem and how fix this issue.

Thanx

Shashi

3 replies

by master3bs

Open up the Services (you can find this on the start menu under administartive options or in the control panel in the same place. Easiest way though is to Click Start->Run, type "services.msc" (without quotation marks) in the open box and click OK. )

Locate and Double click the service "Terminal Services".

Click on the tab "General "; make sure the "Startup Type" is "Automatic". Then, if it not started then click the button "Start" under "Service Status" to start the service.

Check and see if that works. If not, open up the service again and do the following:

-----

Click on the Log On tab, then make sure the option "Local System account" is selected and the option "Allow service to interact with desktop" is unchecked.

Then check if this service has been enabled on the listed Hardware Profile. If not, click the Enable button to enable it.

Hope that works for you!

by yadavshashi

Thanks Master3bs for your suggestion,Sorry I forget to mention that it does not happen after every reboot. Both servers gets every day a reboot to keep caching as low as possible.

Shashi

This discussion is closed to new replies.