Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

can not stop, start, or restart service

Status
Not open for further replies.

bookouri

IS-IT--Management
Feb 23, 2000
1,464
US
I just ran windows update and rebooted a windows 2000 server domain member server. When the server came back up everything looked normal. But then i found that we can not remote to it using terminal services. When I looked at the terminal services service, it claims to be started, and the terminal services manager seems to work.. disconnect, reset session and things like that.. but... the start, stop, restart options are grayed out on the terminal services service. It will probably clear up if i reboot again, but Ive already turned the users loose again... Ive never run into a service that i could not stop or at least restart. Is there a "manual" way to stop and start the terminal services service? or any other services for that matter. I seem to remember seeing command lines for that sort of thing.

thanks for any suggestions
 
I think the command line for stopping and starting service is net stop service and net start service where service = whatever service you want.
 
Terminal services is like that by design. The service cannot be stopped or restarted from within Windows.
 
Copy this into a batch file. It works, but you will not see it happen immediately. It can take up to 15 minutes to work on my network...

net stop TermServLicensing
sleep 5
net start TermServLicensing

I have this batch file setup to run as a scheduled task every night. Seems to help things along quite nicely.

e-mail me at ddraper at igalaxy dot net
 
You shouldn't have to restart TS licensing every day.

bookouri, what is the error that you get when you try to connect to the TS?
 
I just get a generic "cannot connect
remote connections may not be enabled" kind of error on the client trying to connect. There are no errors logged on the server.

 
I am aware that it is not necessary to restart on a daily basis, but when the doctor walks in and is very unhappy that he can't log his citrix client in, he really does not want to wait the 15 minutes for the TSL to restart, so I simply head the problem off at the pass automatically.

I am aware that TSL in 2K is really not as good as 2K3, either, but there you are... Many TS problems fixed in 2K3.

e-mail me at ddraper at igalaxy dot net
 
That's interesting though. I never noticed that you can not start and stop terminal services service, but I looked at other servers and they're all like that... seems kind of odd.. but it IS windows...<G>

 
The service could be corrupted. Have you tried uninstalling TS, rebooting, reinstalling TS and rebooting again?
 
No, that's my final solution, If I havnt figured anything out by this afternoon, it'll mean kicking all the users off and re-installing terminal services/rebooting... I was mainly interested in that business about not being able to stop and restart the terminal services service.. i had just never seen that on any other service...

 
There's a KB article on that behavior. A quick google search should bring it up. But there isn't much more in the article than what I said...it's by design ;-)
 
go figure...<G>

anyway after another uninstall reboot, reinstall reboot, terminal services is now working again...

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top