That is a pretty standard way to handle the situation. It is called
static mapping. Most NAT routers, including RRAS will let you map a public
IP to a private IP.
"guywolcott" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
>I use Windows Small Business Server 2003 to serve several functions on
> our small network: file server, exchange server and firewall. The
> server has two network interfaces: internal (192.168.16.2) and
> external (67.100.185.126). Everything works perfectly. However, I
> would like to add a Web Server inside the local network, behind the
> "firewall". I will have a 2nd public IP (assume it is 67.100.185.125),
> but I would like to assign that IP to the Small Business Server's
> external interface, and have it forward requests on to the internal,
> private IP of the Web Server (say, 192.168.16.3). I don't want to
> connect the Web Server directly to the router using a 2nd network
> interface, if I can avoid it.
>
> I have looked around quite a bit, including this group, to find how I
> would set things up in RRAS to do this correctly. But I haven't found
> what I need. I hope I have described the situation well enough, and I
> greatly appreciate any suggestions. Thanks so much...Guy
>
|