Showing posts with label netowrking. Show all posts
Showing posts with label netowrking. Show all posts

Tuesday, April 7, 2015

Common Preventative Maintenance Techniques Used for Networks

There are common preventive maintenance techniques that should
 continually be performed for a network to operate properly. 
In an organization, if one computer is malfunctioning, generally only that user is affected.
 But if the network is malfunctioning, many or all users are unable to work.
Preventive maintenance is just as important for the network as it is
 for the computers on a network. You must check the condition of
 cables, network devices, servers, and computers to make sure that
 they are kept clean and are in good working order. One of the biggest
 problems with network devices, especially in the server room, is heat.
 Network devices do not perform well when overheated. When dust gathers
 in and on network devices, it impedes the proper flow of cool air and 
 sometimes even clogs the fans. It is important to keep network rooms clean and change air filters
 often. It is also a good idea to have replacement filters available for prompt maintenance.
 You should develop a plan to perform scheduled 
maintenance and cleaning at regular intervals. A maintenance program
 helps prevent network downtime and equipment failures.
As part of a regularly scheduled maintenance program, inspect all cabling. Make sure that cables
 are labeled correctly and labels are not coming off. Replace worn or unreadable labels.
 Always follow the company’s cable labeling guidelines. Check that cable supports are properly 
installed and no attachment points are coming loose. Cabling can become damaged and worn.
 Keep the cabling in good repair to maintain good network performance. Refer to wiring diagrams 
if needed.
Check cables at workstations and printers. Cables are often moved or kicked when they are
 underneath desks. These conditions can result in loss of bandwidth or connectivity.
As a technician, you may notice that equipment is failing, damaged, or making unusual sounds.
 Inform the network administrator if you notice any of these issues to prevent unnecessary network
 downtime. You should also be proactive in the education of network users. Demonstrate to 
network users how to properly connect and disconnect cables, as well as how to move them, 
if necessary.

Network Cards


A NIC is required to connect to the network. The NIC may come preinstalled on a computer, or you might have to purchase one on your own. You must be able to upgrade, install, and configure components when a customer asks for increased speed or new functionality to be added to a network. If your customer is adding additional computers or wireless functionality, you should be able to recommend equipment based on their needs, such as wireless access points and wireless network cards. The equipment that you suggest must work with the existing equipment and cabling, or the existing infrastructure must be upgraded. In rare cases, you might need to update the driver. You can use the driver disc that comes with the motherboard or adapter card, or you can supply a driver that you downloaded from the manufacturer.
There are many types of network interfaces, as shown in the figure:

  • Most network interfaces for desktop computers are either integrated into the motherboard or are an expansion card that fits into an expansion slot.


  • Most laptop network interfaces are either integrated into the motherboard or fit into a PC Card or ExpressBus expansion slot.


  • USB network adapters plug into a USB port and can be used with both desktops and laptops.

Before purchasing a NIC, research the card’s speed, form factor, and capabilities. Also check the speed and capabilities of the hub or switch connected to the computer.
Ethernet NICs will auto-negotiate the fastest speed that is common between the NIC and the other device. For instance, if you have a 10/100 Mb/s NIC and a hub that is only 10 Mb/s, the NIC operates at 10 Mb/s. If you have a 10/100/1000 Mb/s NIC and a switch that is only operating at 100 Mb/s, the NIC operates at 100 Mb/s.
If you have a gigabit switch, you most likely need to purchase a gigabit NIC to match speeds. If there are plans to upgrade the network in the future to Gigabit Ethernet, make sure to purchase NICs that can support the speed. Costs can vary greatly, so select NICs that match the needs of your customer.
To connect to a wireless network, the computer must have a wireless adapter. A wireless adapter communicates with other wireless devices, such as computers, printers, or wireless access points. Before purchasing a wireless adapter, make sure that it is compatible with the other wireless equipment that is already installed on the network. Verify that the wireless adapter is the correct form factor for the customer's computer. You can use a wireless USB adapter with any desktop or laptop computer that has a USB port.
Wireless NICs are available in different formats and capabilities. Select a wireless NIC based on the type of wireless network that is installed:

  • 802.11b NICs can be used on 802.11g networks.


  • 802.11a can be used only on a network that supports 802.11a.


  • 802.11a dual-band, 802.11b, and 802.11g NICs can be used on 802.11n networks.

