ETHERNET - NETWORKING (hopefully) SIMPLIFIED

The following instructions were written by Lloyd back in 97 when coax networks were common.  Today, in 2001, everyone uses a hub and RJ-45 cables. Hubs are cheap now.  

UPDATE 2005: Now everyone uses Windows XP which makes networking a lot more simple via wizards. However, problems do arise and the instructions here about setting up protocols may still be useful.  

If you have a cable modem or a DSL modem, you can use a hub to direct your Internet to all the computers in your house.  You can also use this network for multi-player games.  See the end of this article for more info on hubs. Rick Lee

 

Written by (c) Lloyd James on Wed Aug 6 13:38:28 1997 (editing later)

The following recipe is designed help the new networker setup a small net for home or office using Win95 (or Win98) networking and 10base2 (thinnet) coax. The following limitations for a 10base2 net should be considered (practical/physical):

6 computers practical, max = 30

300 feet total coax length practical, max = 607 feet

Minimum coax distance between T-connectors = 1.6 feet

Thinnet Coax cable is connected to each computer through a T-connector. Many adapter cards come with a simple T-connector. Terminators must be used at each end computer of the net, one of the ends/terminators should be grounded. You can either get terminators to fit into the open end of your end T-connectors, or you can get self-terminating T-connectors. The coax can be bought in various lengths at very reasonable prices. You don't want to try and make the cables yourself.

If your net will exceed these practical limitations, consider a 10baseT (hub) network. All that follows holds true for 10baseT (twisted pair) nets using a hub but the mechanics of setting up the hub are not included here. (For 2 computers only net you can use a crossover wired twisted pair cable connected to the RJ45 jack directly.)

A NIC (network interface card) adapter must be installed in each computer that is to be networked. While there are many good adapters available, if you are just starting I recommend an NE 2000 Compatible combo card (combo accepts both coax and twisted pair wiring). Many cards also have green and red status LEDs which are useful troubleshooting tools when problems develop. NE 2000 Compatible cards have a proven track record of dependability, ease of installation and error free reliability. Plug N Play is nice, but it should allow onboard jumpers (or software) to disable and set IRQ and Port Address just in case conflicts arise. NICs come in both PCI and ISA flavors with PCI having a slight premium in cost. (I have purchased PCI NE2000 combo cards for $24, and ISAs for $20.) Make this selection depending on your free slots in each machine. All things being equal buy the PCI card. There is no restrictions on using a mixture of ISA and PCI. You should be able to network for about $30 per computer total.

All the computers in the net must be using Windows 95 or 98 (or Windows for Workgroups) as the OS. (You cannot run DOS x.x or another operating system and use Windows 95/98 as the network vehicle.)

Note: The following procedures are very broad and are not designed with ANY level of security and will result in unlimited access on a Peer to Peer network. It IS designed to get network running and give you a feel for Win95 networking. After all is working and you are satisfied, then reenter the appropriate areas and restrict access, drives, folders, files, passwords, etc., to suit your requirements.

A. NIC installation (Adapter card and drivers; possible resource conflict/s)

Physically install the adapter (card) in an appropriate slot on the motherboard and install the drivers carefully following the instructions furnished with the adapter. Most cards come with a floppy that will install the card and drivers to most of the different network systems. Select the one appropriate to Windows95/98. Many times there are readme files that give additional information and help. After the adapter and drivers are installed reboot to Win95 and check for possible conflicts in Device Manager.

In Control Panel open System; click Device Manager tab; scroll down and click the '+' next to 'Network adapters'; you should have your network adapter and Dial-Up networking listed (assuming you installed DUN with Win95): click on your adapter* (mine = 'NE 2000 compatible'); if a yellow exclamation point or red halt icon (red circle with a slash) overlays the small green adapter icon a conflict is indicated; Either way, click on Properties;

General tab:

Device type = 'network adapter'; Manufacturer = 'your adapter' (mine says Novell/Anthem); Hardware version = your hardware version /or "not available". Device status box = "This device is working properly"; Device usage = checked box next to "Original configuration".

Resources tab:

Under Resource type look for 'Interrupt Request' and 'Input/output range" (note the IRQ and port address listed opposite each). In 'Conflicting device list' box look for "no conflicts". After confirming no conflicts exist and the adapter card is properly installed click on cancel (assuming you have made no changes) and go to the next item B. If conflicts are indicated or the card is not installed and recognized then you must go back and reinstall.

B. Clients, Adapters, Protocols, and Sharing

First, your computer must have Network Neighborhood (NN) installed. If You did not see this icon on your desktop: open Control Panel; Add/Remove programs; select Windows Setup tab; highlight Communications; click Details; check Dial-Up Networking; click OK; OK; follow the instructions.

In Control Panel open Network: On the configuration tab there are four items to confirm or install in 'The following network components are installed' window.

1. Adapters.

