0.0.0.0:3389 0.0.0.0:0 LISTENING

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

netstat -ano yields:

Proto Local Address Foreign Address State PID
TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING 1340

But it does not have an entry associated with the ip address associated with my
machine. Is this vaild or should it be listening to this port on my address?

 

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

What process is running with PID 1340?

 

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Hi Rick,

> netstat -ano yields:
>
> Proto Local Address Foreign Address State PID
> TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
1340
>

0.0.0.0:3389, and the state of LISTENING means that it is listening on port
3389 on all IP addresses the computer has.
This is normal for Remote Desktop, and should be fine.

Thanks for posting!

David Jones
Small Business Server Product Team

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

 

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

svchost.exe is the process associated with PID 1340.

 

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

I don't understand why my XP home machine can't connect to this XP pro machine's ip address.
I keep getting the following error:

Remote Desktop Disconnected The Client could not establish a connection to
the remote computer. The most likely causes for this error are: 1)Remote
connections might not be enabled at the remote computer. 2) The maximum
number of connections was exceeded at the remote computer. 3) A network
error occured while establishing the connection.

 

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

Hi Rick,

> Remote Desktop Disconnected The Client could not establish a connection to
> the remote computer. The most likely causes for this error are: 1)Remote
> connections might not be enabled at the remote computer. 2) The maximum
> number of connections was exceeded at the remote computer. 3) A network
> error occured while establishing the connection.

Where is the XP Home machine, and where is the XP Pro machine? Are there
any firewalls between the two?
Also, has this ever worked?
Can you access other things on the XP Pro machine? (like file shares, etc).

David Jones
Small Business Server Product Team


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

 

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

"Rick_f" <anonymous@discussions.microsoft.com> wrote:
> svchost.exe is the process associated with PID 1340.

Svchost is just a program that starts services. The command "tasklist /svc"
will show you what service(s) it is. 3389 is the default port for terminal
services. Could be terminal server listening on all interfaces (hence
0.0.0.0) for incoming requests.

 

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

They are on the same local network, no firewall between them. I am
able to ping the Pro Machine. I have never had this working before, and
I have not been able to access other things on the XP Pro machine.

The Pro machine is able to access an Xp Home machine and a 98 machine.
The other machines can browse the Pro machine, but can't see any of the
folders I've shared on it.

 

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

I found my problem. The problem was a cisco vpn service that was running. Even
though I wasn't actively running the vpn connection, the service was being started
and running all the time.

 

[Guest]

Archived from groups: microsoft.public.windowsxp.work_remotely (More info?)

I had this same error. I was connected to my desktop, no firewalls or
anything between my laptop and desktop. I ran windowsupdate remotely,
installed the 5 critical updates release today and upon my desktop coming
up, I tried remoting to it and got the same error immediately. I logged
into a VMWare virtual machine and it had the same problem remoting to the
host. I had the same 0.0.0.0 listening thing you did. I could ping, use
computer management, and file sharing on my desktop, logging in locally
worked as did fast user switching.
I rebooted again to no avail. Same error, sometimes another error claiming
network problems, but I could always remote to my laptop from the desktop.

I unchecked the "allow remote desktop" box in computer properties, applied
the settings and rechecked the box, nothing.

Finally, I ended the svchost that was running terminal services and manually
started the terminal services service, this worked. I rebooted to make sure
and it came back up. I hate errors, esp. the ones that are fixed by by
themselves and/or by changing or doing things that technically shouldn't
matter

I also wonder, does anyone know if it makes any kind of difference if I set
the Terminal Services service to automatic?

"Rick_f" <anonymous@discussions.microsoft.com> wrote in message
news:80FF5EE4-98C5-4E85-9922-3BC100626C49@microsoft.com...
> I don't understand why my XP home machine can't connect to this XP pro
machine's ip address.
> I keep getting the following error:
>
> Remote Desktop Disconnected The Client could not establish a connection to
> the remote computer. The most likely causes for this error are: 1)Remote
> connections might not be enabled at the remote computer. 2) The maximum
> number of connections was exceeded at the remote computer. 3) A network
> error occured while establishing the connection.
>