Remote desktop disconnected

[Guest John Hall]

Recently I have been unable to connect to my Windows 2000 server, which is

running Terminal Services in remote administration mode. I just get a

dialog:

---------------------------

Remote Desktop Disconnected

---------------------------

This computer can't connect to the remote computer.

 

Try connecting again. If the problem continues, contact the owner of the

remote computer or your network administrator.

---------------------------

OK Help

---------------------------

 

The client is Windows XP. Looking on the server, the Terminal Services

service is running, except its start and stop controls are greyed out. There

are no events logged in the event log. If I analyze the network traffic, a

TCP/IP connection is made on port 3389, but after a few packets the server

disconnects.

 

The only recent change to the server has been the installation of VmWare

Server, so perhaps this is relevant.

 

Any ideas? I'm not even sure how to go about debugging the problem any

further.

 

Regards,

John

[Guest Soo Kuan Teo [MSFT]]

Re: Remote desktop disconnected

 

Does this happen to all Client machines?

Can you run TSAdmin.exe and check if the Listener is not in 'down' state?

Can you go to the console of your server, open mstsc.exe, connect to itself.

Can you create the ts session?

Thanks

Soo Kuan

 

 

 

--

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

 

"John Hall" <john-news5@camtechconsultants.com> wrote in message

news:21ed.4759525d.d1c71@mail.cambridgetechgroup.com...

> Recently I have been unable to connect to my Windows 2000 server, which is

> running Terminal Services in remote administration mode. I just get a

> dialog:

> ---------------------------

> Remote Desktop Disconnected

> ---------------------------

> This computer can't connect to the remote computer.

>

> Try connecting again. If the problem continues, contact the owner of

> the remote computer or your network administrator.

> ---------------------------

> OK Help

> ---------------------------

>

> The client is Windows XP. Looking on the server, the Terminal Services

> service is running, except its start and stop controls are greyed out.

> There are no events logged in the event log. If I analyze the network

> traffic, a TCP/IP connection is made on port 3389, but after a few packets

> the server disconnects.

>

> The only recent change to the server has been the installation of VmWare

> Server, so perhaps this is relevant.

>

> Any ideas? I'm not even sure how to go about debugging the problem any

> further.

>

> Regards,

> John

>

[Guest John Hall]

Re: Remote desktop disconnected

 

"Soo Kuan Teo [MSFT]" <sookuant@online.microsoft.com> wrote in message

news:<#aG7QP1OIHA.5980@TK2MSFTNGP04.phx.gbl>...

> Does this happen to all Client machines?

 

Yes.

> Can you run TSAdmin.exe and check if the Listener is not in 'down' state?

 

It's running.

> Can you go to the console of your server, open mstsc.exe, connect to

> itself.

> Can you create the ts session?

 

When I tried to connect I got a message along the lines of "Due to a Network

error, the client was disconnected".

 

The interesting thing is that the Services control panel shows the service

as running, but the controls to start and stop it are disabled (grayed out).

 

Regards,

John

[Guest Soo Kuan Teo [MSFT]]

Re: Remote desktop disconnected

 

John,

In Windows 2000 server, the TS service cannot be stopped as normal

windows services, it is by-design.

can you verify the following step:

Can you go to the console of your Windows 2000 server, open mstsc.exe,

connect to itself. Can you create the ts session? The error you described

previously mostly occur if the ts session is created remotely. I just want

to make sure if you can create the ts session locally.

 

You mentioned that this issue occurs after you installed VMWare.

Can you please verify with VMWare support that Windows 2000 Server (what

service pack?) is the supported host OS for the VMWare version and SKU you

installed? It is also a good time to share your issues with them for their

suggestions.

 

Thanks

Soo Kuan

 

 

 

 

 

 

--

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

 

"John Hall" <john-news5@camtechconsultants.com> wrote in message

news:31a2.475eb0ee.7f2c@mail.cambridgetechgroup.com...

> "Soo Kuan Teo [MSFT]" <sookuant@online.microsoft.com> wrote in message

> news:<#aG7QP1OIHA.5980@TK2MSFTNGP04.phx.gbl>...

>> Does this happen to all Client machines?

>

> Yes.

>

>> Can you run TSAdmin.exe and check if the Listener is not in 'down' state?

>

> It's running.

>

>> Can you go to the console of your server, open mstsc.exe, connect to

>> itself.

>> Can you create the ts session?

>

> When I tried to connect I got a message along the lines of "Due to a

> Network

> error, the client was disconnected".

>

> The interesting thing is that the Services control panel shows the service

> as running, but the controls to start and stop it are disabled (grayed

> out).

>

> Regards,

> John

>

>