Why set up a local area network?
When you have several computers, it can be convenient to connect them to each other to create a local area network (LAN). Setting up such a network costs very little, contrary to what people may think.
Here are a few advantages you could enjoy by setting up a local area network:
• File transfers;
• Sharing of resources (internet connection sharing, printer sharing, shared disks, etc.);
• Mobility (in the case of a wireless network);
• Discussion (mainly when the computers are remote);
• Network games.
Necessary hardware required:
To create an RJ45 local area network in Windows, you will need:
• Several computers running Windows (computers running two different versions of Windows can be part of the same network);
• Ethernet cards on a PCI or ISA port (with an RJ45 plug) or built into the motherboard. When applicable, make sure the diodes on the back of the network card light up when the computer is on and that a cable is plugged in! There are also network adapters for USB ports, particularly in the case of wireless network adapters;
• RJ45 cables in the case of wired networks;
• A hub, a device you can connect the RJ45 cables from the network's various computers to, or a switch, or, as an alternative option, a crossover cable if you want to connect just two computers.
Installing protocols
Protocols are the software components that will enable computers to communicate with each other. The main protocols for a local area network are as follows:
• TCP/IP: the protocol used on the Internet. You will need it if you decide to connect your local area network to the internet
• IPX-SPX: a simple protocol, sometimes used for certain video games.
• Client for Microsoft networks: Microsoft's proprietary protocol, enabling file sharing and printer sharing, among others.
By default, the operating system installs the common protocols, which will be sufficient for almost all users. Unless you have a specific need, you do not need to read the rest of this section.
To install specific protocols, open the properties of the desired network connection and click Install, then choose protocol or services.
Networking in Windows XP
To configure each computer, simply go to the control panel, then double-click "network connections" and right-click "local area connection", then choose properties!
The local area connection window displays the various protocols installed. To be able to share your files, play network games or use your printers, the following protocols need to be installed:
• Client for Microsoft networks
• File and printer sharing for Microsoft networks
• QoS packet scheduler
• Nwlink Netbios
• NWLink IPX/SPX/NetBIOS-compatible transport protocol (for old games)
• TCP/IP internet protocol
If one of these protocols is missing, click "Install..." and add it.
Each computer should then be assigned an address, called an IP address, to be able to communicate. To do so, select "TCP/IP Internet Protocol" and click "Properties".
IP addresses may be automatically assigned or manually defined; the latter is preferable for a small local network. We will commonly give these addresses:
Computer n°1
IP address: 192.168.0.1
Subnet mask: 255.255.255.0
Computer n°2
IP address: 192.168.0.2
Subnet mask: 255.255.255.0
...
Computer n°xxx
IP address: 192.168.0.xxx
Subnet mask: 255.255.255.0
Once the IP address has been assigned, simply close the window by clicking OK (The DNS (name servers) will be left automatic)
To have optimal functioning, it is useful to make sure the network's computers belong to the same workgroup. To do so, simply right-click "My computer" and select "properties". The "Computer name" tab shows the computer's name as well as the workgroup it belongs to. To modify the workgroup and assign the same one to all computers, simply click "Network ID".
Testing the IP configuration
Before doing anything else, you are advised to check the computer's IP configuration. Windows systems offer a command-line tool, called ipconfig, that lets you find out your computer's IP configuration. The output of this command gives the IP configuration for each interface; a computer with two network cards and one wireless adapter has 3 interfaces each with its own configuration.
To view your computer's IP configuration, simply enter the following command (Start/run):
cmd /k ipconfig /all
The output of such a command looks like this:
Windows IP Configuration
Host name . . . . . . . . . . : CCM
Primary DNS suffix . . . . . . :
Node type . . . . . . . . . . : Broadcast
IP routing enabled . . . . . . . . : No
WINS proxy enabled . . . . . . . . : No
Ethernet adapter wireless network connection:
Connection-specific DNS suffix:
Description . . . . . . . . . . . : Intel(R) PRO/Wireless LAN 2100 3A Mini PCI Adapter
Physical address . . . . . . . . .: 00-0C-F1-54-D5-2C
DHCP enabled. . . . . . . . . . . : No
IP address. . . . . . . . . . . . : 192.168.1.3
Subnet mask . . . . . . : 255.255.255.0
Default gateway . . . . . . : 192.168.1.1
DNS servers . . . . . . . . . . : 193.19.219.210
193.19.219.211
Ethernet adapter local area connection:
Media status . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Broadcom 570x Gigabit Integrated Controller
Physical address . . . . . . . . .: 0F-0F-1F-CB-99-87
The above report shows that the computer has two network interfaces, one of which is wireless. The name of the machine on the network is CCM.
The Ethernet interface connected to the local area network (network card) is not active since the cable is disconnected, but the wireless adapter is configured.
Machines on a same network must use a same address range (with different addresses) and a same subnet mask. In the case of a local network, connecting machines that do not have routable IP addresses, so-called private address ranges must be used.
The default gateway refers to, when applicable, the IP address of the machine offering internet access. DNS servers.
The DNS servers must correspond to the organization's DNS servers; most of the time these are the service provider's DNS servers.
Testing the connection
To test the proper functioning of a network, use ping utility. Ping lets you send a data packet to a network computer and lets you evaluate the response time.
To test the network thoroughly, simply open a command-line window, then successively carry out the following steps:
• ping the loopback address (127.0.0.1), representing your computer:
ping -t 127.0.0.1
• ping the IP addresses of the network's computers, for example:
ping -t 192.168.0.3
• ping the computer names, for example:
ping -t Mickey
• ping the computer used as gateway on the local area network, that is, the computer sharing its internet connection. It usually has the address 192.168.0.1:
ping -t 192.168.0.1
• ping the service provider's gateway. The address of the service provider's gateway can be retrieved using the ipconfig command on the computer being used as gateway on the local area network;
• ping the service provider's name servers . The address of the service provider's DNS servers can be retrieved using the ipconfig command on the computer being used as gateway on the local area network;
• ping a machine on the internet network, for example:
ping -t 193.19.219.210
• ping a domain name, for example:
ping -t www.google.com
If all this works, your network is ready to be used!
When you have several computers, it can be convenient to connect them to each other to create a local area network (LAN). Setting up such a network costs very little, contrary to what people may think.
Here are a few advantages you could enjoy by setting up a local area network:
• File transfers;
• Sharing of resources (internet connection sharing, printer sharing, shared disks, etc.);
• Mobility (in the case of a wireless network);
• Discussion (mainly when the computers are remote);
• Network games.
Necessary hardware required:
To create an RJ45 local area network in Windows, you will need:
• Several computers running Windows (computers running two different versions of Windows can be part of the same network);
• Ethernet cards on a PCI or ISA port (with an RJ45 plug) or built into the motherboard. When applicable, make sure the diodes on the back of the network card light up when the computer is on and that a cable is plugged in! There are also network adapters for USB ports, particularly in the case of wireless network adapters;
• RJ45 cables in the case of wired networks;
• A hub, a device you can connect the RJ45 cables from the network's various computers to, or a switch, or, as an alternative option, a crossover cable if you want to connect just two computers.
Installing protocols
Protocols are the software components that will enable computers to communicate with each other. The main protocols for a local area network are as follows:
• TCP/IP: the protocol used on the Internet. You will need it if you decide to connect your local area network to the internet
• IPX-SPX: a simple protocol, sometimes used for certain video games.
• Client for Microsoft networks: Microsoft's proprietary protocol, enabling file sharing and printer sharing, among others.
By default, the operating system installs the common protocols, which will be sufficient for almost all users. Unless you have a specific need, you do not need to read the rest of this section.
To install specific protocols, open the properties of the desired network connection and click Install, then choose protocol or services.
Networking in Windows XP
To configure each computer, simply go to the control panel, then double-click "network connections" and right-click "local area connection", then choose properties!
The local area connection window displays the various protocols installed. To be able to share your files, play network games or use your printers, the following protocols need to be installed:
• Client for Microsoft networks
• File and printer sharing for Microsoft networks
• QoS packet scheduler
• Nwlink Netbios
• NWLink IPX/SPX/NetBIOS-compatible transport protocol (for old games)
• TCP/IP internet protocol
If one of these protocols is missing, click "Install..." and add it.
Each computer should then be assigned an address, called an IP address, to be able to communicate. To do so, select "TCP/IP Internet Protocol" and click "Properties".
IP addresses may be automatically assigned or manually defined; the latter is preferable for a small local network. We will commonly give these addresses:
Computer n°1
IP address: 192.168.0.1
Subnet mask: 255.255.255.0
Computer n°2
IP address: 192.168.0.2
Subnet mask: 255.255.255.0
...
Computer n°xxx
IP address: 192.168.0.xxx
Subnet mask: 255.255.255.0
Once the IP address has been assigned, simply close the window by clicking OK (The DNS (name servers) will be left automatic)
To have optimal functioning, it is useful to make sure the network's computers belong to the same workgroup. To do so, simply right-click "My computer" and select "properties". The "Computer name" tab shows the computer's name as well as the workgroup it belongs to. To modify the workgroup and assign the same one to all computers, simply click "Network ID".
Testing the IP configuration
Before doing anything else, you are advised to check the computer's IP configuration. Windows systems offer a command-line tool, called ipconfig, that lets you find out your computer's IP configuration. The output of this command gives the IP configuration for each interface; a computer with two network cards and one wireless adapter has 3 interfaces each with its own configuration.
To view your computer's IP configuration, simply enter the following command (Start/run):
cmd /k ipconfig /all
The output of such a command looks like this:
Windows IP Configuration
Host name . . . . . . . . . . : CCM
Primary DNS suffix . . . . . . :
Node type . . . . . . . . . . : Broadcast
IP routing enabled . . . . . . . . : No
WINS proxy enabled . . . . . . . . : No
Ethernet adapter wireless network connection:
Connection-specific DNS suffix:
Description . . . . . . . . . . . : Intel(R) PRO/Wireless LAN 2100 3A Mini PCI Adapter
Physical address . . . . . . . . .: 00-0C-F1-54-D5-2C
DHCP enabled. . . . . . . . . . . : No
IP address. . . . . . . . . . . . : 192.168.1.3
Subnet mask . . . . . . : 255.255.255.0
Default gateway . . . . . . : 192.168.1.1
DNS servers . . . . . . . . . . : 193.19.219.210
193.19.219.211
Ethernet adapter local area connection:
Media status . . . . . . . . . : Media disconnected
Description . . . . . . . . . . . : Broadcom 570x Gigabit Integrated Controller
Physical address . . . . . . . . .: 0F-0F-1F-CB-99-87
The above report shows that the computer has two network interfaces, one of which is wireless. The name of the machine on the network is CCM.
The Ethernet interface connected to the local area network (network card) is not active since the cable is disconnected, but the wireless adapter is configured.
Machines on a same network must use a same address range (with different addresses) and a same subnet mask. In the case of a local network, connecting machines that do not have routable IP addresses, so-called private address ranges must be used.
The default gateway refers to, when applicable, the IP address of the machine offering internet access. DNS servers.
The DNS servers must correspond to the organization's DNS servers; most of the time these are the service provider's DNS servers.
Testing the connection
To test the proper functioning of a network, use ping utility. Ping lets you send a data packet to a network computer and lets you evaluate the response time.
To test the network thoroughly, simply open a command-line window, then successively carry out the following steps:
• ping the loopback address (127.0.0.1), representing your computer:
ping -t 127.0.0.1
• ping the IP addresses of the network's computers, for example:
ping -t 192.168.0.3
• ping the computer names, for example:
ping -t Mickey
• ping the computer used as gateway on the local area network, that is, the computer sharing its internet connection. It usually has the address 192.168.0.1:
ping -t 192.168.0.1
• ping the service provider's gateway. The address of the service provider's gateway can be retrieved using the ipconfig command on the computer being used as gateway on the local area network;
• ping the service provider's name servers . The address of the service provider's DNS servers can be retrieved using the ipconfig command on the computer being used as gateway on the local area network;
• ping a machine on the internet network, for example:
ping -t 193.19.219.210
• ping a domain name, for example:
ping -t www.google.com
If all this works, your network is ready to be used!
0 Comments
DID YOU LIKE THIS BLOG.