NOTE: 03/15/05 This article was penned long before broadband became as widely available as it is today; both in DSL and Digital coax modem flavors. Accordingly, setting up a home network is a lot quicker with modern DSL/Cable Modems and combo Router/NAT/Hub boxes. With that in mind, there is still a great deal of complexity configuring most routers to take advantage of their internal hardware firewalls. In that regard, and considering the speed/power of modern PC's, I suggest you set the router to DMZ (pass ALL traffic) and use a good free software firewall like ZoneAlarm on each PC on your LAN. If there is any hair left on your head, this will save whats left. Now, if you are still on a dialup, read on.


SETTING UP A LOCAL AREA NETWORK

This article will explain how to share one PC's Modem (dialup TCP/IP Internet connection) with another PC in your home or office by creating a Peer to Peer LAN (or Local Area Network), using something called a PROXIE server. I will also attempt to describe in laymen's terms how it all works. First, the Internet is a Peer to Peer network. This means that every computer connected to the net has all the same functional capability of running client and server software applications. This statement assumes your Internet Service Provider gives you unfettered access and does not block ports or channels used to communicate. TCP/IP is the protocol or packet language of the Internet but for the purposes of this article you need not understand it.

Quick Note: Alternative to a Proxie server are Hardware Routers/Switches/Hubs (pricy) and NAT's or Network Address Translator. W98 comes with a sudo NAT builtin called ICS or Internet Connection Sharing. Sygate, a popular shareware program, is also a highly recommended 3rd party NAT used for home networks. A NAT has the big advantage of not requiring client software to be Proxie capable. However, a Proxie server is typically much simpler and need only be installed on the server computer (in this case, the one with the modem). If you can afford the money and are using a DSL or Digital cable, I would recommend you explore using one of the newer hardware Routers that combine a Switch and Hub all in one box. More on Routers later.

HOW A PROXY WORKS: Your server PC (the one with the modem that connects to the Internet) acts as an intermediate (or proxie) to relay request coming "from" any client computer on your LAN, via its Network Interface Card (NIC) and cable to the Server's NIC and then going "out" to the Internet via the Servers Proxie and ultimately the servers modem; then the Proxy listens for a reply and when it arrives, sends it back to the precise client on your LAN that made the original request to begin with. Read this paragraph several times until it makes sense to you.

Let's use a Web Browser to illustrate. Normally a web browser send's a request to the Internet using port 80. This will work fine for a Browser located ON the Server (the one with the modem) because it has the direct dialup Internet connection. But, it will not work for the client PC - which must relay traffic through it's NIC to the Servers NIC. This is because the Servers NIC does not have a direct pathway to the modem. And even if it did, LAN PC's are identified with non routable IP's that cannot traverse the backbone routers on the Internet anyway. The Proxy solves the problem. It does this by listening on the Servers NIC to intercept Internet access requests coming from client PC's on the LAN and reroute the request to and from the modem's connection to the Internet.

In the case above the Proxie listens for HTTP request from the Client (through the NIC) on port 8080 (a commonly used http proxy port), and accordingly, the client browser must be "set up" to use port 8080 to "send" its request. The Proxie, after receiving a request from the client PC, re-sends the request through the modem connection to the Internet, but with port 80 restored in the packet datagram, along with the Servers routable IP address. The Proxy remembers what client IP originated the request and listens for replies and forwards any replies received back to the requesting client.

The result of all this is the client PC "behaves" as if it has a direct connection to the Internet, which is what you want. One advantage to a Proxie is it can also be used as a sudo firewall, preventing a client PC from reaching particular Internet services, or preventing penetration from hackers on the Internet who might try to get into your LAN.

To use a Proxi server, the client software on the client machines must be capable of communicating through a Proxi server. Most good clients like MS's Internet Explorer have this adaptability. Its mostly a matter of changing port settings in the clients setup configuration and or activating its proxie functions. Proxie applications are designed to monitor or MAP a wide range of ports to cover all standard services such as HTTP (the web), NNTP (newsgroups), SMTP (email), FTP (file transfers), TELNET (terminal communications).

In addition, a good Proxy software package should be Socks4 or Socks5 compliant - which helps automate port acquisition and socket connections on the server computer. More about this at the end of this article including info on a product called Hummingbird Socks that dynamically configures everything on the client for you, and does so on the fly.



SETTING UP A HOME LAN:

SHARING SERVER - This is the computer (or hardware device) that is directly connected to the Internet, generally via some sort of modem. This can also referred to as the Gateway or Router.

CLIENT - This is the computer that is not directly connected to the Internet. It depends on the Sharing Server for its connection.

Before your computers can share a dialup Internet connection, they need to be able to share with each other! This means that you'll have to connect them together to form a LAN. A LAN is two or more computers with interconnected NIC's (Network Interface Cards) bound to a network protocol; in this case, because you desire to communicate over the Internet, the TCP/IP protocol is required. However, several protocols can co-exist on the same local network; the number and kinds depend on your total needs.

NetBEUI (another W9+ Protocol) is an acronym which stands for NetBios Extended User Interface. It comes with W95/8. NetBEUI is a networking standard well suited for small networks and is easy to set up. It is also "non-routable" meaning, since it uses computer "names" or local non routable IP's to find its way around, it cannot be accessed from distant computers on outside networks. With NetBEUI you can access hard drives and printers on any LAN machine typically faster than with tcp/ip.

Network Interface Cards (NIC's)

There are several types of NIC's on the market. The more popular ones used for small home networks are Ethernet Base10 cards that communicate at 10mbps. Later ones can talk at 100mbps. The later cards are generally PCI types and have the advantage of easier setup on a Windows platform vi Plug and Play. The older (16 bit) ISA cards generally require manual configuration with finding an available (free) IRQ (the most difficult task). However some ISA (16bit) NIC's can be found with plug and play. Just takes some shopping.

NIC's typically use BNC and or RJ-45 Modular Phone jacks on the back of the cards to interconnect together. For coax, thin line (RG-58) 50 ohm cable is used. For modular, CAT4 ot CAT5 copper wire via the RJ45 jacks. Selection of the type jack to use is either done by manual jumpers on the NIC, or a software utility program; or, some NIC's can sense the jack being used automatically. Make sure you know which before proceeding. There are length limitations for cabling but its generally over 600 feet and usually inconsequential for home networks.

If more than two computers are involved in your network you must have a HUB; which is basically a multi cable repeater/amplifier distribution box. The HUB plugs into the Server PC's NIC and from there offers multiple jacks to support multiple client NIC's. HUB's come in various configurations with price varying upward with complexity.

Crossover Cable

A HUB is not necessary for a simple two computer network. If you prefer you can make use of a special CROSSOVER cable (CAT3 or 5 twisted pair with 8 pin RJ- 45 modular connectors) running between the two Nics. Four lines (wires) must be crossed in the cable as indicated below.

pin<------------>pin
1 <-------------> 3
2 <-------------> 6
3 <-------------> 1
4 (not used)
5 (not used)
6 <-------------> 2
7 (not used)
8 (not used)

For Coax connected systems: Use BNC "T" connectors at each and every NIC with the center of the "T" connected directly to the NIC. On the Server's BNC "T" connector, use a "GROUNDED BNC 50 ohm Terminator" on the open end. Also use a standard 50 ohm Terminator on the free side of the "T" at the very end of the backbone run (last connected PC Client).

In general, don't change the DialUpNetworking TCP/IP settings if you have already been sucessfully using a dial up modem to connect to the Internet. You should only have to touch the settings for the NIC's that are connected to your LAN.

If your Client is a laptop and you have to move it between multiple locations, or your ISP provides you a dynamic IP with each login vi a DHCP server, the easiest thing to do is set up TCP/IP to obtain an IP address automatically.

NOTE: For FASTER dialup connections to your ISP, make sure that you uncheck "Log on to Network" on the Server Types tab of your DialUp Connection Properties. This will greatly speed your modem connection to your ISP, and remove a possible security risk to your LAN. This only needs to be checked if you are sharing Files and Printers on your ISP's network... pretty unlikely!

NOTES about private LAN IP's: If you several computers, then feel free to use any numbers between 192.168.0.1 and 192.168.0.254. Just remember that each machine must have its own unique IP address.



ENTER THE FOLLOWING INFORMATION via Control Panel/Network for the TCP bound NIC in your SHARING computer (the one with the modem) You can also gain access by a Rt click the Network Neighborhood Icon on your Desktop and then chose Properties).

