Access an XP Pro with an XP Home Host

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am in the process of upgrading a computer in my network with XP Pto to
allow access to it from the outside.

My Host PC has XP Home and uses Norton Internet Security as a Firewall
instead of Windows Firewall. I have Windows Firewall disabled.

If I open Port 3389 under Windows Firewall screen, will it do the trick, or
will I have to also set something up from Norton Internet Security? If so,
what is it? I have been looking around but cannot see where to open Port
3389.

Any help is appreciated.

Eduardo
 
Eduardo Pietri said:
My Host PC has XP Home and uses Norton Internet Security as a Firewall
instead of Windows Firewall. I have Windows Firewall disabled.

If I open Port 3389 under Windows Firewall screen, will it do the
trick, or will I have to also set something up from Norton Internet
Security? If so, what is it? I have been looking around but cannot
see where to open Port 3389.
Click to expand...

If you are using this XP Home PC to run Remote Desktop Client, you do not
need to open any ports in any firewall.

It is on the XP Pro PC acting as an RDP server that you need to allow
incoming Remote Desktop calls.
 
The Host of my network is an XP Home PC with ICS. All the PC's in this
network access the Internet via this PC (Default Gateway 192.168.0.1). The
Public IP Address of all the PC's is the same, the one that the Cable Modem
has, which is connected to the Host PC.

If I have a XP Pro PC within this network running RDC with Port 3389 open,
is that enough to access this PC from the outside, even if nothing is done to
the Host PC?

Thanks again.
Eduardo
 
My plan is for others to access my XP Pro PC via the Internet (cable modem).
That means that they will have to go "through" the Firewall in my Host PC,
right?

The public IP address of all PC's in the network is the same, the one given
out by my cable modem. Will others have access to the specific XP Pro PC
within the network in this scenario?

Thanks again.
Eduardo
 
Just a clarification... the XP Pro PC will be acting as a server, running
with remote desktop enabled and port 3389 open.
 
Eduardo Pietri said:
The Host of my network is an XP Home PC with ICS. All the PC's in
this network access the Internet via this PC (Default Gateway
192.168.0.1). The Public IP Address of all the PC's is the same, the
one that the Cable Modem has, which is connected to the Host PC.

If I have a XP Pro PC within this network running RDC with Port 3389
open, is that enough to access this PC from the outside, even if
nothing is done to the Host PC?
Click to expand...

No, you will need to configure ICS on the "Host" to forward TCP port 3389 to
the XP Pro PC running the RDP server.

Assuming the "Host" is running XP Service Pack 2, you do this configuration
in control panel Windows Firewall, tab Advanced, select correct network
interface, click button Settings, click Add, fill in IP address or NetBIOS
name of the XP Pro PC on your LAN, external port 3389, internal port 3389,
TCP.
 
Eduardo Pietri said:
The public IP address of all PC's in the network is the same, the one
given out by my cable modem. Will others have access to the specific
XP Pro PC within the network in this scenario?
Click to expand...

Answered in other thread with identical question.
 
Great! Thanks.

Now, how about if I have Windows Firewall DISABLED and have Norton Internet
Security enabled as the Firewall?

I've looked around in the NIS Help & Support but have not found a way to do
the same thing. Do you know?

Eduardo
 
Eduardo Pietri said:
Now, how about if I have Windows Firewall DISABLED and have Norton
Internet Security enabled as the Firewall?
Click to expand...

You must not disable Windows Firewall. You must have Windows Firewall
enabled so that the ICS function can work and so that the port-forwarding
can work.

You should not enable Norton Internet Security, because you must use Windows
Firewall.
I've looked around in the NIS Help & Support but have not found a way
to do the same thing. Do you know?
Click to expand...

NIS cannot configure port-forwarding in ICS. NIS is not a routing product.

I'm not prepared to guess what might happen if you attempt to use ICS and
NIS simultaneously. If NIS works in these circumstances, you would have to
open port 3389 for incoming traffic on the WAN interface, AND ALSO configure
ICS to forward port 3389 to the required LAN address: double the
configuration you would need to do with WF/ICS.
 
Thanks again.

I found another message that states the NIS could work, but I need to add a
Firewall Rule for Port 3389 and it gives the instructions on how to do it.
I'll try that first without enabling Windows Firewall to see if it works.
ICS is working fine within my network with NIS enabled and Windows Firewall
Disabled.

If that doesn't work, then I'll trash NIS and keep Windows Firewall only.

Cheers,
Eduardo
 
Back
Top