problem with Terminal Services on Vista

[Guest Matt Hickman]

We recently ran across a problem where a Vista PC no longer responded

to Remote Desktop requests. On the PC in question, we stopped the

local firewall, checked the settings in remote properties, checked

that terminal services is running and looked at the registry under:

 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\

Control\Terminal Server\WinStations\RDP-Tcp

 

Everything looks like it should, and does not seem to have changed.

 

At he the command line, the following finds nothing:

netstat -ano | find "3389"

 

This indicates that there are no programs listening on port 3389. (I

am assuming that netstat would find a program listening on port 3389

even if a firewall blocked it-- Am I right?)

 

Any ideas about what else to check? What kind of event log entries to

look for? Anyway to look at svhost.exe and see if it is running

terminal services?

 

Thanks for any help,

 

--

Matt Hickman

[Guest Soo Kuan Teo [MSFT]]

Re: problem with Terminal Services on Vista

 

what error do you get when you try to connect to the Vista remotely?

Is "Terminal Services" (TermService) service running?

Can you share the output of running Qwinsta.exe locally?

 

--

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

 

"Matt Hickman" <hemojr@gmail.com> wrote in message

news:3cd8ff1a-ed33-4024-831e-ec49b1d2f687@y5g2000hsf.googlegroups.com...

> We recently ran across a problem where a Vista PC no longer responded

> to Remote Desktop requests. On the PC in question, we stopped the

> local firewall, checked the settings in remote properties, checked

> that terminal services is running and looked at the registry under:

>

> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\

> Control\Terminal Server\WinStations\RDP-Tcp

>

> Everything looks like it should, and does not seem to have changed.

>

> At he the command line, the following finds nothing:

> netstat -ano | find "3389"

>

> This indicates that there are no programs listening on port 3389. (I

> am assuming that netstat would find a program listening on port 3389

> even if a firewall blocked it-- Am I right?)

>

> Any ideas about what else to check? What kind of event log entries to

> look for? Anyway to look at svhost.exe and see if it is running

> terminal services?

>

> Thanks for any help,

>

> --

> Matt Hickman

[Guest Matt Hickman]

Re: problem with Terminal Services on Vista

 

On Feb 1, 8:12 pm, "Soo Kuan Teo [MSFT]"

<sooku...@online.microsoft.com> wrote:

> what error do you get when you try to connect to the Vista remotely?

This computer cannot connect to the remote compouter

> Is "Terminal Services" (TermService) service running?

yes

> Can you share the output of running Qwinsta.exe locally?

C:\Windows\system32>Qwinsta.exe

SESSIONNAME USERNAME ID STATE TYPE

DEVICE

0 Disc

>console myuserID 1 Active

 

--

Matt Hickman

[Guest Soo Kuan Teo [MSFT]]

Re: problem with Terminal Services on Vista

 

Interesting. qwinsta.exe output does not list listener.

Can you double check if remote desktop is enabled? run sysdm.cpl, goto

remote tab.

 

 

--

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

 

"Matt Hickman" <hemojr@gmail.com> wrote in message

news:fa61dab8-b8ea-4e57-a3c6-6118c2c35366@s37g2000prg.googlegroups.com...

On Feb 1, 8:12 pm, "Soo Kuan Teo [MSFT]"

<sooku...@online.microsoft.com> wrote:

> what error do you get when you try to connect to the Vista remotely?

This computer cannot connect to the remote compouter

> Is "Terminal Services" (TermService) service running?

yes

> Can you share the output of running Qwinsta.exe locally?

C:\Windows\system32>Qwinsta.exe

SESSIONNAME USERNAME ID STATE TYPE

DEVICE

0 Disc

>console myuserID 1 Active

 

--

Matt Hickman

[Guest Flemming Bach]

Re: problem with Terminal Services on Vista

 

Hi.

I have the same problem on a Windows 2008 DataCenter Server.

I have tried to setup a new connection with Terminal Services Configuration,

change the port for the service, telnet to the port both on localhost and

from a computer on the same network.

 

I have narrowed the problem down to that the server is not listening on the

port for Terminal Services.

I have checked for the right port in regedit before I used "netstat -an |

find "<portnumber>".

I tried qwinsta.exe, no listener is found.

 

Any ideas ?

 

Seems like reinstall again is the only solution.

I have already reinstalled the system 5 times during a week and used a week

more on finding a solution on the problem.

 

---------

 

The server is a HP ProLiant DL-385 G1 model.

It is installed with MS Virtual Server 2005 SP1 and VM-ware Server.

I have had TS Gateway installed also, but removed it, when RDP stopped

working.

 

Hope you can help me.

Regards,

 

Flemming Bach,

Sima.dk

[Guest Ratnesh Yadav [MSFT]]

Re: problem with Terminal Services on Vista

 

Check following link, on "How to change Terminal Servers's listening port"

http://support.microsoft.com/kb/187623

 

Ratnesh

 

"Flemming Bach" <Flemming Bach@discussions.microsoft.com> wrote in message

news:636D672A-725E-4D82-82BB-9DE8C070FB1A@microsoft.com...

> Hi.

> I have the same problem on a Windows 2008 DataCenter Server.

> I have tried to setup a new connection with Terminal Services

> Configuration,

> change the port for the service, telnet to the port both on localhost and

> from a computer on the same network.

>

> I have narrowed the problem down to that the server is not listening on

> the

> port for Terminal Services.

> I have checked for the right port in regedit before I used "netstat -an |

> find "<portnumber>".

> I tried qwinsta.exe, no listener is found.

>

> Any ideas ?

>

> Seems like reinstall again is the only solution.

> I have already reinstalled the system 5 times during a week and used a

> week

> more on finding a solution on the problem.

>

> ---------

>

> The server is a HP ProLiant DL-385 G1 model.

> It is installed with MS Virtual Server 2005 SP1 and VM-ware Server.

> I have had TS Gateway installed also, but removed it, when RDP stopped

> working.

>

> Hope you can help me.

> Regards,

>

> Flemming Bach,

> Sima.dk