Windows NT Terminal Services not functioning on 2003 sp2

  • Thread starter Thread starter Thomas Roes
  • Start date Start date
T

Thomas Roes

L.S.

A client of mine has installed SP2 on one of there 2003 servers. From
that moment on Terminal Services is not working anymore.

I've discovered the following:

- MMC says terminal services is started BUT i cannot (start)/stop/
restart the service.
- net start/stop TermService fail with error 2182 (already started)
and 2191 (not valid)

- Eventlog does not have any messages about why terminal service is
not running

- There is no service listening on port 3389

- There is no firewall issue

- mstsc /v:localhost also does not work (The Client could not connect
to the remote computer

TCP/IP Trace shows the SYN frame followed by an RST, ACK response.

Any suggestions

Thomas Roes
There is no one at thomasr1@xs4all.nl
 
Mmm, this problem has been reported quite a few times, and I have
actually encountered it myself on one out of 15 identical servers.

The fact that you can't stop or restart the TS service is by
design, as documented here:

278657 - Terminal Services Cannot Be Manipulated
http://support.microsoft.com/?kbid=278657

So the service is running, but it's not listening on port 3389.
The only solution that I know of, and which solved my problem, is
to delete the existing rdp-tcp connection, reboot the server, and
recreate it (use all the default settings).
This must be done at the console of the server, in Terminal
Services Configuration.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

Thomas Roes <thomasr1@xs4all.nl> wrote on 18 jul 2007 in
microsoft.public.windows.terminal_services:

> L.S.
>
> A client of mine has installed SP2 on one of there 2003 servers.
> From that moment on Terminal Services is not working anymore.
>
> I've discovered the following:
>
> - MMC says terminal services is started BUT i cannot
> (start)/stop/ restart the service.
> - net start/stop TermService fail with error 2182 (already
> started) and 2191 (not valid)
>
> - Eventlog does not have any messages about why terminal service
> is not running
>
> - There is no service listening on port 3389
>
> - There is no firewall issue
>
> - mstsc /v:localhost also does not work (The Client could not
> connect to the remote computer
>
> TCP/IP Trace shows the SYN frame followed by an RST, ACK
> response.
>
> Any suggestions
>
> Thomas Roes
> There is no one at thomasr1@xs4all.nl
 
On Jul 18, 4:48 pm, "Vera Noest [MVP]" <vera.no...@remove-
this.hem.utfors.se> wrote:
> Mmm, this problem has been reported quite a few times, and I have
> actually encountered it myself on one out of 15 identical servers.
>
> The fact that you can't stop or restart the TS service is by
> design, as documented here:
>
> 278657 - Terminal Services Cannot Be Manipulatedhttp://support.microsoft.com/?kbid=278657
>
> So the service is running, but it's not listening on port 3389.
> The only solution that I know of, and which solved my problem, is
> to delete the existingrdp-tcp connection, reboot the server, and
> recreate it (use all the default settings).
> This must be done at the console of the server, in Terminal
> Services Configuration.
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> Thomas Roes <thoma...@xs4all.nl> wrote on 18 jul 2007 in
> microsoft.public.windows.terminal_services:
>
>
>
> > L.S.
>
> > A client of mine has installedSP2on one of there2003servers.
> > From that moment on Terminal Services is not working anymore.
>
> > I've discovered the following:
>
> > - MMC says terminal services is started BUT i cannot
> > (start)/stop/ restart the service.
> > - net start/stop TermService fail with error 2182 (already
> > started) and 2191 (not valid)
>
> > - Eventlog does not have any messages about why terminal service
> > is not running
>
> > - There is no service listening on port 3389
>
> > - There is no firewall issue
>
> > - mstsc /v:localhost also does not work (The Client could not
> > connect to the remote computer
>
> > TCP/IP Trace shows the SYN frame followed by an RST, ACK
> > response.
>
> > Any suggestions
>
> > Thomas Roes
> > There is no one at thoma...@xs4all.nl- Hide quoted text -
>
> - Show quoted text -

I had the same issue - probelm was resolved by re-installing sp2 at
the console. Term Services came right up after the re-install. Hope
this helps.
 
Back
Top