Terminal server does not start after reboot

[Chris Ferraro]

I am an IT consultant with servers in different envirnments running SBS2003
SP1 and Windows 2003 server SP2 and R2. I have an intermittent problem when
after server reboots. I am unable to connect to the terminal server. I am
running in remote administrator mode and when I attempt to connect I quickly
get an error saying "The client could not establish a connection to the
remote computer." If I telnet to port 3389 I am disconnected as soon as I
type anything. The problem occurs when connecting locally or remotely via
terminal services client. A reboot of the server resolves the issue

I verified that the terminal service process was listening on port 3389 by
checking netstat -aon | find "3389" and then comparing the process number to
an svchost that has terminal service related threads running in it. However,
when clicked on the RDP-Tcp (listener) and clicked reset, I got a message
saying "permission denied" and then port 3389 was no longer in use and the
RDP-Listener disappeared from the Terminal services manager. I contacted
Microsoft and they deleted all the TS related reg keys and gave me
replacement keys that completely broke the terminal server on the system
where they were applied. They did not have a KB article for this condition
and stated that removing and readding these registry keys would fix the
issue. I also have doubts about the technicians ability to understand the
issue as there was a language barrier and he created the case titled "Unable
to do local host" which in no way describes the issue. I am requesting the
case be reassigned, but was advised of a 3 hour hold time for Windows server
support. Regardless, I cannot reproduce the issue easily so there is no way
for me to prove them wrong.

I checked the event logs and found no errors.

I suspect this issue is common because

 

[Alicia Chen [MSFT]]

Re: Terminal server does not start after reboot

It seems your problem could be a race condition between the TermService
service and TermDD. This seems to happen sometimes when systems are patched
or new software is installed and the typical startup sequence changes. When
the service starts up before TermDD, the listener appears to be listening
but doesn't work. The common workaround for this is to add TermDD to the
list of dependencies in
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\DependOnService
(So the list becomes RPCSS followed by TermDD.)

Alternatively, there is another hotfix,
http://support.microsoft.com/?id=930045, but this describes a deadlock that
occurs during shutdown and from your description it seems that your server
is up and running when the connection fails.

--
Alicia Chen
This posting is provided "AS IS" with no warranties, and confers no rights.

"Chris Ferraro" <ChrisFerraro@discussions.microsoft.com> wrote in message
news:F19C9731-5C46-4D58-AA49-91F143D6F7B7@microsoft.com...
>I am an IT consultant with servers in different envirnments running SBS2003
> SP1 and Windows 2003 server SP2 and R2. I have an intermittent problem
> when
> after server reboots. I am unable to connect to the terminal server. I
> am
> running in remote administrator mode and when I attempt to connect I
> quickly
> get an error saying "The client could not establish a connection to the
> remote computer." If I telnet to port 3389 I am disconnected as soon as
> I
> type anything. The problem occurs when connecting locally or remotely via
> terminal services client. A reboot of the server resolves the issue
>
> I verified that the terminal service process was listening on port 3389 by
> checking netstat -aon | find "3389" and then comparing the process number
> to
> an svchost that has terminal service related threads running in it.
> However,
> when clicked on the RDP-Tcp (listener) and clicked reset, I got a message
> saying "permission denied" and then port 3389 was no longer in use and the
> RDP-Listener disappeared from the Terminal services manager. I contacted
> Microsoft and they deleted all the TS related reg keys and gave me
> replacement keys that completely broke the terminal server on the system
> where they were applied. They did not have a KB article for this
> condition
> and stated that removing and readding these registry keys would fix the
> issue. I also have doubts about the technicians ability to understand the
> issue as there was a language barrier and he created the case titled
> "Unable
> to do local host" which in no way describes the issue. I am requesting
> the
> case be reassigned, but was advised of a 3 hour hold time for Windows
> server
> support. Regardless, I cannot reproduce the issue easily so there is no
> way
> for me to prove them wrong.
>
> I checked the event logs and found no errors.
>
> I suspect this issue is common because

 

[Chris Ferraro]

Re: Terminal server does not start after reboot

I could see this as a possibility, but I would expect there to be a KB
article related to this if that were the case. It does seem to occur after
patches or new software installations. Please let me know if there is a
related KB article.


"Alicia Chen [MSFT]" wrote:

> It seems your problem could be a race condition between the TermService
> service and TermDD. This seems to happen sometimes when systems are patched
> or new software is installed and the typical startup sequence changes. When
> the service starts up before TermDD, the listener appears to be listening
> but doesn't work. The common workaround for this is to add TermDD to the
> list of dependencies in
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\DependOnService
> (So the list becomes RPCSS followed by TermDD.)
>
> Alternatively, there is another hotfix,
> http://support.microsoft.com/?id=930045, but this describes a deadlock that
> occurs during shutdown and from your description it seems that your server
> is up and running when the connection fails.
>
> --
> Alicia Chen
> This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Alicia Chen [MSFT]]

Re: Terminal server does not start after reboot

Hi Chris,

There is a related KB article--http://support.microsoft.com/kb/887583--but
it only applies to WS2000. If the workaround given below does not resolve
your problem, please let me know.

--
Alicia Chen
This posting is provided "AS IS" with no warranties, and confers no rights.

"Chris Ferraro" <ChrisFerraro@discussions.microsoft.com> wrote in message
news:F96461D5-6E68-41C4-A952-A874EE06A7FD@microsoft.com...
>I could see this as a possibility, but I would expect there to be a KB
> article related to this if that were the case. It does seem to occur
> after
> patches or new software installations. Please let me know if there is a
> related KB article.
>
>
> "Alicia Chen [MSFT]" wrote:
>
>> It seems your problem could be a race condition between the TermService
>> service and TermDD. This seems to happen sometimes when systems are
>> patched
>> or new software is installed and the typical startup sequence changes.
>> When
>> the service starts up before TermDD, the listener appears to be listening
>> but doesn't work. The common workaround for this is to add TermDD to the
>> list of dependencies in
>> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\TermService\DependOnService
>> (So the list becomes RPCSS followed by TermDD.)
>>
>> Alternatively, there is another hotfix,
>> http://support.microsoft.com/?id=930045, but this describes a deadlock
>> that
>> occurs during shutdown and from your description it seems that your
>> server
>> is up and running when the connection fails.
>>
>> --
>> Alicia Chen
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>