Re: Remote Desktop
From: Jeffrey Randow (MVP) (jeffreyr-support_at_remotenetworktechnology.com)
Date: 02/06/04
- Next message: Chris: "error 733: a connection to the remote computer cannont be completed????"
- Previous message: Jeffrey Randow (MVP): "Re: VPN - can connect from work to home but not vice versa"
- In reply to: John Cuccia: "Re: Remote Desktop"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 05 Feb 2004 21:07:30 -0600
UPnP simplifies port forwarding as it won't require any user action to
make it work... If you manually forward TCP Port 3389, you don't need
to use UPnP (+ for remote desktop, you must do this by hand as the
UPnP support is for Remote Assistance, not Remote Desktop)
As an example, my UPnP router sets up port forwarding whenever I send
out a file via Windows Messenger.
Jeffrey Randow (Windows Net. & Smart Display MVP)
jeffreyr-support@remotenetworktechnology.com
Please post all responses to the newsgroups for the benefit
of all USENET users. Messages sent via email may or may not
be answered depending on time availability....
Remote Networking Technology Support Site -
http://www.remotenetworktechnology.com
Windows XP Expert Zone - http://www.microsoft.com/windowsxp/expertzone
On Thu, 05 Feb 2004 12:19:00 -0600, John Cuccia <nospam@nospam.com>
wrote:
>In KB article301529 MS says that a UPNP device is needed on at least
>one end of a connection behind broadband routers. Does enabling port
>forwarding eliminate the need for UPNP?
>
>
>On Thu, 16 Oct 2003 20:43:55 -0500, "Sooner Al"
><SoonerAl@somewhere.net.invalid> wrote:
>
>>Forward TCP Port 3389 through the router to the private LAN IP of the desktop PC. Call using the
>>public IP, ie. the IP assigned by your ISP, of the router.
- Next message: Chris: "error 733: a connection to the remote computer cannont be completed????"
- Previous message: Jeffrey Randow (MVP): "Re: VPN - can connect from work to home but not vice versa"
- In reply to: John Cuccia: "Re: Remote Desktop"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|