Home


Networking and Internet connection sharing for Windows

Setting up a LAN (local area network) in a home and then sharing a broadband Internet connection with Windows XP is supposed to be easy.  Well, it was. We used the LinkSys BEFSR41 4-port router.  Here's how we did it.

There are many alternative ways to set up a home network, so read:

What kind of LAN to build, and how to share the Internet connection?

Network hardware 

You have four main options for building a LAN:

  1. Hardwired -- Category 5 cables with male RJ-45 jacks at each end, Ethernet Adapter 10/100 or 10BT (network interface cards) in each computer, and some kind of Network Hub, Switch, or Router.  Advantages: oldest, simplest, best-tested.  Disadvantages: have to run wires through the house.
  2. Over the phone lines -- Use existing phone outlets in the house.  Advantages: use existing phone lines, if there are phone jacks in all the right rooms.  Disadvantages: quality and interference problems?
  3. Power (Home Plug) -- Home Plug Power line Specification 1.0 standard, providing up to 14Mbps bandwidth over home AC wiring. Since the home power lines are the most pervasive medium in households with multiple outlets in every room, the HomePlug USB Adapter allows multiple home desktops and notebooks to be networked to share Internet connectors, printers, files, and play games without any additional wiring.
  4. Wireless -- Home networking access between your wireless and Ethernet devices. Also, wireless devices enable your entire network to share an Internet connection through a cable modem or DSL modem that otherwise is used by a single PC. With minimum setup, you can install and use the router within minutes.  A few different standards to chose from 802.11a, 802.11b, or 802.11g.  Also Home RF was used to some extent.  Advantages: no wires at all.  Disadvantages: reception can be spotty, interference, sometimes difficult installation, and maybe security issues.

Hardware for sharing the Internet connection

Again there are a few options.

  1. A router/LAN switch like the LinkSys BEFSR41.  It acts as the gateway, assigning an IP address automatically to each computer on the LAN.  The ISP only "sees" one IP address at the house. Some ISP's require the hardware address of the device to allow access to their network, others may use a host name to allow access.
  2. A hub or switch if the above option is to much.  There may be a fee imposed by your Provider for extra ip addresses if you select this option.
  3. Two network cards in one computer, which is then designated as the gateway device.  Microsoft seems to promote this approach, Internet Connection Sharing.  It allows you to use your computer to act just like a router. You will still need a hub or switch with this setup to connect the rest of your computers.

Just two computers on one desk: You can use a crossover cable to hook together two computers that have network cards installed.  This is the absolute simplest LAN model.  It can only accommodate two computers.  It is possible to share an Internet connection if one of the computers is hooked to the Internet.

Peer-to-peer or client-server  Simple: peer-to-peer.  Most home users don't need the client-server model, which would require an upgrade to XP Pro anyway.

Security.  Whatever LAN you build, think security.  You don't want the outside world to find a way into the computers on your LAN.  Make sure that every computer is protected with a firewall and antivirus software.  Consider child-watching software to contain the kids when they wander out onto the Internet.  Also consider a pop up ad killer and an antivirus program.. Routers like the LinkSys BEFSR41 have a built-in hardware firewall.

Building a Home LAN

Model:

Hardware:

Software:

Most Routers do all of this:
 

Step 1 -- Hook a computer into the Router and hook the Router into the high-speed modem.

Step 2 -- Hook the other computer into the Router and get it connected to the Internet.

Step 3 -- Configuring your New LAN

    When you look at the network connections on both computers, You may not be able to see computer1 from computer2.  Computer1 knew that computer2 was on the network, but couldn't let me see the contents of computer2.  That's because I had not yet configured either computer's software to participate in the hardware LAN I had created.  You may need to specify a computer name and workgroup (ensure the workgroup is the same on all computers).   You may also need to turn on file and print sharing to share across the network.

Additions steps need to be taken for Windows XP, see below.

You've just bought a computer with Windows XP Home Edition or Windows XP Professional installed, and you can't wait to add it to your local area network. Or maybe you've upgraded an older computer to XP, and now it can't see the network at all!

Windows XP can network successfully with all other versions of Windows, but there are many potential traps and pitfalls. We'll help you avoid them, starting with a quick list of the main points, and then adding the details.
 

Top Ten Rules for Adding Windows XP to an Existing Network

  1. Even if it tells you to do it, don't run Windows XP's Network Setup Wizard on the other networked computers. You want to make the Windows XP computer conform to the existing network. The Wizard wants to make the rest of the network conform to XP.
     
  2. You must disable Windows XP's Internet Connection Firewall on a local area network connection to other computers. If it's enabled on a LAN, Internet Connection Firewall will block File and Printer Sharing
     
  3. To make most network settings, you must be logged on as a user that is a member of the Administrators group.
     
  4. Use the same protocol for File and Printer Sharing on all computers.
     
  5. Remove all network protocols that aren't required for a specific purpose.
     
  6. If you have multiple protocols, un-bind File and Printer Sharing from all but one. Using more than one protocol, even on just one networked computer, can make networking with XP unreliable.
     
  7. TCP/IP, by itself, works for all Windows networking functions.
     
  8. If you assign IP addresses manually, use the same IP subnet on all computers.
     
  9. NetBEUI isn't necessary.
     
  10. Use the same workgroup name on all computers.

