XP Home Remote Desktop port 3389 not listening

[Alma Salazar]

found a link on this site, which describes my problem, but i need some
additional help
http://www.experts-exchange.com/Operating_Systems/WinXP/Q_20655908.html

a user used to be able to connect to a remote server using RDesktop, but now
he gets the error
client could not establish a connection.....
most likely cause
1)remote connections may not be enabled
2)maximum no. of connections exceeded
3)network error occured

I executed netstat -a on the machine, but port 3389 is not listening. I am
able to use RDesktop to connect to an XP Pro machine in the internal
network, but not to the remote server at another location. I am able to
connect to both this XP Home machine and the external server.

I can ping the remote server. Any ideas?


Thank you.

Alma Salazar

 

[Sooner Al]

Is Remote Desktop enabled on the target machine?
If you run services.msc on the target machine is the "Terminal Services" service started?

 

[Bill Sanderson]

There's no end to the story at the link you gave.

If I'd been involved, I would have recommended, as someone did, reinstalling
Service Pack 1 for XP on the machine which had the options greyed out.

I found the thread (and your message) confusing to follow.

The machine which should be found to be listening on port 3389 is the HOST
machine--the one you are trying to connect to.

The fact that you also cannot connect to that machine from a different
client, running a different OS, seems to indicate that the issue may be at
the host machine, or the intervening network.

The fact that you can ping the remote server is a good indication, but if
port 3389 is not getting through the intervening network, RD will fail.

What is the behavior if you Telnet to port 3389 of the remote HOST machine?

 

[Alma Salazar]

Let's see hopefully this is more clear.

I have 3 machines, machine A(offsite server I want to connect to), machine B
(LAN machine, which can access machine A via Remote Desktop and has port
3389 listening all the time, machine C (my problem child which does not have
port 3389 listening, is part of the LAN and receives the error below)

machine B and C are now on Win XP Pro SP1
machine B and C are both part of the network
machine B can connect to C via remote desktop
machine C can not connect to B via remote desktop!

This is the error I receive, which I feel may be related to my initial
problem of machine C not being able to access machine A.

Remote Desktop Disconnected
the client could not connect to the remote desktop
remote connections might not be enabled or the computer
might be too busy......possible that network problems
are preventing your connection.

Does anybody have any ideas on what I need to troubleshoot? Is this a LAN
or more of a router issue?

Thank you.

 

[txics68]

I found the same problem on two of my machines. Both are
XP and both began having problems connecting to
particular win2000 server. I began experiencing the
problem after loading the latest xp windows updates.
Check out the following articles on microsofts knowledge
base site. 304304 and 306759. It may work for you. I am
still working the problem. Since my windows versions are
oem I will follow up with my pc manufacturer.Good luck.