Step A. above should have installed your adapter. The 2nd and 3rd lines should indicate 'Dial-Up Networking' and 'Your Adapter'. NOTE: the NIC adapter can be installed here if you know the manufacturer and model. click Add; click Adapter; click Add; select the manufacturer and model; or Click Have Disk if you have an installation disk. NOTE 2: if you are installing a NE2000 compatible NIC you may use MS drivers for it - select Novell/Anthem in manufacturer; select NE 2000 Compatible in Network Adapters: Follow the installation applet)

2. Network client

The first item in the installed components window should be a small computer icon labeled 'Client for Microsoft Networks'; REMOVE any client except this and add it if not listed. Click 'Add'; click 'Client'; click 'Add'; in left window click 'Microsoft'; in right window click 'Client for Microsoft Networks'; click OK.

3. Protocols

These 4 protocols (protocol icon is a T-cable and connector) should be listed;

'IPX/SPX-compatible Protocol -> your Adapter' (refers to your adapter as listed above). This is the protocol needed for many multiplayer network games

'NetBEUI -> Adapter name' (refers to your adapter as listed above). This is the primary windows network protocol

'NETBIOS support for IPX/SPX-compatible Protocol -> IPX/SPX-compatible Protocol' A companion support for IPX/SPX

'TCP/IP -> Dial-Up Adapter' The protocol used for Internet (and some network) connection.

Add any missing protocols: Click 'Add'; click 'protocol'; click 'Microsoft'; click "protocol name"; click OK. Now it should be in the Network components installed window. Note: To install NETBIOS: Click IPX/SPX-compatible protocol; click properties; Click NetBIOS tab; (check) I want to enable NetBIOS over IPX/SPX

Remove unnecessary protocols: (You will find that some protocols will install with bindings to both your adapter and DUN. i.e. 'TCP/IP -> Adapter name' For the sake of simplicity and to forestall any possible conflict you should remove those extra protocols. For Win95 networking the four above are all that are needed.) Click on the redundant protocol; click 'Remove'

4. File and Print Sharing

Click on the wide button labeled File and Print Sharing; Check both items; Click OK. While here do a little laundry. Just above File and Print Sharing is the window labeled Primary Network Logon. Click the drop down arrow and select 'Windows Logon' (If 'client' is selected it necessitates a logon password procedure at startup.) One other item; Highlight 'TCP/IP -> Dial-Up Adapter' and click Properties; Click on Bindings tab; put check mark only at 'Client for Microsoft Networks'; remove check at 'File and printer sharing for Microsoft Networks' (prevents file access by others when connected on the Internet).

Click on the Identification tab. The first 2 items are mandatory. Type in a unique name for the Computer name:. (My 3 computer names are rather unique - p166, p100, and p60). Type in a name for the Workgroup: This same name (my Workgroup is HOME) will be entered on each computer in the network. Computer Description is an optional entry (I enter the primary user's name).

Click the Access Control tab. Check Share-level Access Control

At the bottom of the Network applet click OK. If changes or additions were made you will get the applet to insert MS Windows95 disk; do so; if the computer has trouble finding it you may have to point it out; X:\win95 ("X" identifies your CD-rom drive). After files are transferred you will be directed to restart your computer. As Nike says "JUST DO IT"

C. After bootup, resource sharing must be accomplished.

Open My Computer; Right click on 'C'; halfway down the menu is an item 'sharing'; click it; the Properties applet opens with the sharing tab active; check 'shared as'; check 'full' click OK; Repeat this step for each drive and printer (open printer folder; right click on local printer) on this computer you wish to share.**

Open Network Neighborhood; You should see a globe icon labeled Entire Network and computer icons for each computer connected on your net labeled with those earlier unique names. Double click on a computer icon You should see all the devices/drives you have elected to share i.e. "c" (harddrive c); "HP Deskjet 560" (printer); etc.

If you do not see any computers go to Start; Find; Computers; click Find now: if it come up with the answer '0 computers found' review these steps and also try Win95 network troubleshooter in 'Help'

D. Mapping Drives

Once you can see all the computers and the resources available open my computer and map each drive. If the toolbar is not visible click 'View'. On the toolbar next to the 'up one level' icon is an icon labeled 'map network drive' (place mouse cursor over it, label will appear after several seconds). Click on it; an applet opens with two dropdown windows labeled Drive: and Path: Click dropdown arrow in drive: the available drive letters appear; pick the 3rd available (my arbitrary choice) i.e. D, E, F, G. ...; pick F; In the path window type in; \\unique name\c (\\p166\c) as shown here drive c on the computer named p166 will be mapped to this computer using drive letter F. Click OK.

In rare cases, computers have been known to balk at adding more drive letters. The solution was to add a line to CONFIG.SYS saying: LASTDRIVE=Z

Open My Computer; the drive you just mapped should appear as network drive icon (drive with coax connected) labeled <C on 'p166' (F)>. Continue to Map each drive you wish to access from this computer. To map a network printer (printer not connected to this computer) open Printers in My computer; doubleclick Add Printer; click Next; bullet Network printer; click Next; click Browse; (you should now see network neighborhood) click the + next to the computer that owns the printer; click on the printer icon in the expansion; click OK; click Next; bullet Yes or NO to the default printer option; click Next; Again Yes or NO; click Finish and follow instructions for Win95 disk if needed.

MAY YOUR NET BE FULL OF ETHER

Your are now networked. Recommend the purchase of a wrist pad for your mouse hand while playing Deathmatch QUAKE to prevent carpal tunnel syndrome;) Many games and flight simulators will work in multi-player mode over your fine new network.