Upgrading to Windows XP

You can upgrade a computer that runs Windows 98, 98SE, or Me to Windows XP Home Edition. Those same versions, along with Windows NT Workstation 4.0 and Windows 2000 Professional, can be upgraded to Windows XP Professional.

To ensure a smooth upgrade and avoid networking problems, follow these tips before starting the upgrade:

  1. Install all network cards. XP will detect them and automatically install the right drivers.
     
  2. Have your Internet connection available. The XP setup process will connect to a Microsoft server to download the latest setup files, including changes that have been made since XP was released.
  3. Some programs are incompatible with XP and can cause networking problems. Un-install these programs. After the upgrade is complete and the network is working, re-install XP-compatible versions of these programs:

     

Windows XP Networking Default Configuration

When it detects the presence of a network card, Windows XP automatically creates a connection named "Local Area Connection" in the Network Connections folder. The connection shows the type of card that XP detected. Some manufacturers use generic chipsets in their cards, and XP often identifies the card using the chipset name. For example, it identified a Netgear FA310TX card as "Intel 21140-Based PCI Fast Ethernet Adapter (Generic)". To see the connection's configuration, right click it and select Properties.

Windows XP automatically installs these items for a new network connection:

  • Client for Microsoft Networks, which allows the XP computer to access other computers on the network.
     
  • File and Printer Sharing for Microsoft Networks, which allows other computers on the network to access the XP computer.
     
  • QoS Packet Scheduler. Allows programs to reserve bandwidth for critical applications like streaming video (You can uncheck this box if you wish).
     
  • Internet Protocol (TCP/IP). TCP/IP is a core component of the XP operating system and can't be un-installed.



 

More to Know

If you've already run XP's Network Setup Wizard on the other computers, don't worry. Check the other computers' network settings and manually reset anything that the Wizard changed. The most likely changes are in the TCP/IP configuration and workgroup name.

Network Protocols:

In Windows XP networking, TCP/IP is the preferred protocol. It's automatically installed, can't be un-installed, and is used by default for all networking functions. This reflects the state of networking in the 21st century. With the widespread use of the Internet, which uses TCP/IP, other network protocols are fading away everywhere.

Windows XP provides one other supported protocol -- IPX/SPX -- and one unsupported protocol, NetBEUI. Unusual protocols that have been included in earlier versions of Windows (Banyan Vines, DLC, etc) are no longer available.

If you're setting up a new network that includes XP, TCP/IP is almost certainly the only protocol to use. If you have an existing network that uses IPX/SPX or NetBEUI, we'll show you how you can continue to use that protocol in XP.

To see the network components, including protocols, which are associated with a network connection, open the Network Connections folder, right click, the connection, and select Properties.

Here are the components that XP installs by default:

To see the settings for a particular protocol, click the protocol and then click Properties.

TCP/IP

By default, XP configures TCP/IP to obtain an IP address automatically. If there's a DHCP server on the network, it will assign the IP address and other TCP/IP settings to the connection. Otherwise, Windows XP will use Automatic Private IP Addressing to assign an IP address to the connection.

This default configuration should work, unchanged, to connect a Windows XP computer to a network that uses TCP/IP for File and Printer Sharing in these common configurations:

Using an Internet sharing program or a hardware router protects the local area network from access by other Internet users, so it's safe to use TCP/IP for File and Printer Sharing on the LAN. The computers have private IP addresses that aren't accessible from the Internet. No other protocol is needed.

If your network uses static IP addresses, click Use the following IP address and enter the configuration information. For example, here are possible settings for a network that uses a proxy server at IP address 192.168.1.1 for Internet access.  Every router is different, please check your manual for the correct ip addresses for the device.

IPX/SPX (Optional)

If the existing network uses IPX/SPX for File and Printer Sharing, you can add that protocol to the Windows XP computer. IPX/SPX is fully supported in XP. In the connection's Properties, click the Install button to add a network component. XP will ask what type of network component to install.

Click Protocol and Add.

Click NWLink IPX/SPX/NetBIOS Compatible Transport Protocol and click OK. Two NWLink items are added to the connection's Properties

NetBEUI (Optional)

NetBEUI was the default protocol in Windows 95, but Microsoft has been moving away from NetBEUI ever since. Starting with Windows 98, TCP/IP has been the default protocol, and NetBEUI has been available for installation as a supported protocol.

Starting with Windows XP, NetBEUI is unsupported. This doesn't mean that NetBEUI won't work! It means that:

Because it's been around for so long, some people think that NetBEUI is required, and they install it on all Windows networks. Actually, nothing in Windows networking has ever required NetBEUI. You can even un-install NetBEUI in Windows 95 and use a different protocol.

