LAN 102: Network Hardware And Assembly
Cables And Connections Between Computers
Depending on the network architecture you choose, you might need to run cables. If you are installing a Fast or gigabit Ethernet network (both of which use UTP cables), you need cables that are long enough to reach comfortably between each computer’s network port and the network’s hub or switch.
Because HomePNA networks are based on your existing telephone line, the patch cord included with the NIC is usually long enough to connect with your existing RJ11 telephone jack. The HomePNA NIC has two jacks: one for the connection to the telephone line and the other to enable you to connect your telephone to the NIC. Be sure you use the correct jack for each cable; otherwise, your network won’t work. HomePNA enables you to use your telephone system for voice and networking at the same time.
Wireless network NICs use an external antenna to make the connection between computers. In some cases, the antenna is built into the NIC, whereas in other cases the antenna is attached to the NIC or needs to be extended from a storage position inside the NIC.
Switch/Access Point
UTP Ethernet networks require a switch if more than two computers will be networked. (You can use a crossover cable between two computers only.) Wireless Ethernet networks also require an access point if more than two computers will be networked or if the network will be used to share an Internet connection. Switches and access points are normally included in a wireless router. With a wireless router/switch as a starting point, additional switches or access points can then be added as necessary.
For a wired Ethernet network, use one or more switches of the correct speed with at least enough ports for each computer on the network. For a wireless Ethernet network, you need at least one access point, depending on the range of your wireless network. Most access points have a range of 150 to 250 feet indoors (and up to twice that distance or more outdoors), which is adequate for most homes and many small businesses. You can use high-gain antennas or add more access points if you need a wider area of coverage.
Configuring Your Network Software
Stay On the Cutting Edge: Get the Tom's Hardware Newsletter
Get Tom's Hardware's best news and in-depth reviews, straight to your inbox.
Windows 9x, 2000, XP and later normally install all of the networking software you need automatically. The following table shows the minimum network software configuration you must install for Windows peer-to-peer networking. Windows Vista and 7 use the Network and Sharing Center to configure peer-to-peer networking.
Minimum Network Software for Peer-to-Peer Networking | ||
---|---|---|
Item | Workstation | Server |
Windows Network client | Yes | No |
NetBEUI or TCP/IP* protocol | Yes | Yes |
File and print sharing for Microsoft Networks | No | Yes |
NIC installed and bound to protocols and services above | Yes | Yes |
Workgroup identification (same for all PCs in workgroup) | Yes | Yes |
Computer name (each PC needs a unique name) | Yes | Yes |
*If TCP/IP is used as the standard protocol, each workstation must have a different IP address—either manually assigned or received from a DHCP server built into a server, router, or gateway computer or device.
For more information about Windows Vista/7 and networks, see Scott Mueller's Upgrading And Repairing PCs, 20th Edition, “Networking with Windows Vista/7,” p. 832 (this chapter).
Use the Network icon in the Windows Control Panel to select your network settings. To set up your network, you’ll need the OS CDs, disks, or hard-disk image files and the network adapter drivers. Devices like routers, access points and switches either have software built-in (accessable via an internal web page) or they don’t need any software at all.
To install a network component, follow this procedure:
- Open the Network icon in the Control Panel.
- The Configuration tab is displayed; select Add.
- Select from the following:
Client—Select if you want to install the Microsoft or other network clients for your network. Every PC on a peer-to-peer network needs the Client for Microsoft Networks.
Adapter—This should already be installed, but you can use this option to install a new adapter.
Protocol—For a simple, non-Internet network with versions of Windows before XP, install NetBEUI. If you want to use Internet Connection Sharing along with networking, install both TCP/IP and NetBEUI. With Windows XP, use the Network Setup Wizard to configure TCP/IP easily.
Service—Install File and Printer Sharing for Microsoft Networks on any computer that will be used as a server. - Click the Identification tab. Enter a unique name for each computer on the network; use the same workgroup name for all computers on the network.
- Click OK. Supply the Windows install disc or other media as necessary to install the network components you requested.
You might need to reboot your PC to complete the process. After this is completed, you’ll be ready to share resources.
Networking with Windows Vista/7
Windows Vista/7 includes TCP/IP as its default protocol, enabling it to connect to other computers running Windows or other OSs. However, its network management and configuration processes are much different from those that earlier Windows versions used.
Network management is performed through the new Network and Sharing Center. The Network and Sharing Center displays the status of the network, the signal strength for wireless networks, the status of network discovery and the sharing of files, the Public folder (equivalent to the Shared Files folder in XP), printer sharing, and media sharing. The Network and Sharing Center can change these settings as desired and controls whether password-protected sharing is enabled or disabled. When this feature is disabled, Vista/7 acts like Windows XP with simple file sharing enabled. When this feature is enabled, you must set up users and assign them rights just you would with Windows XP Professional with simple file sharing disabled.
The Network and Sharing Center can also provide a map of your network, showing the relationship of devices such as routers and switches and Windows Vista/7–based computers on the network. To add Windows XP–based systems to the network map, you can install the Link Layer Topology Discoverer (LLTD) responder. To get this feature and learn how it works, look up Knowledge Base article 922120, “Network Map Does Not Display Computers That Are Running Windows XP,” at http://support.microsoft.com.
To add a protocol or component to a particular network connection, open Networks, select Network and Sharing Center, and select Manage Network Connections from the task list. Then right-click the network adapter and select Properties.
Other differences include enhancements in the use and management of wireless networks, improvements to the Windows Firewall, and improvements in the network repair and diagnostics procedure. Windows Vista/7 also adds support for network projectors and online meetings, using its new People Near Me and Windows Meeting Space utilities.
Current page: Cables And Connections Between Computers
Prev Page Putting Your Network Together-
KelvinTy O... I thought all CAT5 are able to transmit 1000Mbps signals BEFORE reading this article... It's kind of weird ~_~" that I can get 5.X MB/s download speed = ="Reply -
Reynod Don could you talk to Chris A and Joe and see if we could give a few hard copies of this book away as prizes for some of our users here in the forums who work hard to help others?Reply
How about a copy for each of the users who make the top ranks for the month of November ... under the Hardware sections of the forums?
:) -
JasonAkkerman They make it look like making a cable it so easy, and it is, after the first few tries. Also, making one or two cables isn't too bad, but don't let yourself get talked into making 50 two foot patch cables. Your finger tips will never forgive you.Reply -
xx_pemdas_xx JasonAkkermanThey make it look like making a cable it so easy, and it is, after the first few tries. Also, making one or two cables isn't too bad, but don't let yourself get talked into making 50 two foot patch cables. Your finger tips will never forgive you.I got talked into making 10...Reply
-
spookyman JasonAkkermanThey make it look like making a cable it so easy, and it is, after the first few tries. Also, making one or two cables isn't too bad, but don't let yourself get talked into making 50 two foot patch cables. Your finger tips will never forgive you.Reply
Oh I don't know. I have made several thousand patch cord over the past 18 years.
All you need is a high quality crimper, good cutters and small screw driver. You are set.
-
silveralien81 This was a great article. In fact it inspired me to buy the book. I'm happy to report that the rest of the book is just as well written. Very educational. A top notch reference.Reply -
neiroatopelcc Read the first page. Seems like well written stuff, but not exactly written for my type of user. Also it seems to be igoring a lot of stuff. For instance it sais the network runs at the speed of the slowest component and will figure it out on its own. This isn't true. If you run a pair of 1000TX capable nics on old cat 5 cable (without the e), it'll still attempt to run at that speed, despite the massive crc errors it might generate. Also, if you're running on 'old gigabit hardware' it won't nessecarily have support for 10Base-T speeds. Also, not all firmware has autonegotiate or automdix support, thus you sometimes have to specificly set the speed between links. This is mainly for fiber links though, which seem to have been ignored entirely.Reply
Anyway. As I said, I think it's well written and probably quite suitable for people who don't know anything about networks (except it seems to assume people know the osi model). I'll go see if the other chapters are equaly basic.