Malch Silly Counter:
Visitor 84491
Fight Censorship
 Map   New   Links   FAQ   Photo   Malch   Search 

Internet Access for Multiple Win 95 Systems

Objective

You have two or more systems running Win 95 or Win NT connected via a LAN (e.g. Ethernet) and, you want all of them to share a single connection to the Internet.

Background and Discussion

There are two fundamentally different approaches that can be adopted to address this requirement.

  1. Full TCP/IP Routing

    In order to implement full TCP/IP routing, you will need:

    • A registered Class B or Class C IP address.
    • A hardware router or a server with full routing capabilities such as Unix or Windows NT. Windows 95 does not support routing.
    • Appropriate arrangements with your Internet Service Provider (ISP). Routing configurations cannot and will not work unless your ISP has configured their routing equipment accordingly.

    Full TCP/IP routing offers great flexibility. Each node on the network is assigned its own IP address and can be made visible to the entire Internet. It is also rather complex, may be costly (depending upon your ISP's rate structures) and may introduce vulnerabilities with respect to systems security.

  2. Proxy Server Access

    Proxy server access is much simpler. It may be less costly depending upon your ISP's rate structure. And, it is inherently more secure. It does, however, impose some limitations especially with regard to those exotic TCP/IP applications that use non-standard or multiple TCP/IP ports.

    The following sections describe a simple, inexpensive proxy server arrangement that is suitable for many small business and home network situations. In the opinion of the author, large corporations or those with a requirement for high security should consider an industrial strength firewall solution.

Instructions

  1. Establish a basic SLIP/PPP connection

    Establish a regular dial-up PPP or SLIP connection to the Internet.

  2. Establish IP addresses for your LAN

    Each of the systems on your LAN will require its own IP address.

    Do not make the addresses up.

    You can either register a Class C Network with Internic or use one one the following IP addresses which are reserved for private networks. Here is the relevent section from RFC 1597:

    Private Address Space

    The Internet Assigned Numbers Authority (IANA) has reserved the following three blocks of the IP address space for private networks:

    • 10.0.0.0 - 10.255.255.255
    • 172.16.0.0 - 172.31.255.255
    • 192.168.0.0 - 192.168.255.255

    Note: Do not use xxx.xxx.xxx.0 or xxx.xxx.xxx.255 for any of your equipment. These addresses are reserved.

  3. Install TCP/IP for your Ethernet Adapter

    Start Control Panel and select Network. Use the Add option to install TCP/IP for your Ethernet Adapter:

    • TCP/IP -> Your adapter

    Ensure that inappropriate bindings are Removed (for example, you do not want NetBEUI bound to your Dial-up Adapter).

    Repeat this step for each system on the LAN.

  4. Configure the TCP/IP parameters in Control Panel

    Configure the TCP/IP parameters in Control Panel (Network) as follows:

    The following settings assume System A (with dial-up to the Internet) connected via a LAN to System B. The Control Panel Network settings should be set as follows:

    
                SYSTEM A                        SYSTEM B
                ========                        ========
    
    TCP/IP -> LAN ADAPTER
    =====================
    
    IP         10.10.10.11                    10.10.10.12
               {For example}                  {For example}
    
    Mask       255.255.255.0                  255.255.255.0
    
    DNS        xxx.xxx.xxx.xxx                None
               xxx.xxx.xxx.xxx
               {Insert your Internet Providers DNS addresses here}
    
    WINS       None                           None
    
    Gateway    None                           None
    
    Bindings   None                           None
    
    Advanced   None                           None
    
    
    TCP/IP -> DIAL-UP ADAPTER
    =========================
    
    IP         xxx.xxx.xxx.xxx
               {Insert your Internet IP address here}
    
    Mask       255.255.255.0
    
    DNS        xxx.xxx.xxx.xxx
               xxx.xxx.xxx.xxx
               {Insert your Internet Providers DNS addresses here}
    
    WINS       None
    
    Gateway    xxx.xxx.xxx.xxx
               {Insert your Internet Providers Gateway address here}
    
    Bindings   None                           None
    
    Advanced   None                           None
    
    
  5. Configure Dial-Up networking on System A

    On System A, select the Properties dialog for your Dial-Up Networking configuration and set them as follows:

    
    IP                   xxx.xxx.xxx.xxx
                         {Insert your Internet IP address here}
    
    DNS                  xxx.xxx.xxx.xxx
                         xxx.xxx.xxx.xxx
                         {Insert your Internet Providers DNS addresses here}
    
    WINS                 None
    
    IP Header Comp       {Set according to your Internet Providers
                         instructions}
    
    Use default Gateway  Checked
    
    
  6. Test TCP/IP over your LAN

    Test your configuration. Reboot both systems. From System A, ensure that your dial-up Internet connection is still working. Then, test the operation of TCP/IP over your LAN using Ping. Each system should be able to Ping each of the other systems on the LAN.

  7. Obtain WinGate

    Point your browser at:

  8. Configure Wingate and go...

  9. For additional information

    Additional WinGate documentation is available on line at:

 

© Copyright Malcolm Hoar 1995-2014
malch at malch dot com