If your existing network uses NetBEUI for File and Printer Sharing, consider changing to a different protocol. Most networks can safely use TCP/IP. The main exceptions to this rule are when:

If, after considering all of the options, you decide to install NetBEUI on Windows XP, follow the instructions in this Microsoft Knowledge Base article. If the Welcome to Microsoft Windows XP screen appears when you insert the CD-ROM, click Perform additional tasks followed by Browse this CD.

If you have more than one local area network connection, this procedure will install NetBEUI on all of them. It isn't possible to install NetBEUI on a dial-up connection

You can un-bind NetBEUI from a LAN connection by opening the connection's Properties screen and un-checking the NetBEUI Protocol box.
 

If you have a new computer that didn't come with a Windows XP CD-ROM, see if the computer manufacturer will send you the CD-ROM or the necessary NetBEUI files. If that isn't possible, you'll have to use a different protocol on your network.

If you need them, here are instructions on implementing NetBEUI in Windows 2000.

Un-Binding a Protocol

By default, Windows XP binds an installed protocol to each network connection and service. You can remove the binding, preventing that service from using that protocol.

Open the Network Connections folder and click Advanced followed by Advanced Settings.

To see the bindings for a connection, click the connection name under Connections. The bindings appear under Bindings.

To remove a binding, un-check the corresponding box. For example, to use IPX/SPX instead of TCP/IP for file sharing, un-bind TCP/IP from both File and Printer Sharing and Client for Microsoft Networks.

 

File Sharing: The preceding information should get your new Windows XP computer on the network and enable it to access shared files on other computers. All that's left to do is enable sharing on XP so that other computers can access its files.

For Windows XP Home Edition, see our article on Simple File Sharing.

For Windows XP Professional, Simple File Sharing lets you share disks and
folders on a network where there are no concerns about security and no
need to control access to shared files. If you want more security and
control, see our article on Windows XP Professional File Sharing.

 

    XP Home's Network Connection Wizard presented a somewhat bewildering variety of options for choosing the type of network to set up.  A home networking tutorial at http://www.microsoft.com/windowsxp/home/using/howto/homenet/default.asp helps to make sense of the variety of options the Wizard presents.  XP Home would prefer you to designate one PC as the gateway and use XP's own firewall, but there are ways around that.  In fact the Wizard seems to be quite flexible.

    Our setup looks like this, except that the residential gateway and Ethernet network hub are combined into a single device (a Broadband Router).  This was the last option discussed at the Microsoft website, filed under "Other":

 Residential gateway

    A residential gateway like a LinkSys BEFSR41 router contains a firewall and replaces an ICS host computer as the central Internet connection.  The BEFSR41 uses NAT and TCP/IP port inspections.  Should a hacker manage to bypass the router's firewall, the only access gained is to the device, which is in effect empty. A disadvantage of a residential gateway is the extra cost it adds to putting together a network.  To be extra safe you can install a third party firewall on each PC (Zone Alarm Pro integrates with this particular router).  Please note if turn DMZ on through the router, this will open up what whatever computer that you select (Meaning they will see your computer and not the router).

Please also note for Gamers, if you host a server you will need to specify ports through the gateway device.  If you are playing certain games you may need to specify those ports as well. 

Step 4 -- Using your New Local Area Network


Here's tidbit:

Adding IPX/SPX is OK, but it is absolutely NOT necessary in order to make file and printer sharing work. Nothing in a typical Windows network requires IPX/SPX (or NetBEUI). TCP/IP, by itself, is sufficient to allow computers running Windows 95, 98, Me, NT, 2000, and XP to see each other and share files and printers.  If the network only works after adding IPX/SPX, something is wrong with the TCP/IP configuration. Make sure that : 

1. All computers should be in the same subnet.
2. NetBIOS over TCP/IP is enabled on all computers.
3. There are TCP/IP bindings for "File and Printer Sharing" and
"Client for Microsoft Networks" on all computers.
4. All other firewall programs, should be properly
configured. Disable them if you need to troubleshoot your new LAN.

 

Here's another tidbit:

"If you are using IPX/SPX, make sure the non-XP machines are set to "enable NetBIOS over IPX/SPX.  You'll find it under the properties for the IPX/SPX protocol.  Didn't need this before when peering two win98 machines."

Step 5 -- Security

    Opening up a computer to participate in a LAN also opens the computer to attacks from the Internet.   So it is critical that the LAN and all individual computers be protected with a firewall.  The LinkSys router contains a hardware firewall.  But in addition you can add a software firewall to the LAN.  Home network security reading: http://www.cert.org/tech_tips/home_networks.html

Here are my choices. 

Step 6 -- Tweaks and Troubleshooting


Home


© 2002-2006 copyright Olobahn.net - Design by Computerwarrior

Microsoft logo's are trademarks of Microsoft Corporation and All trademarks mentioned on this page are the property of their respective owners.