Windows Forum

Ask something
Discussion Locked

Using multi-homed server for internet ac

0 helpful
4 replies

by cray

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We have a Linux box that has been setup for years and none of us know how to use or what its doing so we are going to NT/IIS. We ran a test to see if we encountered any problems before we do the final swap. I have a multi-homed NT4.0 server running IIS, DNS. Our internal network uses real IP addresses (which the server is on) and the router to our ISP uses real IP addresses, but between the other network card and the router we are using 192.x.x.x for security reasons. I can hit our website fromoutside and I can get outside from the server, but none of the network clients can access the site or the internet even when they are set to use the webserver as their DNS server. What am I missing? Do I need to use Wins too? IP forwarding is enabled on the server but it doesn't seem to forward any internet requests. I'm obviously missing a key element here. What do I need to do to get the server to allow clients to access the internet through the "hidden" router?

4 replies

by nichomach

Use a proxy server such as MS proxy v2. Or you could try ProxyPlus from http://www.proxyplus.cz. WINS will not save you. Try either of the two above - there's a 3 month eval of MS Proxy available for download, and ProxyPlus is free for two concurrent users (beyond that, you pay a license fee).

by cray

I was hoping you wouldn't say that, but that was the only thing I hadn't tried yet.

by inspectorclave

You said that your internal network uses real IP addresses. Why? You only need one real IP address in order to access the Internet. It doesn't matter if you have one workstation on your LAN or 500. What you need to do is install a proxy of some sort. MS Proxy server is not cheap, but it is a business package that will get the job done. An inexpensive option would be SyGate by Sybergen (www.sybergen.com). These products do NAT (Network Address Translation) which takes multiple non-routable IP addresses (192.168.x.x for example) and translates them to one real IP address for Internet access. All you need to do is bind the real IP address to one NIC in the server, then bind a 192.168.x.x address to the internal LAN NIC in the server. Enable IP forwarding (if you so choose). You can even implement DHCP to automatically configure the workstations with a 192.168.x.x address and the IP of the gateway (mutli-homed PC). The ISP is doing DNS, so you only need to implement DNS on the server for local host na

by cray

I inherited the network in its present condition. I'm aware that we don't need real IPs for internal traffic. We are actually converting to non-routable IPs in the near future. Thanks for the info on the cheap Proxy server.

This discussion is closed to new replies.