Home
¦
Direct Cable Connections
¦
Null Modem connections
¦
Serial Ports
¦
Technical Page
¦
Build a home LAN
After several months of planning, editing and procrastinating, this page was finally updated on Monday, June 22, 1998.
I can personally vouch that once you get two or three computers, it is very handy to have them networked LAN-style.
Not only is this much much faster than something like direct cable connection, but once you get it setup, it's there every time you boot. (DCC needs you re-establish the connection manually) You can use your LAN to cutback on harddisk storage, and make backups of important data to other computers, and share resources like printers, zip drives, CD-ROMS, and so on.
Several years ago the networking scheme seemed a bit expensive but as time has passed, prices have fallen. Now you can hookup two or three computers easily for less than $100.
(I'm going to use the same layer model as I did on my direct cable connection page.) To complete a network, you need to setup the following layers:
Program Applications
_____________|________________
| |
Client for MS Networks File and Print Sharing
|______________________________|
|
NetBIOS
|
____________________________
| | |
TCP/IP IPX NetBEUI
|____________|_______________|
| |
Network Dial-up Adapter (PPP)
Card |
| |
(the physical medium) LAN Modems and ports
You already have program applications. For my purposes, these are programs like Excel, Word, Quattro, games, or basically any other application.
The second layer consists of your network client. Windows 95 has Client for Microsoft Networks built in, and this should be fine for anyone connecting machines with Microsoft operating systems. Software such as Novell Netware has served as the client for many years now. This really shouldn't be needed with Windows networks.
In the control panel, which can be accessed from the start menu, locate the icon called "Network." Double click this icon. This should bring up a box titled "network," which controls your network settings. (Image of the Network dialogue box)
If the client is not already installed, you can install it by clicking on the "add" button. From the next box, select "Client" and proceed. Finally, select "Microsoft" as the manufacturer, and "Client for Microsft Networks" as the client. This installation will probably require your Windows 95 source disks.
This step is required if you wish to share resources such as drive letters, folders, or printers on your computer.
To enable this, you need to first install File and printer sharing for Microsoft Networks. The setup process for this is nearly identical to that of installing Client for MS Networks.
After this service is installed, click in the button labeled, "File and Print Sharing." Select the appropriate check boxes.
You won't need to worry about configuring the NetBIOS layer. This will be done automatically. If I understand correctly, it is basically the way the upper layers communicate with the protocols.
This consists of the networking protocol that is used. The most common ones for LANs is IPX/SPX and NetBEUI. I would advise using these if you are setting up a simple home network. TCP/IP will work also, but requires some setting up before it will work. The first two I mentioned should basically just work once installed.
From the network dialogue box, click the "Add" button. From the next box, select "Protocol." Following this selection, select "Microsoft" as the manufacturer, then choose the protocol of your choice.
Your LAN should work with any one of the protocols installed (and configured). If you wish, you can install multiple protocols and the computer may switch back and forth during data transfers. The computer will manage that selection.
The network interface card (ethernet card) comprises the fourth layer of this model. Follow whatever steps you would follow to install most other devices.
Once the card is properly inserted into the machine, the proper software drivers need to be installed. Hopefully these drivers came on a disk along with the card and are easy to install. With luck there is an install utility on that disk. If not, you may be able to manually install the driver from within Windows. To do so, start the add new hardware wizard and follow the appropriate steps.
If the card was obtained as someone else's throwaway and you have no drivers, I would recommend letting Windows search for it and trying some generic drivers. Unfortunately, I probably cannot be much help with this.
Hopefully we have made it down to the last layer of our network model - the cable. Generally speaking, there are two types of cable that can be used. Those consist of category five patch cable, which is generally used with RJ-45 connectors, and co-axial cable, which is generally used with BNC connectors.
Cat5 cable is also called 10BaseT.
Co-ax cable is also called 10Base2.
The RJ-45 connector looks very similar to the standard telephone jack. (A telephone jack is RJ-11.) RJ-45 cables have eight wires, and therefore eight pins on the end of the connector. (Remember a telephone jack as four) Each wire is paired with another wire thus producing the potential of four pairs. In reality with regular ethernet, only four of the wires, two pairs, are used. (Continuing our telephone comparison, a phone wire also uses only on pair of wires)
In order for two RJ-45 networked machines to communicate, some wire crossing must be done. This means that the cable cannot be wired straigh through. This means that each pin number cannot travel to the corresponding pin number on the other end. (1-to-1, 2-to-2, 3-to-3, 4-to-4. . . 8-to-8)
When we make our RJ-45 cables, we wire them with a straight through configuration. This would pose a problem for our data transfer needs. Our solution to this dilemma is the hub. A hub is basically an adapter that switches the correct wire paths. It also serves as a signal amplifier.
If we have a very simple network that consist of exactly two computers,
we can bypass the need for the hub by making a cable that has the wire
crossings that a hub would do. Such a cable is called a crossover cable
and plugs directly from one ethernet card to the other. Though crossover
cables are used fairly often, many vendors don't have a clue what you are
talking about when you ask for one. If you have trouble finding a ready-made
crossover cable, you can find a shop that will custom make cables and specify
what you want. The appropriate pinouts are as follows:
1-3
2-6
3-1
6-2 Follow this
link for a graphic representaion
I made my own crossover cable with an ethernet cable and a terminal strip. Here is an image of my home made cable
___ ___
| | | |
|___| |___|
[_____] --------- [_____]
Crossover
PC#1 Cable PC#2
___ ___
| | | |
|___| |___|
[_____]\ /[_____]
PC#1 \ / PC#2
\ /
[Hub]
___ / \ ___
| | / \ | |
|___| / \ |___|
[_____] [_____]
PC#3 PC#4
BNC is co-axial cable. It is similar to what is used with televisions but has a smaller diameter. (Near that of a pencil) The fastening device for BNC is a push-and-twist contraption. About a quarter twist secures the cable to the T connector. A T connector is the piece that connects to the ethernet card. On each side of the T, a cable is connected. This arrangement leaves loose ends on each machine. These "loose ends" must be properly sealed off it what is called a terminator. (50 Ohm terminator)
Therefore, if you are connecting two computers via BNC, you would need two T connectors, a cable to reach between both stations, and two 50 Ohm terminators.
There are other specifics with BNC that I am less familiar with and would advise seeking knowledge beyond this page if you plan on using BNC. For example, some advise you should ground one of the terminators, others claim there is no need. I do not know which is best. Also, I have heard conflicting reports as to whether or not the terminator can be directly attached to the T connector.
___ ___
| | | |
|___| |___|
[_____] [_____]
| |
- === --------------- === -
Both types of media are capable of up to 10 megabits per second. In my opinion, RJ-45 is easier to deal with, but it makes no difference to functionality.
Listed below are the costs of the parts it would take to setup a network. These prices were taken from one store where I have done business before. I used that store in this example because it is the main one I am familiar with. There are many vendors who offer products at the same prices.
I figured all hub prices with 8 port hubs since they are only slightly more expensive than smaller hubs. I would recommend at least an 8 port hub.
2 Computer Setup
Two cards @ $12 = $24 25 foot Crossover Cable = $8 Shipping = $7 Total-------------------- $39
3 Computer setup with 8 port hub
Three cards @ $12 = $36 8 Port Hub = $35 Shipping = $7 Total-------------------- $78
4 Computer setup with 8 port hub
Four cards @ $12 = $48 8 Port Hub = $35 Shipping = $7 Total-------------------- $90
2 Computer Setup
Two cards @ $12 = $24 25 foot BNC Cable = $5 2 terminators = $3 2 T connectors = $2 Shipping = $7 Total-------------------- $41
3 Computer setup with BNC
Three cards @ $12 = $36 Two 25 foot cables = $10 2 terminators = $3 3 T connectors = $3 Shipping = $7 Total-------------------- $59
4 Computer setup with 8 port hub
Four cards @ $12 = $48 Three 25 foot cables = $15 2 terminators = $3 4 T connectors = $4 Shipping = $7 Total-------------------- $77
Prices reflect March 1998 prices at www.netlux.com
I had to guess the price of T connectors
Netlux was selected as an example solely because it was the first company I purchased
network equipment from