Re: The client could not connect to the remote computer
From: Robin Walker (rdhw_at_cam.ac.uk)
Date: 11/01/04
- Next message: Robin Walker: "Re: Is it possible to map a drive over 3389 using 2003 TS + remote desktop ?"
- Previous message: scott: "Re: Is it possible to map a drive over 3389 using 2003 TS + remote desktop ?"
- In reply to: Simon: "RE: The client could not connect to the remote computer"
- Next in thread: Simon: "Re: The client could not connect to the remote computer"
- Reply: Simon: "Re: The client could not connect to the remote computer"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 1 Nov 2004 13:56:13 -0000
"Simon" <Simon@discussions.microsoft.com> wrote in message
news:9BF5B570-EEEA-4A61-9FE9-8403329E2E3A@microsoft.com
>
> Thanks for that. Yes, I've definitely got 3389 open and RDC marked on
> both PCs
You only need RDP enabled and port 3389 opened on the server PC (XP Pro).
Settings on the client are not needed.
> My laptop (Xp Home SP2) is the one I want to make the connection from
> remotely and my office PC (Xp Pro, SP1) is the one I want to be able
> to connect into. When my laptop is physically connected to the LAN by
> ethernet the Remote Desktop Web Connection works fine. When I
> disconnect my laptop
> from the LAN, go someplace and use its modem to dial-up the internet,
> I do still get the internet RDC page up on the screen alright, but
> when I type in my server name (i.e. the name of my office PC - I just
> type in its name right?, not the IP address of its network card which
> is 192.168.0.xxx) there is no connection.
No, you cannot use its name, and you cannot (on the outside internet) use
its internal LAN address 192.168.0.xxx. You must use the WAN IP address of
your home router.
Only in your home LAN can you use the 192.168.xxx.xxx address of the RDP
server.
> The office LAN uses a Netgear router/gateway so we are not using
> Microsoft Internet Connection Sharing, everything goes through the
> router whose IP address is different from the Office PC's network
> card IP address. I have the router configured to "Always Allow"
> incoming and outgoing RD requests on port 3389.
That's not enough: in the router you need to port-forward TCP port 3389 to
the local LAN address of the RDP server PC. This PC should therefore be
assigned a fixed LAN IP address within the subnet of the router, but outside
its DHCP allocation pool, so that the port-forward will remain meaningful
for ever. If your XP Pro PC has a DHCP-assigned address, it could change,
and the port-forward would become invalid.
> I have the laptop's
> modem TCP/IP WINS tab configured with the IP address of the Office
> PC's network card address.
This appears to be an error, and of no possible use in the RDP context.
Remove the setting. You cannot use local LAN IP addresses (192.168.xxx.xxx)
in the broader internet anyway.
-- Robin Walker rdhw@cam.ac.uk
- Next message: Robin Walker: "Re: Is it possible to map a drive over 3389 using 2003 TS + remote desktop ?"
- Previous message: scott: "Re: Is it possible to map a drive over 3389 using 2003 TS + remote desktop ?"
- In reply to: Simon: "RE: The client could not connect to the remote computer"
- Next in thread: Simon: "Re: The client could not connect to the remote computer"
- Reply: Simon: "Re: The client could not connect to the remote computer"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
