Re: NAT Problem Port Forwarding
- From: "Doug Sherman [MVP]" <dsherman@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Fri, 16 Sep 2005 11:18:26 -0400
If the clients are XP with firewalls enabled (or any OS with a firewall
installed), you will have to open these ports on the clients as well.
Doug Sherman
MCSE, MCSA, MCP+I, MVP
"Kotowski" <Kotowski@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:0944A389-B6DB-44D9-835E-A5759DD0513A@xxxxxxxxxxxxxxxx
> Hi people!
>
> Need some help here.
>
> My network schema:
>
> Client PC1 -> 192.168.0.XX
> Client PC2 -> 192.168.0.XY
>
> Windows 2003 DC -> 2 NICs (Internal -> 192.168.0.XX; External ->
146.XX.XX.XX)
> -External NIC connected to the internet
> -RRAS with NAT/Basic Firewall enabled
> -External NIC as public interface...
> -Internal NIC as private interface...
>
> My needs:
>
> 1. I need to forward traffic from the internet to my Windows 2003 DC TCP
> port 80 to Client PC1 TCP port 80.
>
> 2. I need to provide RDC access from the internet to 146.XX.XX.XX TCP port
> 3389 to Client PC2 TCP port 3389.
>
> What i did:
>
> In my Windows 2003 DC, RRAS, NAT/Basic Firewall, External, Properties,
> Services and Ports, i did this:
>
> - Marked checkbox Web Server (HTTP), on this interface, protocol TCP,
> incoming port 80, private ip address Client PC1, outgoing port 80;
> - Marked checkbox Remote Desktop, on this interface, protocol TPC,
incoming
> 3389, private ip address Client PC2, outgoing port 3389;
>
> But it didn´t work.
>
> As a test, i could successfully redirect HTTP traffic to my Windows 2003
DC
> itself via the same step above, only changing the private ip address to my
> Windows 2003 DC ip address instead of Client PC1.
>
> Any clue?
>
> I do not have ISA Server (it is out of question by now).
>
> Thanks in advance,
> Kotowski.
.
- Prev by Date: Re: DNS Question
- Next by Date: Re: DNS Question
- Previous by thread: DNS Question
- Next by thread: Re: NAT Problem Port Forwarding
- Index(es):
Relevant Pages
|
Loading