So you don't trust the Internet Setup Wizard, eh? OK, here's
   TCP/IP in a nutshell.
   
   Transmission Control Protocol/Internet Protocol (TCP/IP) comes with
   Win95 as an NDIS 3.1 protocol. So, aside from connecting to The
   Internet, you can use any other Win95 clients or services over TCP/IP
   as well, or at least, those that don't depend on a particular
   protocol. Now that's pretty cool, but we want to connect to The
   Internet, right?
   
   Win95's network setup also copies the Windows Sockets libraries, based
   on Berkeley University's UNIX Sockets interface. Winsock works over
   any protocol really, which is why Win95 Setup must replace any other
   WINSOCK.DLL with its own, but for The Internet we're primarily
   concerned with Winsock over TCP/IP. All Windows Internet apps use the
   Winsock interface, in one form or another.

     * 8.1.1. How do I set up TCP/IP through a network card? 
       
   If you don't already have a network card installed, install it and
   load its Win95 driver. Then add TCP/IP protocol. TCP/IP has six
   property sheets, some of which affect all of TCP/IP, and others only
   affect the net card they're bound to:
     * IP address: Either have it select an IP address automatically, or
       give it an IP address and subnet mask directly. To perform
       automatic IP selection you need a BOOTP server or DHCP server
       operating within your local network. This is unique for each card
       using TCP/IP. NOTE: Thanks to MS short-sightedness again, Win95's
       TCP/IP won't auto-configure from a BOOTP server. Get the BOOTP
       addon desceibed below.
     * WINS configuration: To use Client for MS networks or any other
       NetBIOS apps over TCP/IP, you should have a Windows Internet Name
       Service (WINS) server accessible to you. Feed its IP address here,
       or if you have a DHCP server you can let it fetch WINS information
       from there. For regular Internet connections, select "Disable WINS
       Resolution". These settings affect all net cards using TCP/IP.
     * Gateway: To get to the rest of the Net, feed your router's IP
       address here. I don't believe Win95 will grab Gateway info from a
       DHCP server so ask your administrator for this value. This is
       unique for each card using TCP/IP.
     * DNS Config: This tab not only enables Domain Name Service for
       Winsock apps, it also enables NetBIOS name resolution over DNS.
       Select "Enable DNS" and feed it up to three addresses of DNS
       servers. If you have a local DNS and an Internet provider's DNS,
       you can enter both of them here. Yes, it does work. Also, if you
       wish, enter the domains you wish to enable NetBIOS naming for. For
       example, if you want to look for a server named \\JOE in the
       domain my-domain.com, insert my-domain.com into the domain search
       order list. For regular Internet access you can leave the search
       order fields blank. This tab affects all net cards using TCP/IP.
       NOTE: Supposedly, if you provide DNS info on a DHCP server and
       you leave DNS disabled here, Win95 will grab DNS info from the
       DHCP server.
     * Advanced: This is a useless tab, probably inserted to provide
       controls like TTL and hop count limits and such, but Microsoft
       chose to omit it. Too bad, because enough people complain about
       not being able to control them. Here are the settings I'm
       talking about.
     * Bindings: Very important tab if you don't want someone on The
       Internet poking in your computer. If you have File & Print Sharing
       for MS networks installed, turn off the checkmark to that service
       in this Bindings tab. This way, FPS won't work over TCP/IP, and no
       one on The Internet can get to your computer. This is unique for
       each net card using TCP/IP.
     * 4.00.950B users only: NetBIOS: If you don't use Client for MS
       networks over TCP/IP, you have the option of disabling NetBIOS
       over this protocol, which saves some bandwidth and avoids the
       dreaded RNAAPP bug. If you use Client for MS over any other
       protocol, you must disable the binding between TCP/IP and Client
       for MS networks before it will allow you to turn off NetBIOS over
       TCP/IP.
       
   perin@onyx.interactive.net spent a considerable amount of time
   developing a BOOTP add-on for Win95. If you want to use BOOTP instead
   of DHCP, install his add-in software. You can find it at
   http://www.interactive.net/~perin/

     * 8.1.2. How do I set up TCP/IP through a modem? (Follow exactly to
       the letter, or else!) 
       
   Make sure you installed Dial-up Networking from Add/Remove
   Programs/Windows Setup. Then make sure you have the Dial-up Adapter
   installed in your Network setup. Then add TCP/IP. Follow the
   guidelines for net cards, except use these settings:
     * IP address: Obtain IP address automatically
     * WINS Resolution: Disable WINS resolution
     * Gateway: leave blank unless your provider gave you a Gateway
       address, if so put it here
     * DNS: Disable DNS Resolution (We insert DNS addresses later!)
     * Advanced: Nothing, but turn off "Use this as default protocol".
     * Bindings: Definitely turn off the FPS for MS networks binding if
       you have it.
       
   Then re-boot, double-click on your Dial-up Networking folder and make
   a new connection. The modem configuration may be whatever you like,
   but your Server type must have these settings:
     * Server type: PPP (Win95, Win NT 3.5, Internet) (You can do
       SLIP too, contrary to popular belief)
     * Log on to network: OFF (This prevents disconnects if you're logged
       into a NetWare network)
     * Enable Software Compression: OFF (Unless you're dialing into an NT
       dial up server, in which case this will really speed things up!)
     * Require Encrypted password: OFF (Again, only useful if you're
       dialing into an NT dial up server)
     * Protocols supported: Only have TCP/IP turned on and the others
       OFF!
       
   Then in TCP/IP Settings:
     * Server assigned IP address: turned on unless your provider handed
       you one, in which case feed it here. It will automatically use
       Subnet mask 255.255.255.0.
     * Specify Name server addresses: Here's where you feed the DNS
       server addresses! Leave the WINS server addresses at 0.0.0.0 to
       disable WINS over the dial-up connection.
     * IP header compression: Turn ON unless your provider tells you not
       to.
     * Use Default Gateway: Turn ON unless your provider gave you a
       specific gateway address, and you put in your TCP/IP properties
       back in Network Setup.
     * Finally hit OK.
       
   The above settings work with 99% of all UNIX and NT dial up servers
   known to me. By hard-coding the DNS addresses here and specifying only
   TCP/IP, you prevent Win95 from sending unusual PPP requests to the
   dial up server, some of which can CRASH some UNIX dial-up servers. The
   Internet Setup Wizard automatically prepares a dial-up connection
   with all the proper switches set, except it turns on "Enable Software
   Compression", which you can turn off if you have troubles connecting.
   The next thing to turn off would be "Enable IP header compression" if
   you still have troubles connecting.
   
   If your provider requires a special login procedure, bring up
   properties for the dial up connection again, select "Configure...",
   and in the Options tab, turn on "Bring up terminal window after
   dialing". This will let you manually login to the dial up server. When
   you connect, log in manually, and activate PPP, however you're
   supposed to do it, then hit "Continue" or press F7, which continues
   the PPP negotiation. Learn your provider's login procedure, then read
   on to learn how to write an automated dial up script.

     * 8.1.2.1. Should I get the ISDN DUN 1.3 update if I don't have
       ISDN? 
       
   Dial-up Networking 1.3 fixes a few problems in the original DUN, but I
   haven't run into enough of them to suggest that everyone should
   upgrade. Microsoft makes DUN 1.3 available at
   http://www.microsoft.com/windows/downloads/contents/Communication
   s/dun13win95/default.asp
   
   You should get DUN 1.3 if:
     * You use Point to Point Tunnelling Protocol (PPTP) at all
     * You need to connect to multiple TCP/IP networks at the same time
       (such as two ISPs, or an ISP and a local LAN where the LAN has a
       router or two)
     * You need to get all the TCP/IP bugfixes with minimal fuss
     * You want to run a dial-up server and don't have MS Plus
         * 8.1.2.2. Can I use two modems at the same time to speed up my
       connection? 
       
   Depending on your ISP's policies for such things, yes you can. Get the
   DUN 1.3 update to install Multilink capability.
   
   To enable Multilink in DUN 1.3:
     * Bring up your dial-up connection's properties (right-click on the
       connection icon, hit "properties")
     * Select the Multilink tab
     * Hit Add to add modems and phone numbers to the list.
       
   NOTE: Your ISP may have policies against multiple connections. Phone
   lines are not cheap. Also note that you may be billed at twice your
   normal connection rate.

     * 8.1.2.3. How come TCP/IP routing past my router doesn't work if I
       have a net card AND dial-up? 
       
   This is actually a classic bug in Microsoft's implementation of TCP/IP
   that existed since MS introduced PPP into NT Workstation 3.5. What
   happens is, you have one gateway (Your LAN's router) and you have a
   "Hop count" of 1 to the rest of your inter-network. When you establish
   a dial-up connection, the dial-up connection's gateway (the dial-up
   server) has a hop count of 1 and your LAN's gateway will have a hop
   count of 2, so when your machine needs to access a machine past your
   local subnet it'll try to reach it through the dial-up gateway instead
   of your LAN's gateway. (phew! How's that for an explanation?) This, of
   course, won't work.
   
   You can actually view this with:

ROUTE PRINT

   from a DOS session. Try it before and after you dial up.
   
   You have three fixes you can try:
    1. Don't use TCP/IP on your LAN connection. Use NetBEUI or IPX
       instead, and disable bindings between TCP/IP and your net card (by
       deleting that particular entry in the Network control panel).
    2. Install the Winsock 2 update or the Dial-up Networking 1.3
       update (DUN 1.3 includes Winsock 2). Winsock 2 allows for name
       lookups and sessions over more than one TCP/IP connection.
    3. Edit the routing table after you establish the connection. Say,
       for example, your machine lives in a subnet of 192.1.1.0 and you
       need to access a machine in the 192.1.2.0 subnet while you're
       simultaneously connected to the Internet via a dial-up. Type this
       at a DOS prompt:
       
route -f add 192.1.2.0  MASK 255.255.255.0  192.1.1.1

   This example describes the target subnet (192.1.2.0), the subnet mask
   of the target subnet (255.255.255.0), and the router with which to
   access that subnet (192.1.1.1). Thanks to Mike Ziemann for actually
   getting this to work. Please send me corrections if this is wrong!
   
   NOTE: Win95 doesn't save routing tables between reboots. You'll need
   to execute this after you establish a dial-up TCP/IP connection.
     * 8.1.3. How can I share one dial-up connection over my network? 
       
   We all heard of Wingate and how you could use an NT workstation as a
   dial-up router, but Wingate takes a LOT of TCP/IP knowledge, and NTWS
   routing requires some co-operation from your ISP, both of which are
   scarce. I suggest I-Way One, because it only requires ONE computer
   (albeit a Windows NT Workstation) running TCP/IP, and only one dial-up
   account. I-Way One replaces WINSOCK.DLL and WSOCK32.DLL and routes
   requests to these libraries to the one NT machine connected to The
   Internet, via NetBIOS or IPX.
   
   UPDATE 11 DEC 96: I-Way One isn't available from Workgroup
   Communications anymore, but I have copies. I've asked for permission
   from IXCHANGE (http://www.ixchange.com) to keep a copy on my
   server if it's legal I'll do so. This software is just far too useful
   to lose! In the meantime you can obtain it from ixchange.com.
   
   The only catch to using I-Way One vs Wingate is you end up replacing
   Win95 system components (The Winsock libraries) and it can't co-exist
   with any TCP/IP protocol on the client. It includes a library switcher
   which watchdogs the system and swaps these libraries as needed, but it
   makes more sense just to use I-Way One and no other version of Winsock
   on the machines.
   
   So, the quick instructions on using it: first set up one NTWS and make
   sure you can connect to your ISP using its included RAS software.
   Then, install the I-Way One server on it and the clients on the
   stations. The NTWS will dial out whenever a client needs any Winsock
   access, and hang up after some moment of inactivity. You don't need
   anything else special on the NTWS or on the clients.
   
   Another TCP/IP proxy exists from Technocratix. I have yet to try it,
   but you can help yourself to it at
   http://www.technocratix.com/webetc/
   
   Still another TCP/IP proxy to try is Microsoft's own Proxy Server, or
   the "re-released" Routing and Remote Access Service (previously
   code-named "Steelhead"). This allows an NT server to perform
   dial-on-demand routing.