Stop and Start Terminal Services

[Guest Noah]

I have a x64 2003 sp2 server that is not responding to Terminal Services

Admin connections. I have been trying to restart the terminal services.

They are grayed out and when i use a net stop command i get errors. Any

way to stop and restart these services without a reboot?

 

Thanks

[Guest TP]

Re: Stop and Start Terminal Services

 

No.

 

-TP

 

Noah wrote:

> I have a x64 2003 sp2 server that is not responding to Terminal

> Services Admin connections. I have been trying to restart the

> terminal services. They are grayed out and when i use a net stop

> command i get errors. Any way to stop and restart these services

> without a reboot?

>

> Thanks

[Guest Noah]

Re: Stop and Start Terminal Services

 

So a reboot is the only fix for this problem?

 

 

 

TP wrote:

> No.

>

> -TP

>

> Noah wrote:

>> I have a x64 2003 sp2 server that is not responding to Terminal

>> Services Admin connections. I have been trying to restart the

>> terminal services. They are grayed out and when i use a net stop

>> command i get errors. Any way to stop and restart these services

>> without a reboot?

>> Thanks

[Guest Vera Noest [MVP]]

Re: Stop and Start Terminal Services

 

Yes.

But before you do that I'd check some things.

Is the server listening on port 3389? Check with "netstat -an" in

a command window on the console.

Can you establish an rdp session

to the server from the console of the server itself?

Are there any

warnings or errors in the EventLog?

 

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

Noah <noah@carpathiahost.com> wrote on 20 sep 2007 in

microsoft.public.windows.terminal_services:

> So a reboot is the only fix for this problem?

>

>

>

> TP wrote:

>> No.

>>

>> -TP

>>

>> Noah wrote:

>>> I have a x64 2003 sp2 server that is not responding to

>>> Terminal Services Admin connections. I have been trying to

>>> restart the terminal services. They are grayed out and when i

>>> use a net stop command i get errors. Any way to stop and

>>> restart these services without a reboot?

>>> Thanks

[Guest paulc]

Re: Stop and Start Terminal Services

 