Network Installation Steps


Having a clear understanding of all the steps required to physically building a network improves the success of a project. You may need to install network cards, wireless and wired network devices, and configure network equipment.
When installing a wireless network, you can use a wireless access point or a multipurpose device. The Linksys E2500 is a multipurpose device that provides both router and access point capabilities. You have to decide where you want to install access points to provide the maximum range of connectivity.
After you have determined the location of all the network devices, you are ready to install the network cables. If you are installing the cable yourself, make sure that all the necessary materials are available at the site, as well as a blueprint of the network’s physical topology.
To physically create a network, follow these steps:

Step 1. Make sure all Ethernet wall port locations are properly marked and meet the current and future requirements for the customer. To install the cable in ceilings and behind walls, you perform a cable pull: One person pulls the cable, and another feeds the cable through the walls. Make sure to label the ends of every cable. Follow a labeling scheme that is already in place, or follow the guidelines outlined in TIA/EIA 606-A.

Step 2. After the cables are terminated at both ends, use a cable tester to make sure that there are no shorts or interference.

Step 3. Use a floor plan to find the locations for access points that allow maximum coverage. The best place for a wireless access point is at the center of the area you are covering, with line of sight between the wireless devices and the access point.

Step 4. Connect the access point to the existing network.

Step 5. Make sure that the network interfaces are properly installed in the desktops, laptops, and network printers. After the network interfaces are installed, configure the client software and the IP address information on all the devices.

Step 6. Make sure to install switches and routers in a secured, centralized location. All LAN connections terminate in this area. In a home network, you might need to install these devices in separate locations, or you might have only one device.

Step 7. Install an Ethernet patch cable from the wall connection to each network device. Check whether you have a link light on all network interfaces and on each network device port that connects to a device.

Step 8. When all devices are connected and all link lights are functioning, test the network for connectivity. Use the ipconfig /all command to view the IP configuration on each workstation. Use the ping command to test basic connectivity. You should be able to ping other computers on the network, including the default gateway and remote computers. After confirming basic connectivity, configure and test the network applications, such as email and the web browser.

OSI and TCP/IP Data Models

An architectural model is a common frame of reference for explaining Internet communications and developing communication protocols. It separates the functions of protocols into manageable layers. Each layer performs a specific function in the process of communicating over a network.

The TCP/IP model was created by researchers in the U.S. Department of Defense (DoD). The TCP/IP suite of protocols is the dominant standard for transporting data across networks and the Internet. It consists of layers that perform functions necessary to prepare data for transmission over a network. The chart shows the four layers of the TCP/IP model.

A message begins at the top application layer and moves down the TCP/IP layers to the bottom network access layer. Header information is added to the message as it moves down through each layer and is then transmitted. After reaching the destination, the message travels back up through each layer. The header information that was added to the message is stripped away as the message moves up through the layers toward its destination.

Application Layer Protocols
Application layer protocols provide network services to user applications, such as web browsers and email programs. Common protocols that operate at the application layer include HTTP, Telnet, FTP, SMTP, DNS, and HTML.

Transport Layer Protocols
Transport layer protocols provide end-to-end management of the data. One of the functions of these protocols is to divide the data into manageable segments for easier transport across the network. Common protocols that operate at the transport layer include TCP and UDP.

Internet Layer Protocols
Internet layer protocols provide connectivity between hosts in the network. Common protocols that operate at the Internet layer include IP and ICMP.

Network Access Layer Protocols
Network access layer protocols describe the standards that hosts use to access the physical media. The IEEE 802.3 Ethernet standards and technologies, such as CSMA/CD and 10BASE-T, are defined in this layer.

Install the Motherboard


