Terminal Server Service does not allow stop/start/pause

[Thierry F. [MS MVP]]

Hi,

I just have a problem and I cannot find a solution by myself. I cannot
control the terminal server service. When I use the MMC to control the
services, all the buttons are grayed (only for RPC Server, Logging and
Terminal Services). The service is started (listening on all interfaces on
port 3389). When I use the terminal server management console, I see only
one RDP listener (I was used to see two listeners). When I try to connect to
the Terminal Server, I see a very quick line (maybe the server try to create
a new listener) which desappear). I don't know why it does not work (I
reinstalled the service with no success). I dont know how I can troubleshoot
this problem (there is no event generated in the event logs). Any idea will
be greatly appreciated!

 

[Vera Noest [MVP]]

That you cannot change the terminal server service is by design.
Check:

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

That you have only one listener is a bit strange (if you didn't
change the number of listeners).
And even with one listener, it should allow a connection.

When you try to connect, do you ever get a logon dialogue box, or
don't you even get that far? Have you tried to delete the rdp-tcp
connection completely and create a new one?

 

[Thierry F. [MS MVP]]

Hi Vera and thanks for your answer. The server was fine when I left it (two
weeks ago). The customer has probably made something ;-) I guess a
WindowsUpdate was made (I uninstalled all the most recent updates just for
try to find a solution).

The port is listening on the 3389 port. I can use telnet server 3389 and
connect to the server (just establish a socket connection). If I use the TSE
client (from Windows XP), I get a error (the connection cannot be made for
security or something related to security). I never seen a problem like this
before! I'll open a case to Microsoft tomorrow to try to find an answer.

 

[Matthew Harris [MVP]]

Is this system in remote admin mode or application mode?

Are there any eventlog messages that would indicate a
problem?

-M

-----Original Message-----
Hi Vera and thanks for your answer. The server was fine when I left it (two
weeks ago). The customer has probably made something ;-) I guess a
WindowsUpdate was made (I uninstalled all the most recent updates just for
try to find a solution).

The port is listening on the 3389 port. I can use telnet server 3389 and
connect to the server (just establish a socket connection). If I use the TSE
client (from Windows XP), I get a error (the connection cannot be made for
security or something related to security). I never seen a problem like this
before! I'll open a case to Microsoft tomorrow to try to find an answer.

--
Thierry Frache [MVP Windows Servers]
http://www.microsoft-mvp.com
"Vera Noest [MVP]" <[email protected]> a écrit dans le
message de news: [email protected]...

That you cannot change the terminal server service is by design.
Check:

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

That you have only one listener is a bit strange (if you didn't
change the number of listeners).
And even with one listener, it should allow a connection.

When you try to connect, do you ever get a logon dialogue box, or
don't you even get that far? Have you tried to delete the rdp-tcp
connection completely and create a new one?

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---

.

 

[Thierry F. [MS MVP]]

There is no TSE related event. The server is in administration mode.

--
Thierry Frache [MVP Windows Servers]
http://www.microsoft-mvp.com
"Matthew Harris [MVP]" <[email protected]> a écrit dans le message
de [email protected]...
Is this system in remote admin mode or application mode?

Are there any eventlog messages that would indicate a
problem?

-M

-----Original Message-----
Hi Vera and thanks for your answer. The server was fine when I left it (two
weeks ago). The customer has probably made something ;-) I guess a
WindowsUpdate was made (I uninstalled all the most recent updates just for
try to find a solution).

The port is listening on the 3389 port. I can use telnet server 3389 and
connect to the server (just establish a socket connection). If I use the TSE
client (from Windows XP), I get a error (the connection cannot be made for
security or something related to security). I never seen a problem like this
before! I'll open a case to Microsoft tomorrow to try to find an answer.

--
Thierry Frache [MVP Windows Servers]
http://www.microsoft-mvp.com
"Vera Noest [MVP]" <[email protected]> a écrit dans le
message de news: [email protected]...

That you cannot change the terminal server service is by design.
Check:

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

That you have only one listener is a bit strange (if you didn't
change the number of listeners).
And even with one listener, it should allow a connection.

When you try to connect, do you ever get a logon dialogue box, or
don't you even get that far? Have you tried to delete the rdp-tcp
connection completely and create a new one?

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---

.

 

[Vera Noest [MVP]]

Since you mention something about a security error, have you seen
this article:

329896 - Error Message: Because of a Security Error, the Client Could
Not Connect to the Terminal Server
http://support.microsoft.com/?kbid=329896

 

[Thierry F. [MS MVP]]

Thanks Very. I'll try it soon.

Since you mention something about a security error, have you seen
this article:

329896 - Error Message: Because of a Security Error, the Client Could
Not Connect to the Terminal Server
http://support.microsoft.com/?kbid=329896

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup ---