Remote desktop connection doesn't find other computer

  • Thread starter Thread starter Michael Moser
  • Start date Start date
M

Michael Moser

Hi all,
I am trying to access one computer on my home network from another one
(both running WinXP +SP1) using Remote Desktop connection but I can't
get things to work.

The symptom that I am struggling with is, that the client - when I try
to connect - always reports that it can't find the remote computer
while at the same time I can access a couple of shared directories on
that very same computer (after first locating it via "search for
computer") using precisely that very same computer name.

So why does the Remote Desktop client not find the remote computer?

Michael
 
Michael said:
I am trying to access one computer on my home network from another one
(both running WinXP +SP1) using Remote Desktop connection but I can't
get things to work.

The symptom that I am struggling with is, that the client - when I try
to connect - always reports that it can't find the remote computer
while at the same time I can access a couple of shared directories on
that very same computer (after first locating it via "search for
computer") using precisely that very same computer name.

So why does the Remote Desktop client not find the remote computer?


Could be a lot of things..

Such as, the computer is not in a DNS anywhere..
Try accessing it by the computers IP instead.

Such as you've configured the firewall to allow file/printer sharing, but
port 3389 is still closed.
Check your firewall settings on the remote computer (if this applies.)

You've configured your router (if you have one and these machines are not
both on the same router) to allow pass-thru for some ports, but not 3389 to
this PC.
Check you port forwarding on your router (if this applies.)

There's other possibilities, but I am just throwing out guesses without
knowing more about your configuration.
 
hi my name is evan i heard about this do you have a net hub is it pluged in or do you have a crossover cable. or you might need softwhere like pc anywhere for it well i can people told me to get pc anywhere i got it then it worked. just telling you pc anywhere is a not for home use but you can use it for home use.To go remotely you need winxp pro or pc anywhere.that is how much i can tell you
 
Shenan Stanley said:
computer?


Could be a lot of things..

Such as, the computer is not in a DNS anywhere..

That's true: the systems are not registered in any DNS server.
Try accessing it by the computers IP instead.


I tried that and that made things go. But what I find inconsistent
here is: why did the system then find the other computer by name when
doing a "search for computer"?
Such as you've configured the firewall to allow file/printer sharing, but
port 3389 is still closed.
Check your firewall settings on the remote computer (if this
applies.)

I had even disabled the firewell while trying out things but that
hadn't helped. Only using the IP address did. And now - I guess - it
is cached, since doing further attempts using the machine name now
worked as well. I guess it will now work until the DHCP somewhen
chooses to assign new addresses, at which point I have to start this
procedure all over... :-(

Michael
 
It sounds like you have enabled Port forwarding and that is the secret. Once you know your public IP (the one your ISP provides for you), and your local, the one your DHCP device assigns the specific machine in question, forwarding the request to that machine will work. If your ISP changes your public IP then you will have to do it over---unless you set up an address that will not change. Check out http://www.no-ip.com/ . You can get a permanent domain name to use which they will monitor. If your public IP changes, they will automatically assign it to your domain address. All you need watch is your local. (192.168.xx) If your DHCP changes this, be sure to open that port

Comcast has changed our IP at least four times this year. No-IP trapped it every time.

Hope this helps!
 
Back
Top