The CPU, heat sink and fan assembly might be installed on the motherboard before the motherboard is placed in the computer case. This allows for extra room to see and maneuver components during installation.
CPU
Figure 1 shows a close-up of the CPU and the motherboard. The CPU and motherboard are sensitive to electrostatic discharge. When handling a CPU and motherboard, make sure that you place them on a grounded antistatic mat. Wear an antistatic wrist strap while working with these components.
CAUTION: When handling a CPU, do not touch the CPU contacts at any time.
The CPU is secured to the socket on the motherboard with a locking assembly. Before installing a CPU into the socket on the motherboard, make sure that you are familiar with the locking assembly.
Thermal compound helps to conduct heat away from the CPU. When you are installing a used CPU, clean the top of the CPU and the base of the heat sink with isopropyl alcohol and a lint free cloth. A paper coffee filter works well as a lint free cloth. This removes the old thermal compound. The surfaces are now ready for a new layer of thermal compound. Follow the manufacturer recommendations about applying the thermal compound.
Figure 2 shows thermal compound being applied to the CPU. In most cases, apply a very small amount of thermal compound to the CPU. The compound spreads out evenly under the weight and pressure of the heat sink and fan assembly.
Heat Sink and Fan Assembly
Figure 3 shows the heat sink and fan assembly. It is a two-part cooling device. The heat sink draws heat away from the CPU. The fan moves the heat away from the heat sink. The assembly usually has a 3-pin power connector.
Figure 4 shows the cable and the motherboard connector for the heat sink and fan assembly.
To install a CPU and heat sink and fan assembly, follow these steps:
Step 1. Align the CPU so that the Connection 1 indicator is lined up with Pin 1 on the CPU socket. This ensures that the orientation notches on the CPU are aligned with the orientation keys on the CPU socket.
Step 2. Place the CPU gently into the socket.
Step 3. Close the CPU load plate. Secure it in place by closing the load lever and moving it under the load lever retention tab.
Step 4. Apply a small amount of thermal compound to the CPU. Follow the application instructions provided by the manufacturer of the thermal compound.
Step 5. Align the heat sink and fan assembly retainers with the holes on the motherboard.
Step 6. Place the assembly onto the CPU socket, being careful not to pinch the CPU fan wires.
Step 7. Tighten the assembly retainers to secure the assembly in place.
Step 8. Connect the assembly power cable to the CPU fan connector on the motherboard.

Computer Assembly

Assembling computers is a large part of a technician’s job. As a technician, you must work in a logical, methodical manner when working with computer components. At times, you might have to determine whether a component for a customer’s computer needs to be upgraded or replaced. It is important that you develop advanced skills in installation procedures, troubleshooting techniques, and diagnostic methods. This chapter discusses the importance of component compatibility across hardware and software. It also covers the need for adequate system resources to efficiently run the customer’s hardware and software.





Network topology

Ø Network topology is the arrangement of the various elements (links, nodes, etc.) of a computer network
Ø In computer networking, topology refers to the layout of connected devices.
Network topological are categorized into the following basic types:

·         bus
·         ring
·         star
·         tree
·         mesh

v Bus Topology
Bus networks (not to be confused with the system bus of a computer) use a common backbone to connect all devices.

v Ring Topology

In a ring network, every device has exactly two neighbors for communication purposes. All messages travel through a ring in the same direction (either "clockwise" or "counterclockwise"). A failure in any cable or device breaks the loop and can take down the entire network.

v Star Topology

Many home networks use the star topology. A star network features a central connection point called a "hub node" that may be a network hub , switch or router .

v Tree Topology

Tree topologies integrate multiple star topologies together onto a bus. In its simplest form, only hub devices connect directly to the tree bus, and each hub functions as the root of a tree of devices.

v Mesh Topology

Mesh topologies involve the concept of routes. Unlike each of the previous topologies, messages sent on a mesh network can take any of several possible paths from source to destination.


Summary

Topologies remain an important part of network design theory. You can probably build a home or small business computer network without understanding the difference between a bus design and a star design, but becoming familiar with the standard topologies gives you a better understanding of important networking concepts like hubs, broadcasts, and routes.

DHCP, Dynamic Host Control Protocol


Ø The Dynamic Host Configuration Protocol (DHCP) is a network service that enables host computers to be automatically assigned settings from a server as opposed to manually configuring each network host.

v Advantages of DHCP  Over Manual Configuration Methods

*    Each computer gets its configuration from a "pool" of available numbers automatically for a specific time period
*    Configuration information can be administered from a single point.
*    Major network resource changes (e.g. a router changing address), requires only the DHCP server be updated with the new information, rather than every system.
NOTE THAT
*      if you have the option to set-up your client machines automatically, please do, as it will save you time and a lot of headaches.

v Disadvantages of DHCP  Over Manual Configuration Methods