Well, if you know the service name to get the PID, you can use PSKILL (get

it here:

http://www.microsoft.com/technet/sysinternals/Processesandthreadsutilities.mspx?wt.svl=featured).

Works great if you need to kill a process on a server that for some reason

you can't or don't want to reboot.

 

 

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

news:Xns99B1DA2065BDAveranoesthemutforsse@207.46.248.16...

> Yes.

> But before you do that I'd check some things.

> Is the server listening on port 3389? Check with "netstat -an" in

> a command window on the console.

> Can you establish an rdp session

> to the server from the console of the server itself?

> Are there any

> warnings or errors in the EventLog?

>

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> Noah <noah@carpathiahost.com> wrote on 20 sep 2007 in

> microsoft.public.windows.terminal_services:

>

>> So a reboot is the only fix for this problem?

>>

>>

>>

>> TP wrote:

>>> No.

>>>

>>> -TP

>>>

>>> Noah wrote:

>>>> I have a x64 2003 sp2 server that is not responding to

>>>> Terminal Services Admin connections. I have been trying to

>>>> restart the terminal services. They are grayed out and when i

>>>> use a net stop command i get errors. Any way to stop and

>>>> restart these services without a reboot?

>>>> Thanks

[Guest Vera Noest [MVP]]

Re: Stop and Start Terminal Services

 

The Terminal Services service is an integrated part of the core OS,

that's why it can't be stopped or restarted as most other services.

 

I would *not* recommend killing it. Chances are that you can't

restart it and that you put your server in an unstable state.

 

278657 - Terminal Services Cannot Be Manipulated

http://support.microsoft.com/?kbid=278657

_________________________________________________________

Vera Noest

MCSE, CCEA, Microsoft MVP - Terminal Server

TS troubleshooting: http://ts.veranoest.net

___ please respond in newsgroup, NOT by private email ___

 

"paulc" <paulc@mmcwm.com> wrote on 20 sep 2007 in

microsoft.public.windows.terminal_services:

> Well, if you know the service name to get the PID, you can use

> PSKILL (get it here:

> http://www.microsoft.com/technet/sysinternals/Processesandthreads

> utilities.mspx?wt.svl=featured). Works great if you need to kill

> a process on a server that for some reason you can't or don't

> want to reboot.

>

>

> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

> in message

> news:Xns99B1DA2065BDAveranoesthemutforsse@207.46.248.16...

>> Yes.

>> But before you do that I'd check some things.

>> Is the server listening on port 3389? Check with "netstat -an"

>> in a command window on the console.

>> Can you establish an rdp session

>> to the server from the console of the server itself?

>> Are there any

>> warnings or errors in the EventLog?

>>

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting: http://ts.veranoest.net

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> Noah <noah@carpathiahost.com> wrote on 20 sep 2007 in

>> microsoft.public.windows.terminal_services:

>>

>>> So a reboot is the only fix for this problem?

>>>

>>>

>>>

>>> TP wrote:

>>>> No.

>>>>

>>>> -TP

>>>>

>>>> Noah wrote:

>>>>> I have a x64 2003 sp2 server that is not responding to

>>>>> Terminal Services Admin connections. I have been trying to

>>>>> restart the terminal services. They are grayed out and when

>>>>> i use a net stop command i get errors. Any way to stop and

>>>>> restart these services without a reboot?

>>>>> Thanks

[Guest TP]

Re: Stop and Start Terminal Services

 

I agree with Vera's comments.

 

I would add that this situation occurs sometimes when the

server is restarted for some reason (for example, an update),

but the restart fails. TS is disabled during the shutdown

process but is not re-enabled when it is aborted.

 

The result is a server that appears to be functioning fine,

you can access its files remotely, use IIS, etc., but not

connect to it via RDP.

 

-TP

 

Noah wrote:

> So a reboot is the only fix for this problem?

>

[Guest paulc]

Re: Stop and Start Terminal Services

 

Oops. Thanks, Vera. I stand corrected. (and very happy I've never

'pskilled' a TS service. :) )

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

news:Xns99B1E6AB96267veranoesthemutforsse@207.46.248.16...

> The Terminal Services service is an integrated part of the core OS,

> that's why it can't be stopped or restarted as most other services.

>

> I would *not* recommend killing it. Chances are that you can't

> restart it and that you put your server in an unstable state.

>

> 278657 - Terminal Services Cannot Be Manipulated

> http://support.microsoft.com/?kbid=278657

> _________________________________________________________

> Vera Noest

> MCSE, CCEA, Microsoft MVP - Terminal Server

> TS troubleshooting: http://ts.veranoest.net

> ___ please respond in newsgroup, NOT by private email ___

>

> "paulc" <paulc@mmcwm.com> wrote on 20 sep 2007 in

> microsoft.public.windows.terminal_services:

>

>> Well, if you know the service name to get the PID, you can use

>> PSKILL (get it here:

>> http://www.microsoft.com/technet/sysinternals/Processesandthreads

>> utilities.mspx?wt.svl=featured). Works great if you need to kill

>> a process on a server that for some reason you can't or don't

>> want to reboot.

>>

>>

>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

>> in message

>> news:Xns99B1DA2065BDAveranoesthemutforsse@207.46.248.16...

>>> Yes.

>>> But before you do that I'd check some things.

>>> Is the server listening on port 3389? Check with "netstat -an"

>>> in a command window on the console.

>>> Can you establish an rdp session

>>> to the server from the console of the server itself?

>>> Are there any

>>> warnings or errors in the EventLog?

>>>

>>> _________________________________________________________

>>> Vera Noest

>>> MCSE, CCEA, Microsoft MVP - Terminal Server