Set this NIC's IP address to 192.168.0.1
with a Subnet Mask of: 255.255.255.0
WINS Configuration: Disable WINS resolution
Gateway: Make sure there are NO entries.
DNS Configuration: Leave this alone (no DNS) (DNS settings apply to all NICs in a given computer, so you can't set them differently for the LAN NIC).

If your ISP uses DHCP to assign you an IP address, then this will probably be disabled because the DHCP server takes care of giving your computer the DNS and Gateway server information it needs.

If your ISP has assigned you a static IP address, this will probably be enabled and other information will be filled in when the first NIC was set up.

At any rate, don't change the DNS setting.

Bindings: Check Client for Microsoft Networks. File and Printer Sharing for Microsoft Networks is optional.

Advanced: make sure the "Set this protocol to be the default protocol." is checked if other protocols are involved.

NetBios: no changes.



TCP/IP SETTINGS FOR THE NIC IN A CLIENT COMPUTER. Access Properties the same way as mentioned up above.

IP address: set IP to 192.168.0.2
Again, use Subnet Mask: 255.255.255.0
WINS Configuration: Disable WINS resolution
Gateway: Make sure there are NO entries.
DNS Configuration: set to Disabled
Bindings: Check Client for Microsoft Networks and File and Printer Sharing for Microsoft Networks.

Advanced: make sure the "Set this protocol to be the default protocol." is checked.

NetBios: no changes. That should be it for TCP/IP installation.



SHARING FILES and PRINTERS Option

If you elect to use "File and Printer Sharing" you must make sure each client uses the same Workgroup Name; and, that the PC with modem (the server) is set to "Browse Master Enabled" (in the File/Printer sharing setup) and all the client PC's are set to "Browse Master Disabled". Dont forget to access each Drive and Printer on each computer vi the "My Computer" Icon and "Enable" them for "sharing". Once activated, a hand will appear on each drive or printer icon on the local machine; and a network pipe symbol on all the remote "active" devices. No pipe or grayed out means the device appears dead. NOTE: It takes several minutes after bootup for each PC to "see" the shared hardware of the other, so expect a delay, its normal.



INSTALLING AND CONFIGURING YOUR PROXIE SERVER

Read the authors setup instructions carefully and take your time. I believe in KISS, "keep it short and simple"; and something thats GOOD plus FREE makes it even harder to pass up. I recommend a very compact highly efficient Proxie server called THE HANDY DANDY ANALOGX PROXY SERVER. This proxie is so small and powerful, its hard to believe it does what it does. For running a simple Web Browser and E-Mail program on your Client PC's, Analogx does a very respectable job.

Download it from ANALOGX PROXY SERVER

For a more configurable Proxie as well as Socks5 support, I recommend something called Spoon Proxie by Pi-Soft Computing.

Download it from Pi-Soft Consulting Corp.

Finally, to eliminate a lot of arcane Proxy port mapping on your server PC while running apps like Yahoo, AIM and PalTalk on your client computer, I recommend you install a Socks Gateway. A solid version called Hummingbird Socks installed on your client PC is FREE for private users. You can download it from Hummingbird Socks



TESTING YOUR NETWORK with PING:

After you configure the Network software and set the IP addresses, use the ping command on the Sharing Computer to make sure all of the computers are "alive" (at least in the TCP/IP sense).

NOTE! You will not be able to ping your ISP or any Internet address from your Sharing Clients until you install your Sharing software. This is because they are on separate subnets and require the Sharing software to route (or move) data between the subnets.

To do this, go to the Windows Start button, choose Programs, then MSDOS Prompt. When you get the C: prompt, type ping 127.0.0.1 If everything is ok, you should get the following response (or something similar):

Pinging 127.0.0.1 with 32 bytes of data

Reply from 127.0.0.1: bytes=32 time<10ms TTL=32
Reply from 127.0.0.1: bytes=32 time<10ms TTL=32
Reply from 127.0.0.1: bytes=32 time<10ms TTL=32
Reply from 127.0.0.1: bytes=32 time<10ms TTL=32

This means that TCP/IP is working on the machine that you are typing on. 127.0.0.1 is a special address that "loops back" to the machine you are pinging from. You can also type ping localhost and receive a similar response, since localhost and 127.0.0.1 mean the same thing.

If things aren't ok, you'll get something like:

Pinging 127.0.0.1 with 32 bytes of data

Request timed out.
Request timed out.
Request timed out.
Request timed out.

If the above "pinged" ok, next you should ping your modem's IP. This is the second network that connects to your soon-to-be shared computer, and is a subnet of your dial-up ISP. You first need to go on-line before you perform this next check. So connect to your ISP as you normally do first.

Type ping [yourISPIP] where [yourISPIP] is the IP address temporarily assigned to you by your ISP. You should get the proper "Reply from..." response.

You can use the winipcfg command to find out your temporary IP address. An example winipcfg screen is shown below. Make sure that you set the drop-down selection box to "PPP Adapter".

You need to be on-line to see this information.

If all of that is ok, then you're on a roll, so you might as well ping your sharing Clients! They will have IP addresses of 192.168.0.X, so go ahead and ping 'em.

You can also try pinging the NIC on the Sharing computer from your Client computer(s). Also try Client to Client if you have more than one. Just don't try to ping your ISP or anything other than the computers on the LAN from your Client computers.

IN CONCLUSION..........

If you've followed directions and the Force has been with you, your LAN should be working with TCP/IP now. TCP/IP will work invisibly (in the background) on your client PC or PC's. That is, there will be nothing obvious to indicate its functional or operational. But the moment you boot up, any Net client software you run should immediately be able to communicate using tcp/ip.

Remember, with "File and or Printer Sharing enabled there may be a delay after booting before the server/client PC's "Icons" appear in the "Network Neighborhood" window. This is perfectly normal.

PRINTING WITH A SHARED PRINTER: Selecting the "Print" command within any application should reveal any Network printers currently available. Its always a good idea when first installing a shared printer to print a "test" page to ensure there are no hardware difficulties.

FILE SHARING: From within the "Windows Explorer" file manager utility, you should see the remote PC's hardware listed under the "Network Neighborhood" folder/icon; and, be able to drag and drop (copy and move) files from your server drive(s) to any networked drive(s), or vice versa, by manipulating the left and right window pane views. Likewise, when operating any applications that use data files (and that can be configured where to find them), network drives are now as accessible as the former "local" drives were.

FINAL CAUTION: If you allow "Shared File Access" on your LAN while connected to the Internet, you should operate a basic firewall like ZoneAlarm (which is FREE to private users) to prevent hackers, worms etc from infiltrating your Server through the Internet.



DSL and DIGITAL Cable sharing ALTERNATIVES

If you have twisted pair DSL or Digital cable Internet service, you can eliminate the need for a Proxy by simply using a Router/Hub (like the popular NetGate box) between your incoming DSL modem and the NIC's in each client. You might wish to pay your ISP for an additional static IP for each client computer but the upside is each computer acts as if it had its own independent connection to the Internet with its own IP address. File sharing is still possible with this setup but requires a second NIC in each shared computer. See more info down below.

DEFINITIONS:
HUBS - SWITCHES and ROUTERS

A Hub is a device that connects multiple clients (PC's) together on a single network. You run a cable from the Server's NIC to the Hub then from the Hub to each client PC in a simple network.

A hub has shared bandwidth. If you have a 100 mbps hub and 5 users, if THEY all send information at the same time, each gets 20 mbps of bandwidth. Whereas with a 100 mbps SWITCH, everyone gets 100 mbps. Cascading is adding a hub/switch connected to another hub/switch. It's how you can get 30 users with 10 port devices.

A ROUTER, is a device that connects two or more networks together. When it gets an IP packet from one of the networks it decides, based on the IP address, which network to send it to. Routers and Hubs can be combined in one box. Routers can be software based as well. A Router is sometimes called a Gateway when used to access an outside Network.

With the barn storming arrival of DSL and Digital Cable we are also witnessing the arrival of newer, less expensive Routers; Routers that combine Switches, Hubs and DHCP servers all in one box. Couple this with the ability to purchase additional routable static IP's from the high bandwidth providers and you have the ingredients for a truly peer extension from the Internet to your LAN clients. Here are links to several Router manufacturers you may want to explore: NetGear and Barricade

PERSONAL NOTES: Since installing Network cards on PC's I have noticed an additional delay in the time it takes Windows to properly shut down. From contact with others I have concluded this is a normal time out activity of a networked windows PC.

PS: If you found this article useful, or found glaring technical errors, I would appreciate hearing from you. Contact me (Sage Yoda) at arc@bigfoot.com So Long!