*    For a network administrator this process can be time consuming.
*    Problems can occur when manually setting up your client machines.
*    The DHCP server can be a single point of failure in networking environments that only have one DHCP server.
NOTE THAT

*      if you have the option to set-up your client machines automatically, please do, as it will save you time and a lot of headaches.

Monday, April 6, 2015

Network Control: Peer-to-Peer Networks versus Client/Server


In the world of local area networks, there are basically two choices of network control, or network types: peer-to-peer and client/server. The choice of these two networks basically determines the relationship each PC or device on the network has with the other in terms of control.
A peer-to-peer network is a true democracy. Each PC on the network is equal to the other in that the PCs can communicate with each other directly, and do not have a centralized PC monitoring and controlling the communication on the network.
A client/server network, on the other hand, has a central authority figure that controls the communication and access to resources on the network. This centralized controlling PC is called a server.
NOTE
Servers are PCs that control access to different resources on the network. In a home network, this can be such things as printers, a central storage drive, MP3 files, and anything you can think of that can take advantage of the server's capabilities. The server generally has a bigger processor and more storage than other PCs, or the clients, on the network.
A network client is a PC on a client/server network that communicates to other PCs on the network community through the server. It takes advantage of the server's resources and is very similar to other "clients" on the network.
If the peer-to-peer network is like a democracy, the server in a client/server network is more a network "dictator." Don't worry; in reality, the server is not a bad guy, and there are actually sound reasons that many networks today are set up as client/server networks, which we will explore later.
But first, let's look at the relative characteristics of each type of network to help you better understand the differences. Table 3.1 outlines these differences.
Table 3.1 Peer-to-Peer Networks Versus Client/Server Networks
Peer-to-Peer Networks
Client/Server Networks
Each PC is an equal participant on the network
One PC acts as the network controller
PCs are not reliant on one PC for resources such as the printer
One PC controls access to network resources
Access to the network is not centrally controlled
Network access and security are centrally controlled
Can operate on a basic PC operating system
Need a special operating system
Are generally simpler and lower cost
Are generally more complex but give the user more control

