Routing

[Brian Roden]

Have the NIC attached to the ISDN router set with the IP address given to
you by your ISP. On the NIC that connects to the LAN, use one of the
reserved private IP networks (192.168.1.xxx, for example). Use this
throughout the LAN, whether you're using static IPs or DHCP to assign them
automatically. Make sure IP forwarding is turned OFF on the server that
connects to the Internet. Then install a proxy server on the server PC, and
install the proxy clients on your LAN machines. Requests from your browsers
and FTP clients on the LAN stations (which shold have options to use a
proxy server, which you will need to set) will go to the Proxy Server, then
be repacked and sent on the 'Net. When replies come back, the Proxy Server
will send them to the LAN PCs that made the original requests. Since the
Proxy Server PC has routing turned off, the other PCs on the separate
subnet will not be visible to the outside world.
--
--Brian Roden
--Leisure Arts, Inc.
--Bri...@leisarts.usa.com

Todd Chandler <tcha...@atc-usa.com> wrote in article
<01bc86ee$91c868a0$3bf901ce@tchanlder>...
> I have an NT Member Server with two NICs (3Com 3C509). One of the NICs
is
> connected to an ISDN router that goes out to the internet via 64k ISDN.
> The other NIC is connected to the internal LAN. For security purposes
> wouldn't I want to have the two NICs on separate subnets? If so, how do
I
> do this and how do I make it so that the computers on my internal LAN can
> still get out to the Internet.
>
>