>>> TS troubleshooting: http://ts.veranoest.net

>>> ___ please respond in newsgroup, NOT by private email ___

>>>

>>> Noah <noah@carpathiahost.com> wrote on 20 sep 2007 in

>>> microsoft.public.windows.terminal_services:

>>>

>>>> So a reboot is the only fix for this problem?

>>>>

>>>>

>>>>

>>>> TP wrote:

>>>>> No.

>>>>>

>>>>> -TP

>>>>>

>>>>> Noah wrote:

>>>>>> I have a x64 2003 sp2 server that is not responding to

>>>>>> Terminal Services Admin connections. I have been trying to

>>>>>> restart the terminal services. They are grayed out and when

>>>>>> i use a net stop command i get errors. Any way to stop and

>>>>>> restart these services without a reboot?

>>>>>> Thanks

[Guest Noah]

Re: Stop and Start Terminal Services

 

Thanks for the help guys. I was just a little confused as to WHY you

could not stop and start the services. As it is a reboot fixed the issue

and the system is running just fine. Thank you for all the help and the

informative links.

 

 

 

paulc wrote:

> Oops. Thanks, Vera. I stand corrected. (and very happy I've never

> 'pskilled' a TS service. :) )

> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message

> news:Xns99B1E6AB96267veranoesthemutforsse@207.46.248.16...

>> The Terminal Services service is an integrated part of the core OS,

>> that's why it can't be stopped or restarted as most other services.

>>

>> I would *not* recommend killing it. Chances are that you can't

>> restart it and that you put your server in an unstable state.

>>

>> 278657 - Terminal Services Cannot Be Manipulated

>> http://support.microsoft.com/?kbid=278657

>> _________________________________________________________

>> Vera Noest

>> MCSE, CCEA, Microsoft MVP - Terminal Server

>> TS troubleshooting: http://ts.veranoest.net

>> ___ please respond in newsgroup, NOT by private email ___

>>

>> "paulc" <paulc@mmcwm.com> wrote on 20 sep 2007 in

>> microsoft.public.windows.terminal_services:

>>

>>> Well, if you know the service name to get the PID, you can use

>>> PSKILL (get it here:

>>> http://www.microsoft.com/technet/sysinternals/Processesandthreads

>>> utilities.mspx?wt.svl=featured). Works great if you need to kill

>>> a process on a server that for some reason you can't or don't

>>> want to reboot.

>>>

>>>

>>> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote

>>> in message

>>> news:Xns99B1DA2065BDAveranoesthemutforsse@207.46.248.16...

>>>> Yes.

>>>> But before you do that I'd check some things.

>>>> Is the server listening on port 3389? Check with "netstat -an"

>>>> in a command window on the console.

>>>> Can you establish an rdp session

>>>> to the server from the console of the server itself?

>>>> Are there any

>>>> warnings or errors in the EventLog?

>>>>

>>>> _________________________________________________________

>>>> Vera Noest

>>>> MCSE, CCEA, Microsoft MVP - Terminal Server

>>>> TS troubleshooting: http://ts.veranoest.net

>>>> ___ please respond in newsgroup, NOT by private email ___

>>>>

>>>> Noah <noah@carpathiahost.com> wrote on 20 sep 2007 in

>>>> microsoft.public.windows.terminal_services:

>>>>

>>>>> So a reboot is the only fix for this problem?

>>>>>

>>>>>

>>>>>

>>>>> TP wrote:

>>>>>> No.

>>>>>>

>>>>>> -TP

>>>>>>

>>>>>> Noah wrote:

>>>>>>> I have a x64 2003 sp2 server that is not responding to

>>>>>>> Terminal Services Admin connections. I have been trying to

>>>>>>> restart the terminal services. They are grayed out and when

>>>>>>> i use a net stop command i get errors. Any way to stop and

>>>>>>> restart these services without a reboot?

>>>>>>> Thanks

>

>