As shown in Table 3.1, there are definite differences between networks set up as peer-to-peer and those set up as client/server. It should be stated that most home networks today are set up as peer-to-peer, because this network type is simpler and works great for the needs of the home user. Because most home networks today are set up to perform basic but important tasks such as sharing an Internet connection or multiplayer gaming, there is no reason for a user to consider a client/server network. However, we will discuss each type more in-depth, and this information will help you decide how you want to set up your network.
Understanding Peer-to-Peer Networks
When all PCs on the network are set up to act as equals, this is called a peer-to-peer network. Every PC shares its files and resources with the other PCs on the network. Communication among PCs is a direct link with no central network controller, such as a server.
As shown in Figure 3.1, the two PCs on this simplified network engage in direct communication, or peer-to-peer. In reality, the network can look as simple as this figure, with the PCs talking directly to each other through one cable. We will look more at the actual physical configuration of the PCs and cables later in this chapter.
Figure 3.1 A basic peer-to-peer network.
A basic peer-to-peer network can also be set up in which a piece of network equipment can facilitate this direct relationship. Remember the discussion in Chapter 2, "Home Network Building Blocks: What Makes Your Network Tick," about the network hub? The hub can, as described before, act as the central station for the direct, peer-to-peer communication between the different PCs on the network, as shown in Figure 3.2.
Figure 3.2 A basic peer-to-peer network using a hub.
At first it might not be apparent why you would want to use a hub in your network if you can connect them directly, NIC to NIC, with one piece of network cabling. We will discuss the benefits of each type of configuration in the second half of this chapter (in "Network Topologies"). For now you should know that it is easier to grow your network when you are using a hub, because you simply add a new connection from the PC to the hub.
Pluses of a Peer-to-Peer Network
The peer-to-peer network is the easiest type of network to set up. It does not require any software other than the operating system already on your PC, and it does not require the more complex configuration of a client/server network.
The following subsections cover all the advantages of a peer-to-peer network.
Simplicity
A peer-to-peer network is so basic that you don't need anything more than your PC's existing software, a couple of NICs, and some cable. In a wireless network, all the hardware you will need is two wireless NICs.
Peer-to-Peer Is Supported in Windows
Because most personal computers in homes today have some form of Windows, it is very easy to set up a home network. Of course, you need to have Windows 95 or a newer edition of Windows, but chances are that you do.
Low Cost
The cost to build a home network using peer-to-peer technology is lower than that for a client/server network because you do not need any special software or computer.
New Technologies for Home Networking Favor Peer-to-Peer
Technologies we will talk about in Part II, "Digital Plumbing: Network Wiring and Hardware Options," such as phone linepower line, and wireless networking, are built with the understanding that you will likely build a peer-to-peer network. This isn't to say that you can't build a client/server network with these technologies, but with these "no-new-wires" solutions, a peer-to-peer network is extremely simple.
What's Mine Is Yours
A peer-to-peer network allows each PC on the network to access resources on all the other PCs on the network. That Zip drive on Dad's PC, the laser printer downstairs on Mom's, the PC camera on Billy's PC—they're all part of the network community after you create a peer-to-peer network.
Potential Minuses of a Peer-to-Peer Network
Now that you have seen some of the advantages a peer-to-peer network can offer, you will explore some possible drawbacks peer-to-peer networks can hold. The following are the potential minuses of a peer-to-peer network.
Security
If a PC is on a peer-to-peer network, there is the chance that another PC on the home network will access files that the owner of the PC might not want accessed. Not that this will necessarily happen or that you have something to hide from other users (or do you?), but this is something to think about. However, Windows provides the capability to block access to certain drives, so this shouldn't be a worry for anyone who properly configures her network software.
PCs Down on the Network Can Cause the Network to Go Down
In some instances, a PC might not be working, either because of problems or because it has simply been shut off. In a basic peer-to-peer network that uses direct connections from PC to PC without a hub, this might cause a problem.
Network Speed
In a peer-to-peer network situation in which a hub or switch is not used (such as a phoneline network), it becomes a real possibility that the network can get bogged down when more than one user is using it at the same time.
Scalability
A peer-to-peer network is great for a home network with a handful of users such as three to five PCs. However, if one day you decide to go into business with Brad, your neighbor, and set up a network in your home, when you start to increase the number of users to 10 or beyond, you might want to consider moving to a client/server network.
Understanding Client/Server Networks
The other network type is a client/server network. As described earlier, client/server networks have more centralized control of the network through the network server.
As shown in Figure 3.3, the communication and services on the network are controlled through the server. The resources, such as Internet service and printer sharing, are controlled through the network server. If you were to set up passwords to get on the network, this would also be controlled through the server.
TIP
An important distinction to make here is that this does not mean that all communication needs to go through the server. In a situation in which a hub or network "central station" is used, Client A can communicate directly with Client B. However, the permission that enabled this direct connection was granted by the network "dictator," the server. Figure 3.3 is a conceptual diagram and doesn't show the use of a hub or switch that actually handles network "traffic."
NOTE
Network traffic is what we call the actual communication over the network. Network gurus like to use this term to describe how "congested" (see where we're going here?) or busy the network is.
Figure 3.3 Central control through a client/server network.
Considering that a client/server network is generally more complicated and expensive than a peer-to-peer network, you're probably asking yourself why you would ever need one. Here are the circumstances in which you might want to consider using a client/server network:
  • You expect that your network will grow over time and might exceed 10 users.
  • You have a PC that has a noticeable advantage in processor speed and disk drive (storage) space.
  • You need to control access to your network.
  • You want to be able to have greater management and monitoring control over your network.
  • You want to set up a Web server (a special server that creates Web pages on the Internet).
These are all reasons you should consider using a client/server network over a peer-to-peer network. A client/server network, because of a more robust operating system such as Windows NT or Net-Ware, allows the network administrator to have better control over who accesses what and allows monitoring of network traffic and usage patterns.
Choosing Between Peer-to-Peer and Client/Server: A Suggestion for Your Sanity
As you can see, you must weigh a few basic considerations when deciding between the two options. But to give you even more value from your investment in this book, I will make a suggestion that should ease your pain considerably:
Unless you feel very strongly that you should have a client/server network based on the answers you had to the previous questions, by all means go with the much easier solution of a peer-to-peer network.
So you might be shocked that I go so far as to suggest what you should use, but don't be. That's my job (and I'm an extremely nice person).
Not convinced? Let me go over a few reasons I believe you should consider a peer-to-peer network unless you are absolutely convinced a client/server is for you:
  • As I've mentioned repeatedly, peer-to-peer networks are much simpler. They use your basic PC operating system and the newer operating systems, such as Windows ME and XP, have built-in wizards to help you create your home network.
  • Network operating systems are more complex, and you will have to learn a whole new set of commands to get your client/server network operating to your liking.
  • Client/server networks are more expensive.
  • Most home networks have only five or fewer PCs, which is well within the capabilities of a peer-to-peer network.
  • Most important, in a peer-to-peer network you can share files, share printers, create passwords, and do most of the things you do with a client/server network.
Don't be surprised by that last statement. A peer-to-peer network can take advantage of the resources of different PCs within the network. If one has a larger hard drive, make that one the PC where you store all your large music and video files. If you want to use dad's laser printer in the den, make sure you ask him nicely to allow sharing. For a home network, in almost all instances, you can do all the things you want to do with a peer-to-peer network.
Here's one more reason to consider a peer-to-peer network. As I've mentioned before, new products aimed specifically for home networks are coming to market, and many of these are beginning to fulfill functions that a server might have done in the past.
For example, home routers or residential gateways are available today to provide basic security against hackers and allow for Internet sharing, two functions that could have been administered by a server in the past. Media servers and network storage drives are available that allow you to store large multimedia files such as movies and music in a "media tank." Some of these products are even designed to plug right into your stereo system or TV so that they won't look like a PC sitting awkwardly in your living room.
Because I feel so strongly that a peer-to-peer network is a great fit for a home network, the rest of this book focuses mainly on explaining how to set up and use a peer-to-peer home network.


Advantages and disadvantage of Peer-to-peer networking over Client –Server networking

Advantages of Peer-to-peer networking over Client –Server networking are:-
It is easy to install and so is the configuration of computers on this network,
2) all the resources and contents are shared by all the peers, unlike server-client architecture where Server shares all the contents and resources.
3)  P2P is more reliable as central dependency is eliminated. Failure of one peer doesn't affect the functioning of other peers. In case of Client –Server network, if server goes down whole network gets affected.
4)  There is no need for full-time System Administrator. Every user is the administrator of his machine. User can control their shared resources.
5)  The over-all cost of building and maintaining this type of network is comparatively very less.
Disadvantages (drawbacks) of Peer to peer architecture over Client Server are:-
1) In this network, the whole system is decentralized thus it is difficult to administer.

 That is one person cannot determine the whole accessibility setting of whole network.
