Remote Desktop connection problems

[Guest]

I am trying to connect to an XP machine from a Windows Me machine through remote desktop. RD has been enabled on the XP machine. I downloaded the remote desktop software from the Microsoft site and installed it on the Win Me machine. Everytime I try to connect using the IP address of the XP machine, I get the following error message

"The client could not connect to the remote computer. Remote conncections might not be enabled or the computer might be too busy to accept new connections. It is also possible that network problems are preventing your connection...

Any ideas why RD is not working? I have never been able to connect using RD

Thanks

 

[Vera Noest [MVP]]

What kind of network connection do you have between these two
machines? Are they on the same LAN? Can you ping the XP client from
the ME client?

 

[Guest]

Hi Vera
I am trying to connect over the Internet. The XP professional machine is at home. The Win Me computer is in a hotel room half way around the world. I have broadband Internet at both locations

I will try pinging and let you know
Iv
----- Vera Noest [MVP] wrote: ----

What kind of network connection do you have between these two
machines? Are they on the same LAN? Can you ping the XP client from
the ME client

 

[Vera Noest [MVP]]

OK, but then you probably have some private IPnummer on your XP
machine at home, or ...?
Or maybe one or both of the machines are behind a firewall which
doesn't allow traffic through port 3389?

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*

 

[Guest]

Hi Vera

I tried pinging it. At first I got an error message that said that the network is out of reach or something like that. Now, however, the ping just times out. I remember I disabled the firewall on the XP machine but unfortunately that computer is in the U.S. while I am in Japan, trying to connect to it.

Any ideas?
Thanks,Iv
----- Vera Noest [MVP] wrote: ----

OK, but then you probably have some private IPnummer on your XP
machine at home, or ...
Or maybe one or both of the machines are behind a firewall which
doesn't allow traffic through port 3389

--
Vera Noes
MCSE,CCEA, Microsoft MVP - Terminal Serve
http://hem.fyristorg.com/vera/I
*----------- Please reply in newsgroup -------------

 

[Vera Noest [MVP]]

Do you have a static and public IP addres on your home computer?
Anyway, if you can't ping it, you can't rdp to it either.
I wouldn't know how to fix this without having access to the
machine.

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

 

[Netwerkz]

Hi Vera:

I tried pinging it. At first I got an error message that said that the

network is out of reach or something like that. Now, however, the ping just
times out. I remember I disabled the firewall on the XP machine but
unfortunately that computer is in the U.S. while I am in Japan, trying to
connect to it.

Any ideas?
Thanks,Ivo
----- Vera Noest [MVP] wrote: -----

OK, but then you probably have some private IPnummer on your XP
machine at home, or ...?
Or maybe one or both of the machines are behind a firewall which
doesn't allow traffic through port 3389?

--
Vera Noest
MCSE,CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
*----------- Please reply in newsgroup -------------*

What is between your XP machine and it's internet connection?
A router? Some proxy?

The ip address on the XP machine: is it in the private ip address range:
10.0.0.0 - 10.#.#.#
172.16.0.0 - 172.31.#.#
192.168.0.0 - 192.168.#.#

If in the above ranges, you are likely behind a device doing NAT
and you may need to redirect incoming traffic on port 3389 to
go to your XP machine.

If your ip address on the XP machine is not in the private ip address
space, and is static or dynamically assigned via your ISP, then you
may have to disable the XP firewall (you stated you have done this) and
enable "Remote Desktop Connection".

Not being able to get an echo reply to a ping does not necessarily
mean you won't be able to connect (although usually it's a good
indicator) as some routers can be set not to reply to ping request.