NAT Settings for exposing an internal web server to the outside world?
- From: "Keith Vinson" <Me@xxxxxxxxxxx>
- Date: Fri, 11 Aug 2006 17:51:29 -0400
Hi All,
I am having a bit of trouble getting this to work. What I need to do is get
an internal web server exposed to the outside world.
I followed the instructions in the online help to create a static address
reservation inside the RRAS -> IP Route -> NAT/basic firewall -> Outside LAN
properties. Also created a custom service & ports entry. But it doesn't
work. I used Active Ports to look for the proxy that is listening for the
connection, and I don't see one.
The outside LAN interface has 1 IP 192.168.6.100 assigned to it.
The inside LAN interface is 192.168.15.1 with .50 to .100 assigned by DHCP
The DHCP Address 192.168.15.52 is reserved for the internal web server (it
gets it, local machines can hit it)
The RRAS NAT address pool is 192.168.6.100 to .110
The RRAS NAT address pool has a reservation it is 192.168.6.102 maps to
192.168.15.52 (allow incoming sessions)
The RRAS NAT Services and Ports has a custom entry that maps
192.168.6.102:80 to 192.168.15.52:80
Should not the NAT server be listening on 192.168.6.102:80 for connections?
Does anyone know what steps I left out? the MS docs & TechNet don't imply
that there is more to this than this.....
Thanks,
Keith
.
- Follow-Ups:
- Re: NAT Settings for exposing an internal web server to the outside world?
- From: Robert L [MS-MVP]
- Re: NAT Settings for exposing an internal web server to the outside world?
- Prev by Date: Re: Changing subnet mask Server 2003
- Next by Date: Re: NAT Settings for exposing an internal web server to the outside world?
- Previous by thread: Re: Changing subnet mask Server 2003
- Next by thread: Re: NAT Settings for exposing an internal web server to the outside world?
- Index(es):
Loading