Remote Desktop Not working

[Guest]

I set up Remote desktop on my Vista Ultimate machine when Vista was released.
It worked find for about a month or 2. But now When I try to get connect
from a remote location it won't connect. I have tried turning remote desktop
on and off, messed with the firewall settings, and still can not get any
sessions to connect. I doesn't seem to be going far enough to test the
creditials I am logging in with so I know thats not the problem, it simply
doesn't seem to be accepting a connection.

 

[Synapse Syndrome]

I set up Remote desktop on my Vista Ultimate machine when Vista was
released.
It worked find for about a month or 2. But now When I try to get connect
from a remote location it won't connect. I have tried turning remote
desktop
on and off, messed with the firewall settings, and still can not get any
sessions to connect. I doesn't seem to be going far enough to test the
creditials I am logging in with so I know thats not the problem, it simply
doesn't seem to be accepting a connection.

Are you sure that the Remote Destop port is forwarded from your router to
the correct internal IP address for your computer?

Are you sure that an exception is set for Remote Desktop in the Windows
Firewall or any other firewall that you may use?

Are you sure you are using the correct and current global IP address when
trying to connect to your computer remotely, and are you sure you are not
using the internal LAN IP address? Or are you using a hostname?

ss.

 

[Guest]

Yes I am sure. Like I said it was working when I first set it up. I have
checked the firewall multiple times and 3389 is open (or telling me its
open). I should have also mentioned that I can't even connect the machine
internally.

 

[Guest]

Hi Eric - I am having the same trouble. RDP was working on my Vista Business
PC, but stopped recently. I cannot even RDP on the local LAN to it. I
checked the status of Port 3389, and Vista is no longer "Listening" for it.
From a command prompt, try:

netstat -ano

You should see an entry for TCP Port 3389. For some reason, mine is now
gone, and I do not know how to get it back to listening.

 

[Andrew McLaren]

Hi Eric - I am having the same trouble. RDP was working on my Vista
Business
PC, but stopped recently. I cannot even RDP on the local LAN to it. I
checked the status of Port 3389, and Vista is no longer "Listening" for
it.
From a command prompt, try:

netstat -ano

You should see an entry for TCP Port 3389. For some reason, mine is now
gone, and I do not know how to get it back to listening.

Hi Eric and PittPanther,

The other precondition for making a Remote Desktop connection to your Vista
machine is that the Terminal Services service is running. You can verify
this with either of 2 different comands:

1) C:\>net start

or

2) C:\>tasklist /svc

In the Tasklist command, the "/svc" parameter tells tasklist to show the
services which are running in each Service Host process. So you should see
something like:

svchost.exe 1284 CryptSvc, Dnscache, KtmRm, NlaSvc,
TapiSrv, TermService

This tells you that the Process ID for Terminal Services is 1284.

When you do a "netstat -ano" it will show you the process IDs for the
processes listening on the various ports. If/when Terminal Services is
active, it will show up in the netstat list, on port 3389 ands Pitt Panther
correctly notes.

TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
1284

So, make sure you have Terminal Services running on your machine!

Let us know how you get on.

 

[Guest]

Hi Eric and PittPanther,

The other precondition for making a Remote Desktop connection to your Vista
machine is that the Terminal Services service is running. You can verify
this with either of 2 different comands:

1) C:\>net start

or

2) C:\>tasklist /svc

In the Tasklist command, the "/svc" parameter tells tasklist to show the
services which are running in each Service Host process. So you should see
something like:

svchost.exe 1284 CryptSvc, Dnscache, KtmRm, NlaSvc,
TapiSrv, TermService

This tells you that the Process ID for Terminal Services is 1284.

When you do a "netstat -ano" it will show you the process IDs for the
processes listening on the various ports. If/when Terminal Services is
active, it will show up in the netstat list, on port 3389 ands Pitt Panther
correctly notes.

TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
1284

So, make sure you have Terminal Services running on your machine!

Let us know how you get on.