Question on port forwarding and Remote Desktop

It is my understanding that you must Port Forward 3389 in order to use
Remote Desktop via the Internet.

My questions - must you do this for both your router and the Windows
Firewall and must you forward both TCP & URL?

Since I'm running XP Pro on a LAN, must I include forwarding for each of the
pc's I want to access?

TIA

On Mar 13, 10:45*am, "Jim" wrote:
It is my understanding that you must Port Forward 3389 in order to use
Remote Desktop via the Internet.

My questions - must you do this for both your router and the Windows
Firewall and must you forward both TCP & URL?

Since I'm running XP Pro on a LAN, must I include forwarding for each of the
pc's I want to access?

TIA

Port forward is only done at the router. You just need to permit
Remote Desktop to "pass-thru" the firewall.

Also, it should be UDP and not URL.

On Mar 13, 10:45*am, "Jim" wrote:
It is my understanding that you must Port Forward 3389 in order to use
Remote Desktop via the Internet.

My questions - must you do this for both your router and the Windows
Firewall and must you forward both TCP & URL?

Since I'm running XP Pro on a LAN, must I include forwarding for each of the
pc's I want to access?

TIA

Port forward is only done at the router. You just need to permit
Remote Desktop to "pass-thru" the firewall.

Also, it should be UDP and not URL.

Hi
Ports have be forward in the receiving computer (I.e. the one that is
controlled from the outside).
The forwarding has to be done through all devices, and software applications
that blocks ports. Typically it is the Router and software Firewall.
Jack (MS, MVP-Networking)

"Jim" wrote in message
...
It is my understanding that you must Port Forward 3389 in order to use
Remote Desktop via the Internet.

My questions - must you do this for both your router and the Windows
Firewall and must you forward both TCP & URL?

Since I'm running XP Pro on a LAN, must I include forwarding for each of
the pc's I want to access?

TIA

Hi
Ports have be forward in the receiving computer (I.e. the one that is
controlled from the outside).
The forwarding has to be done through all devices, and software applications
that blocks ports. Typically it is the Router and software Firewall.
Jack (MS, MVP-Networking)

"Jim" wrote in message
...
It is my understanding that you must Port Forward 3389 in order to use
Remote Desktop via the Internet.

My questions - must you do this for both your router and the Windows
Firewall and must you forward both TCP & URL?

Since I'm running XP Pro on a LAN, must I include forwarding for each of
the pc's I want to access?

TIA

Jim wrote:
It is my understanding that you must Port Forward 3389 in order to use
Remote Desktop via the Internet.

My questions - must you do this for both your router and the Windows
Firewall

The windows firewall has to have the port set as an an exception, yes.

and must you forward both TCP & URL?

URL? No, I don't know what you mean. If you mean UDP, then no.

Since I'm running XP Pro on a LAN, must I include forwarding for each
of the pc's I want to access?

You can't do this if you don't have multiple public IPs bound to the WAN
interface on your router, and one to one NATs set up for each public to
private. Otherwise, you'll need to change the listening port for each
computer in the registry (e.g., 3390, 3391, etc) and make sure they're set
with non-changing private IP addresses. Then set up custom exceptions in
each PCs firewall for those ports. Then set up a rule for each in the
firewall This is a pain - you might consider an SSL VPN appliance like the
SonicWALL or Netgear lines which will let you access your desktops via a web
page / menu, and none of this nonsense.

TIA

Jim wrote:
It is my understanding that you must Port Forward 3389 in order to use
Remote Desktop via the Internet.

My questions - must you do this for both your router and the Windows
Firewall

The windows firewall has to have the port set as an an exception, yes.

and must you forward both TCP & URL?

URL? No, I don't know what you mean. If you mean UDP, then no.

Since I'm running XP Pro on a LAN, must I include forwarding for each
of the pc's I want to access?

You can't do this if you don't have multiple public IPs bound to the WAN
interface on your router, and one to one NATs set up for each public to
private. Otherwise, you'll need to change the listening port for each
computer in the registry (e.g., 3390, 3391, etc) and make sure they're set
with non-changing private IP addresses. Then set up custom exceptions in
each PCs firewall for those ports. Then set up a rule for each in the
firewall This is a pain - you might consider an SSL VPN appliance like the
SonicWALL or Netgear lines which will let you access your desktops via a web
page / menu, and none of this nonsense.

TIA

Thanks to all who responded

"Jim" wrote in message
...
It is my understanding that you must Port Forward 3389 in order to use
Remote Desktop via the Internet.

My questions - must you do this for both your router and the Windows
Firewall and must you forward both TCP & URL?

Since I'm running XP Pro on a LAN, must I include forwarding for each of
the pc's I want to access?

TIA

Thanks to all who responded

"Jim" wrote in message
...
It is my understanding that you must Port Forward 3389 in order to use
Remote Desktop via the Internet.

My questions - must you do this for both your router and the Windows
Firewall and must you forward both TCP & URL?

Since I'm running XP Pro on a LAN, must I include forwarding for each of
the pc's I want to access?

TIA