* Note: If you do not have an adapter listed you must install one. Either go to Add New Hardware in Control Panel or go to step "B. 1. Adapters" and install your adapter. After installation return and run through "A." again.

** Note: It is not necessary to share a whole drive; folders can be marked as shared in explorer. If you do mark a drive as shared then all folders and files on that drive are accessible on the network.

*** Note: BEWARE! BEWARE! Networking in Windows95 is a plus feature but it does not have good security. It works great and is easy to maintain in home or small office networks if you personally control access to the net. If you plan to operate in an environment where unauthorized access to files or data on the network could cause personal or business harm or you just don't want snoopers, Windows NT or another network system with access administration would be a better choice.

**ADDENDUM**:

2/21/99 from Lloyd:


1. Most NICs should come with WIN 95/98 drivers and these should be
installed instead of "NE2000 compatible" drivers. Recommend purchase only
card that has 95/98 drivers. Also, check for latest drivers available for
NIC. Especially if 'sync' errors occur. (had a dickens of a time tying to
play "Age of Empires" multiplayer. Kept getting disconnects. Downloaded and
installed the latest 'Realtek' drivers for my cards and all is well)

2. combo PCI NIC cards available now for under $20. Should be able to
network two computers for under $50.

3. Under Protocols the following paragraph could mislead.

"Remove unnecessary protocols: (You will find that some protocols will
install with bindings to both your adapter and DUN. i.e. 'TCP/IP -> Adapter
name' For the sake of simplicity and to forestall any possible conflict you
should remove those extra protocols. For Win95 networking the four above are
all that are needed.) Click on the redundant protocol; click 'Remove'"

A lot of the newer games (i.e. "Quake 2") require TCP/IP protocol to play
instead of IPX/SPX. No Problem except that each computer must have the
TCP/IP protocol for the NIC and Each computer must be assigned an IP
address.

To do this:

A. Open "Control Panel | Network"; Check if "TCP/IP->(your NIC) is present
(it should already be present with bindings to "DialUp Adapter"); If it is
present skip down to "B.". If not, Click 'Add'; Highlite 'Protocol'; click
'Add'; highlite 'Microsoft'; scroll down and highlite 'TCP/IP'; click 'OK';
(you will need the Win98/95 CD). This will add the TCP/IP protocol with
bindings to the NIC. After restarting enter "Control Panel | Network";
again.

B. Highlite 'TCP/IP->NIC' (NIC would be your adapter name); click
'Properties'; click 'IP' tab; bullet 'Specify an IP address'; On your first
computer on your net at the 'IP Address:' window enter "192.168.0.1". On the
second computer enter "192.168.0.2". Continue for each computer (damn can't
think of the word) adding a different digit in the last group up to "255"
but the first three groups should be same. (Note: "192.168.0.xxx" (xxx being
from 0 to 255) is the set of IP addresses assigned by convention to private
nets and their use while not mandatory is highly recommended. You could
enter "100.0.0.1", "100.0.0.2" and so on.) Enter in every (each) computer in
'Subnet Mask:' window "255.255.255.0". This must be identical.

Now you have a network which can use the TCP/IP Protocol. This will in no
way interfere with the TCP/IP protocol used for internet access through
DialUp Networking (modem connect).

ADDENDUM regarding HUBS (by Rick Lee, not Lloyd)

I recently changed my network from a coax system (using the black coax wire similar to cable-tv wire) to a hub-type system which uses the non-coax wire with the large RJ-45 phone type jacks.  I needed the hub to accommodate my new DSL modem. I bought an inexpensive 8-port 10baseT hub and some cables and just hooked them up in my existing NIC combo cards (which have both the coax connection and the RJ connection).  To my surprise, the network continued to work just fine without ANY changes to my Windows 98 networking setup... which was set up using the above recipe. 

I plugged the DSL modem into the switchable port on the hub and flipped the switch until the little light came on signifying that it was working. I plugged the other computers into the hub and installed the DSL software from Bell Atlantic onto each of the computers.  Surprise... they were all able to connect to the DSL modem just fine.  

More info on home networking here.

 

Google
Web www.rickleephoto.com

Back to Rick's Flight Simulator Page

Rick Lee's Art Page

Rick Lee's Photography Page

Rick Lee's Home Page

Send Email to Rick Lee