2) Security in this system is very less viruses, spywares,Trojans, etc malwares can easily transmitted over this P-2-P architecture.
3) Data recovery or backup is very difficult. Each computer should have its own back-up system
4) Lot of movies, music and other copyrighted files are transferred using this type of file transfer. P2P is the technology used in torrents.

Peer to peer networks are good to connect small number (around 10) of computer and places where high level of security is not required. In case of business network where sensitive data can be present this type of architecture is not advisable or preferred.

Advantages and Disadvantages to Peer-to-Peer and Client/Server Networks Peer-to-Peer


*      Advantages

·         Easy and simple to set up only requiring a hub or a switch to connect all computers together.
·         You can access any file on the computer as-long as it is set to a shared folder.
·         If one computer fails to work all the other computers connected to it still continue to work.
*      Disadvantages

·         Security is not good other than setting passwords for files that you don't want people to access.
·         If the connections are not connected to the computers properly then there can be problems accessing certain files.
It does not run efficient if you have many computers, it is best to used two to eight computers.


Client/Server

*      Advantages

·         A client server can be scaled up to many services that can also be used by multiple users.
·         Security is more advanced than a peer-to-peer network, you can have passwords to own individual profiles so that nobody can access anything when they want.
·         All the data is stored onto the servers which generally have far greater security controls than most clients.
·         server can control the access and resources better to guarantee that only those clients with the appropriate permissions may access and change data.

*      Disadvantages

·         More expensive than a peer-to-peer network you have to pay for the start up cost.
·         When the server goes down or crashes all the computers connected to it become unavailable to use.
·         When you expend the server it starts to slow down due to the Bit rate per second.
·         When everyone tries to do the same thing it takes a little while for the server to do certain tasks.


 
biz.