Data transfer in one point to another is the most important aspect of computers. Networks should be safe, reliable and secure for data motion. Any problem which occurs with computer networks triggers havoc. Understanding networks, just how they work, and how they are built helps a network administrator to recognize and fix the problems.
11. 2 Technique to troubleshoot network problems
A simple formula that allows network administrators solve any type of network problem is:
Identify the symptoms.
Identify the damaged area.
Determine what has changed
Select the most probable cause
Implement a solution
Test the result
Recognise the actual ramifications of the solution
Document the solution
11, 2, 1 Identify Symptoms
Indicators are either physical or logical symptoms that help determine the nature of the situation, the reach of the trouble, etc. These symptoms enable a network administrator to adopt timely preventive measures to solve the challenge before it grows up beyond control.
System or operator problems
System errors occur from some type of computer, network device or an activity that's not related to a user's immediate interaction with the machine or network. Such errors can occur credited to hardware inability, faults in the process of data transfer or manipulation.
Operator mistakes are a primary consequence of any user's action. The activities that can cause such errors may be wrong log in, wrong links to a server, misidentification of servers or network devices, imperfect network relationships, etc. Errors on area of the network administrator that are common factors behind operator errors are misconfiguration of devices, programs or services.
Link lights
When a networking device detects a network connection a inexperienced or amber Light-Emitting Diode (LED) is fired up. This is actually the link light that shines when in the 'ON talk about. Components of a network were created with link lamps to show the express of the network connection. Whenever a physical network connection is present a link light remains on and another light is present that displays the current activity of the network greeting card and blinks, pluses, during data transfer. . Link lights are designed to not light in case there is an inappropriate network cable connection. By examining the link light of an device, a consumer can determine whether a network connection is working or not.
Collision lights
Lights that signify whether a certain interconnection is facing problems due to packets colliding with each other is a collision light. The collision light (activity light) is green while mailing and receiving data which is yellow or orange whenever a collision mistake is detected. The packet being received or dispatched is lost when a collision occurs. Faulty wires or hubs can cause packets being produced from other packets or electric powered interfaces which when in large magnitude are called chatter. These network chatters can finish up halting a whole network because of data packet collision. Network administrators and users should screen these equipment and lighting to detect network chatter and prevent it.
Power lights
A electric power light indicates when there is power supply to the networking device or not. In the event there is absolutely no power supply the power light is off. The energy supply wires or wall structure connectors should be checked out for proper connections while troubleshooting a network problem.
Error displays
A device inability or malfunction is indicated by one display. A aesthetic error dialogue field using the pc or an LED error screen on the network device is the form of one display. These exhibits also describe the situation that is found. Typically, an error display pertains to an error code that needs to be referred by an individual to identify the reason and the right solution. Every physical or logical problem has a distinctive solution provided by its maker which is often within its paperwork.
Error logs and displays
A list of the errors experienced on the network device is the mistake log. Enough time of the problem occurrence, the nature of the problem and a suitable solution is what constitutes an error log. The information found in an error log is not sufficient to resolve an issue and requires the support of the related documentation to resolve the challenge.
Error logs are important sources of information which includes the time of the problem, probable cause and other operations afflicted by the mistake. An error screen gives a aesthetic alert of a problem and logs it in the error log. Not absolutely all error exhibits require immediate attention but a few are warnings that not indicate an existing problem but need attention.
An Event Viewers is an mistake logging mechanism which is typical to Windows-based OS such as Glass windows clients and machines. Event viewer is a critical tool in diagnosing and resolving a difficulty. Red-X error entries which have occurred are recorded in an event viewer. This is a credit card applicatoin that reads the binary log documents stored at \system32\config folder.
To view the problem logs, the network administrator requires to see the config folder because the function viewer gathers information from the data positioned in that folder.
Error logs are of three types that ought to be supervised by the network administrator regularly and they are the following:.
System log - Mistake text messages that are related to device drivers inability, service start failing and standard information about Operating-system events are recorded in the machine log.
Security log - When auditing has been empowered all security related events are documented in a security log.
Application log - Events that are made by application jogging on top of the OS are recorded in an software log.
Identify network problems
Troubleshooting a network is one of the key concept in networking. Discovering network problems and determining ways of troubleshooting these problems is quite crucial for smooth performing of any network.
The job of highlighting the condition is usually done by the network customer. This will not be the foundation on which an administrator should attack a problem. It is advisable to see the problem personally along with the consumer who reported it. This can help the network administrator confirm if the problem is real or just an error. There are certain users whose knowledge about computers and sites is not vast. With such users when a problem is reported, a first-hand inspection and verification are necessary.
The best method of solving a problem is by determining its scope. The key reason why a knowledge of the nature of the problem is essential is the fact that it establishes the type of attack.
Gathering information helps the network administrator to thin down to the main of the condition. This approach avoids a network administrator spending needless time on needless jobs. Following the network administrator can pinpoint the cause of the condition, then finding a remedy is possible.
A network administrator must first collect information to discover if the situation is with a single computer or with the complete network. In the event the challenge is local, then the complete network is not burdened and a solution are available easily. The first logical step that is to be taken is to check on all cable connections to and from the system. It isn't advisable to look into bigger issues or concentrate on larger resources when the reason might be very simple. The key reason why a system is not able to hook up to other systems may be that the network cable connection is not plugged in properly in to the system. If the cable is connected properly, the network connection is up and running.
For example, if two systems in a network cannot communicate with each other then the network administrator is capable of doing simple investigations like verifying the associations between the systems or connections to the network
A network administrator should check if issues is consistent and replicable. If the condition reported unique to something or could it be replicated in other systems in the network. If the same problem is reported from another system also, then the challenge is consistent and replicable. The amount of destruction is high in such an instance since many systems are infected. If the condition is identified to be with the network, then the network administrator must reach to the cause of the condition step-by-step.
A large computer network takes a lot of work from the network administrators and users for this to run smoothly. Increasing the huge activity of maintenance is the work of fixing issues. It becomes difficult to identify the actual problem for you'll find so many workgroups and workstations. It really is advisable to address large network problems with the trial and error method.
The administrator should first check the neighborhood system from where a problem has been reported. A thorough check of its internet connections, network links, electric power supplies and so forth should be done. If the problem is not with an area system then other systems in the vicinity should be examined. The routers to and from the machine should be verified for proper working. The various cable connections should be confirmed.
One of the best solutions to check and fix network problems is to try joining to other systems and elements of the network by pinging to them.
11. 2. 2 Identify the affected area.
After the reason for the situation is determined it is simple logic to isolate the afflicted area. This step helps an administrator filter down to the core of the situation. With many issues to be taken care of at the same time; administrators must prioritise the issues. Issues which have an effect on work to a huge amount should be set first and the others should follow sequentially. By doing this the downtime can be reduced and the system can be fixed faster.
Same lines, different computer
While trying to resolve a problem it is important to isolate the influenced system. A simple method of examining if the condition is replicable is by replacing the initial workstation with another system which may have no problems. By confirming if the condition is with the local system or beyond it, the network administrator eliminates one factor of the problem. An easy way of isolating the machine is by changing it with another system. This task determines if the problem is computer specific or not.
Same computer, different line
When a user reports of the problem, another way the administrator can reach the cause of the situation is by changing the network cords for the machine. Using this method, the possibility of a network mistake can be recognized or nullified. In case the machine works properly with a fresh interconnection, then it is for certain that the challenge is with the original network and not the computer.
Swapping components
In a network, hubs, cords, terminators can be swapped with other systems to check on for replication or consistency of the problem. This can help in case there's a faulty part and the work of the initial system user is not disturbed since an extra is in place. This step helps determine the range of the situation and treat it appropriately.
Prioritising work is very important for network administrators and network administrators since the time and effort used to repair an issue should help users to make contact with work faster. Bigger and crucial problems require immediate action while the smaller ones can be attended to after the bigger ones are fixed.
Isolating segments of the network
By isolating parts of the network get spread around of the problem is checked in a way that the entire network will not collapse. The systems that have reported issues must be disconnected from the network and terminators connected in. That is a safe practice as it can help the network administrators fix the problem with minimal overloads of data and work.
Steps for problem isolation are given in Desk 11. 1
Step
Action
Determine which systems are and that are not exhibiting symptoms.
Separate the systems that are showing symptoms from those that aren't with hubs or terminators.
Rule out simple issues.
Reset all major associations to and from the system.
Eliminate cable tv problems.
Check for physical harm or erroneous associations of cables.
Eliminate serious cable tv issues.
Use TDR to determine cable television problems.
Table 11. 1 Methods to isolate network problems.
11. 2. 3 Determine what has changed
Computer sites have many components, both hardware and software that may be changed or reset to meet the requirements of the business. This can be one of the sources of a network problem.
For example, if the user reports of a problem after something in a network is substituted then your administrator should check if the address of the adjusted system is properly recorded and connected with the prevailing network.
To have the ability to fix problems when changes are created to the network, it is highly recommended to keep proper records of most details about the new and existing network like the points of change, the the different parts of change, their variants, IP addresses and network cords. A detailed records system helps fix such issues quickly.
Checking the position of servers
Servers are an intrinsic and crucial tool in a network. Their health is very important for functioning of a network. Therefore it is logical to check on the server status when faced with a problem. If sever issues aren't addresses promptly, then the amount of harm can be high.
A few server monitoring jobs that can keep an eye on their status are the following:
Check services
Check error logs
Check connectivity
Monitor performance and network traffic
Confirm notifications and alarms
Verify back-up logs along with test restores.
Checking problem logs
Error logs are an important source of information for a network administrator. It throws light on the errors that have happened and their nature. The amount of damage can even be assessed out of this log. The administrator can prioritise mistakes on the scope of destruction and fix them for the reason that order. It's important to examine the error sign on a daily basis because certain errors have dependencies which can propagate the destruction faster. It is advisable to make it a habit to check the problem logs at some point of time in the day to help the network are better. Connectivity between systems or servers can be examined using the Ping feature. If the machine at the other end of the ping communication responds then your connection is intact, else an intensive check of the connection should be done. Regular assessments should be carried out to consider server overload problems. An overloaded server can decelerate system performance and speed. Backup servers also needs to be watched for posts and performance. In case of an emergency back up data and resources are very essential. An alert system can be designed which can boost alarms when predefined boundaries are exceeded. This is a good precautionary measure that helps in proper performing of your network.
Checking for configuration problems
Before introducing a fresh resource into the network it is necessary to verify the existing configurations and contacts. In case the existing settings are incorrect, then the new reference cannot work.
For example, before establishing a new server it is good to check on the base Operating-system, TCP/IP, network wires, mistake logs and storage area allocation for precision. This enhances performance and does not allow deterioration of the system.
After the existing settings and cable connections are verified the new resource and additional services must be configured accurately. There are a few duties which require the complete network to be turned off for a few minutes before rebooting. This activity must be timed for low work fill hours.
A few critical services which determine functioning of the whole network and requries frequent monitor and accurate configuration are:
DNS
a Microsoft energetic index and other Internet-based applications helps this service. A detailed plan should be in place before configuring a DNS which need a list of information before set up.
Domain name
WINS
WINS is a feature just like DNS which resolves NetBIOS titles to IP addresses. That is a active service which can add, modify and erase name registrations and avoid human errors and save time. WINS has many construction possibilities and the user can add a static mapping for clients or severs.
Host file
Host data and DNS are similar in function. Host files require manual configuration of repository with exact mappings of hostname to IP addresses. Host data files reside on every computer making the procedure of updating difficult. It is vital to provide right hostname to IP address mappings so that all rules that apply to the DNS, also connect with the host documents. In order to avoid typing mistakes while configuring variety data, it is safe to replicate the prevailing hosts to the newly created file and on each one of the machines.
Checking for viruses
Viruses are a huge and common danger to computers. Your personal computer network is at better risk as the amount of computer systems is large and the destruction can be huge. Defending networks and computer systems outside of systems from infections is a high priority job. Trojans grow in the computer world at a rate which fits the growth in the biological world. The mechanisms to kill viruses evolve every minute to battle the most powerful and newest pathogen. It's the job of the network administrator to keep carefully the network free of viruses. Constant revisions of virus classification files, scans to check on for entrance of viruses and antivirus software are the most popular and best solutions to fight them. Precautionary options are best when deployed round the clock. All resources in a network should be scanned for viruses and guarded from them. Every piece of software and hardware is vital to the even working of an network or system. There are a number of trojan scanning utilities available in the market which enables pcs to automatically update virus definition documents from a primary server therefore preventing the administrator making excursions to each workstation.
Checking the validity of bill name and password
Account name and password are the gates that lead an individual to a complete world of services, applications and data. Their validity concerns a great deal for an individual to have the ability to gain access to services, applications or data. Many services use the built-in system bank account details for success while additional services require the user to get on a distant system. This task requires a merchant account name and security password that resides in the network account database. To activate certain services or applications, administrative privileges or account in certain organizations is essential which again requires profile name and security password. For quite a few system-related responsibilities, administrative rights are needed which allows an individual to change certain settings to match the need. The worst situation is whenever a network administrator has configured many applications and services with the administrator consideration which gets deleted on end of service of the administrator. If all services and applications using the administrator bill are impaired and access is denied, then it's very difficult to fix this.
Rechecking operator logon procedures
Very often users conclude facing problems with passwords. Users try to logon to an integral part of the network that access is not awarded, ignore passwords, do not bear in mind the case-sensitive feature of passwords, etc. Many a times a end user will try more than thrice to logon with a certain or different passwords and the user is locked out. To resolve this trivial but deep-penetrating concern the administrator must reset the security password for the user. Passwords should be changed at regular intervals for basic safety also to avoid expiry and this is an issue for many users.
Selecting and operating appropriate diagnostics
Diagnostics can be an essential tool to even out variants and eradicate potential problems in a network. Though this is a preventive mechanism the advantages of using it are extensive. Diagnostics consider bottlenecks and problematic situations. Diagnostic tools bring out problems or drawbacks and limitations that may be set before they erupt as big problems. While choosing a diagnostic program the user should remember the network requirements for which it is usually to be employed. Smaller sites should use simple diagnostic programs while large systems require extensive protocol analysing and packet sniffing products. Free diagnostic products such as performance screen and network screen work very well for a medium sized network. To utilise the tool to the maximum without impacting the network performance, the network administrator must research the diagnostic product in depth. With experience and products like these, an administrator is able to identify the problem with time and fix it effectively. A reliable baseline of activities must be established for trials. Snapshots of different activities at different time periods of your day, week and month helps evaluate the network efficiently and effectively.
11. 2. 4 Choose the most possible cause
Of the many steps suggested to resolve a problem, experience of the network administrator is a capacity that matters a lot for the procedure. In the event the network administrator is not well versed with the network or common network issues, resolving becomes a tough task. The way a network administrator approaches a problem solves the issue to quite an degree for this can guide or misguide what sort of solution is made. In case a fresh or another network administrator has been roped in to solve a network problem the chances of long system downtime is high. The brand new network administrator must get familiarised with the network, and then look out for probable causes. The greater the experienced the network administrator is, the simpler it is to resolve the issue.
Many a times problems may be similar across systems and a network administrator can tap the knowledge from days gone by to repair it faster. An organization can benefit basically from a full-time network administrator and who is aware the facts of the network at the back of the mind.
Common problems and their possible causes
The common network problems are their probable causes receive in Table 11. 2
Problem
Probable cause
Cannot connect to a computer on a remote network.
A routing issue in all probability. Check if it's possible to hook up to an area system and ping the router or another system on the remote network.
Communication in the whole network is down.
If in a coax-based network, look for loose connections. If in a twisted-pair network, check if the hub is functional. If in a token band network, check if the computer is not beaconing.
Takes a very long time to connect to a network reference.
Network may be overloaded.
A device on the machine is not operating and network connection is extremely hard.
A network greeting card configuration issue in most cases. Check if the NIC is configured properly. Drivers may be loaded incorrectly.
Communication in a local network is extremely hard, but other networks are working.
Check if the hub/transition is not locked up. Check if the network adapter is configured properly.
No Internet access.
Check the web gateway. Check the router present has a fervent Internet connection. Check the web provider's network.
Token engagement ring network is locked up.
Someone in the network is beaconing. Also check if the bridge is locking up.
Table 11. 2 Certain problems and probable causes
11. 2. 5 Put into action a solution
In order to repair a difficulty a network administrator can consult others, read related documents, research from the web and seek help from owner help lines. Finally with a remedy readily available that seems most suitable it ought to be implemented without the delay.
11. 2. 6 Test the result
Confirming if the solution implemented is correct and has solved the challenge is very imperative to the problem handling process. Any consumer contacts the network administrator with a wish of fixing the problem and getting back again to work. In case the network administrator leaves the user without confirming if the answer provided is right, then the reason for the network administrator being present is defeated. It's the duty of the network administrator to ensure that the condition with which the user had contacted does not replicate.
11. 2. 7 Recognise the potential ramifications of the solution
With an operating solution set up another factor that a network administrator should consider is the aftermath of the solution. Many instances are available in which a certain means to fix problems has brought about problems in other areas of the system or network. This cascading aftereffect of a solution should be monitored and checked. For example, a end user may report something communication problem and a solution can be provided by resetting of the network cords. The local problem of the machine not having the ability to speak might be solved, but the system might still not have the ability to connect to some other elements of the network. Such rippling effects of a remedy require attention from the network administrator. Proper execution of a solution, confirming its working and nullifying all side effects of a remedy completes the perfect solution is phase.
11. 2. 8 Documenting the solution
After an issue reported has been solved and work is back to normal, it is the job of the network administrator who solved it to record it properly for future use. The fact that one problems might recur after some time frame, a new network administrator might face a difficulty already solved early, etc are the reasons why documentation is necessary. An organisation benefits from proper documentation of troubleshooting when there is a change of hands with network administrators, saving on time by not going right through the whole process after an apt solution is available by one. It even benefits when a certain solution has faded in the memory space of a network administrator. Proper documentation for each aspect of troubleshooting is really as good as providing an appropriate solution on time.
11. 3 Common connectivity issues in a network
The common connection issues in a network can be of two types - network inability anticipated to physical problems such as device or wire issues and reasonable problems such as invalid IP addresses or VLAN problems.
11. 3. 1 Physical issues
Cabling problems are the most common physical issues. Visible indications such as link lights, activity signals and collision lamps can be used to fix these problems. A few common issues that a network administrator fixes are:
Recognising abnormal physical conditions
To have the ability to recognise deviations from the standard, a good understanding of what is the standard is essential. If an individual is not aware of the default information, then it isn't possible to improve or reset details. A end user should be aware of certain issues in order to spot problems. These issues are as follow:
Authentication takes more time.
More problems are logged than typical.
Printing is taking more time.
Connecting to a network is getting slower.
Connections to resources are being lost.
Isolating and correcting problems in the physical media
Network cables are the most vulnerable resources in a network. They conclude leading to a whole selection of problems and can get fixed easily. The cable which reaches a high risk of problems is the cable television from the workstation to the wall membrane jack.
A solution as easy as plugging it back again can solve network problems at times.
If the problem is not resolved, try another cable and try with other wires till contact is set up.
Cable problem
Probable solution
Communication in the whole network is down.
Check if the cable tv is intact. The point where the wire has been ruined should be reconnected with a new cable.
The new UTP cable television is not allowing network communication. The network is working with the test cable television.
The new UTP cable connection might be considered a crossover cable. Test the connections with a cable tester and replace the UTP wire if not fine.
A system was migrated to a fresh location and is not able to communicate now. The machine is working properly.
Cables might be broken during transit. Replace the old wires with new ones for proper connection.
Table 11. 3: Common cable television problems and possible solutions.
Crosstalk
When adjacent wire connections hinder a certain wire system it is called crosstalk. The first indicator of crosstalk is signal degradation. Using another cable television type with multiple tiers of shielding is the best solution because of this problem.
Nearing cross talk
Issues in network connection occur when a cable wire triggers electromagnetic interference in the wiring adjacent to it and releases a current. This aspect has the most powerful possibility of combination talk and is normally present in the first part of the cable which is linked to a connection, move or NIC. Nearing crosstalk helps to measure this type of cross converse.
Attenuation
Signals degrade as the distance they travel rises, this is named attenuation. When a user discovers it difficult to talk to system at a considerable ways, then your maximum cable period for that type of cable would have exceeded. In such a case, a repeater can be utilized sooner or later in the cable to reamplify signals or a new cable tv type can be used.
Collisions
Data collision is a common issue whenever there are many systems in a network. Data packets traveling over the network collide with each other affecting network performance. To resolve this problem network hubs can be changed with switches which has each interface on the turn owning its network segment making certain data does not collide.
Shorts
A network brief leads to network downtime. Utilizing a cable analyser to recognize shorts can reduce the challenge of connectivity and shorts.
Open impedance mismatch (echo)
Network signals bounce creating communication problems scheduled to high impedance. Impulses jump because of miswired cables or wrong connectors. Recrimping of the cable is a good treatment for avoid high impedance problems.
Interference
Network cables experience signal disturbance from external components like ability cables, backup lines, etc. Network cords should be laid from realtors that can interfere with its signals.
11. 3. 2 Reasonable issues
Logical issues have simple solutions but can result in huge problems if not attended to properly. Several logical issues and alternatives are listed in this section.
Port velocity and duplex settings
Confirming that the swiftness and duplex options of the network card are set properly avoids problems for systems connecting to the other person across a network.
Incorrect VLAN
Communication between systems across VLANs is not possible unless there exists routing done between them. Therefore inserting systems related to the VLAN is important.
Incorrect IP address
If IP addresses of systems are not set properly for communication, problems will definitely appear. The first rung on the ladder in troubleshooting should be to check for accurate IP addresses.
Wrong gateway
If the Ip of the router is not place correctly then the default gateway adjustments are incorrect which causes communication problems from the network. IP addresses should be appropriate.
Wrong DNS
If the Ip is correct yet the user struggles to communicate with other systems, then the condition is with the name image resolution feature. Concur that the IP address configured on the system is set as the DNS server admittance.
Wrong subnet mask
Correct subnet face mask information along with correct IP address ensures proper communication between your systems. Hence, check for correct subnet mask information in the TCP/IP properties.
Network loops
Loops include interconnection problems in a network. STP standard protocol (from Cisco) prevents loops by positioning one of the slots informed in a obstructed state. A thorough check of the network wiring and removal of cables that create loops is the perfect solution is because of this problem.
Routing issues
Routers are an essential components of the network. If there is a routing problem, then the whole network collapses with no communication between systems. Checking of the routing stand on the router solves routing problems.
Wireless issues
Incorrect cordless network connection for cordless clients is the most common wireless problem. Cordless devices and microwave devices are potential resources of cordless problems. Therefore, such devices should be put away from the network.
11. 4 Triggers for escalation
Certain network issues like moving over loop, routing loop, option problems, proxy ARP and Broadcast storms if identified must be escalated as these require experience and skill to resolve.
11. 4. 1 Switching loop
To ensure fault tolerance and weight balancing, switches in a network are frequently linked to links that aren't used to provide insert balancing and problem tolerance in the network. To prevent switching of loops and keep maintaining mistake tolerance the Spanning Tree Standard protocol (STP) can be used. In case there is an STP failure leading to an STP convergence problem then the network ceases, restarts and ceases again with no alert. Reconfiguration and repair of the network post STP failure requires competence and time, and hence in such a scenario escalation is needed.
11. 4. 2 Routing Loop
Routing loops appear in the event the routing protocols are not configured appropriately or whenever a network administrator creates conflicting routes through the network leading to issues in traffic circulation for the network users. As this example is very complicated and can't be fixed easily escalation to experts resolves the problem. Another reason for the routing loops to occur is if the network is using old protocols like RIP and RIPv2 updating these protocols to the latest ones can prevent routing loops.
11. 4. 3 Way problems
Routing problems appear in case an incorrect default route is defined over a router or the router configurations are improved randomly. Router configurations include things like NAT, PAT, Gain access to lists, and Authentication protocols. A big change in the configuration of the router can lead the network traffic to an inappropriate avenue or even bring the entire network to an end. As router configurations are incredibly correct and must be an exact match to the device being used for routing hence, these problems should be escalated to a systems administrator.
11. 4. 4 Proxy Address Image resolution Protocol (ARP)
The purpose of the Proxy ARP was to provide several configured default gateway to the number over a network, though it is no more used in today's networks. It had been also used as a service to resolve IP addresses to Apple pc addresses. Though Proxy ARP is a redundant process many hosts and routers still own it by default. Each and every time the Proxy ARP transmits a note it uses valuable network bandwidth, wastes time and impacts the performance of the network. The routers being used on the network will need to have the Proxy ARP handicapped to prevent network traffic and ensure security. Escalation to an expert is necessary in case the Proxy ARP requires to be disabled on the sponsor or the router.
11. 4. 5 Broadcast storms
In case there can be an STP failure between switches or the turn has been handicapped then all the switches continuously transmit, receive and rebroadcast packets leading to a broadcast storm. This causes network congestion. Troubleshooting the network is possible only by locating the bad website link on the network and requires the treatment of experts.
11. 5 Resources to troubleshoot networks
Not all network problems get set by replacing wire, checking for links, and so forth. A number of resources are made to help network administrators solve problems that happen to be stated in this section.
11. 5. 1 TechNet
TechNet is a searchable data source from Microsoft which includes all articles and paperwork from Microsoft on all its products. This is a monthly problem of information that can be subscribed. An internet version of TechNet is also available at www. microsoft. com/technet which is easier to reach and search. Problems and alternatives from numerous users world over are noted here which can be of enormous use to all or any Microsoft users.
11. 5. 2 Manufacturer Web sites
Any product comes by a supplier who can take responsibility of support when requested. The website of the maker is a good way to obtain information which has the latest information about both hardware and software. This is actually the first step a user must take before getting for the manufacturer for a lot of support is provided in the website itself. Technical support help lines are also part of the situation resolution process for which links can be got from the Web site.
11. 5. 3 Source of information sets and knowledgebase
Resource packages are a trustworthy source of alternatives for many problems experienced by users. This database has a large amount of information about the Operating-system along with specialized details not easily available elsewhere. This knowledge platform is much greater than a standard documentation which gives only necessary information.
11. 5. 4 Trade publications and white papers
The latest & most recent innovations and technologies that have entered the marketplace are available in trade publications and white documents. This may not be the immediate source of information to resolve a certain problem, but regular reading of such articles and data enhances the knowledge of the user and enables them to resolve problems easily.
11. 5. 5 Cell phone technical support
It is definitely easy to seek help from a person alternatively than documents and articles. Associated with people and explaining problems to the people is simpler. Phone technical support is provided by most suppliers and manufacturers. Skilled and experienced network administrators speak to users and help them straighten out network issues over calling. A little homework on part of the customer quickens the support process. The information that is useful for such interactions is:
Hardware and software environment information, for example OS of the system
Version number of hardware and software
Serial numbers
Troubleshooting done by the user
Details of the problem
Contact number for going back the call
11. 5. 6 Seller CDs
A whole selection of information is directed at the user in the form of a CD at the time of purchase of the hardware or software. This is made up of details about set up, configuration and answers to probable problems. Most users undermine the value of supplier CDs and vacation resort to own methods of solving issues. It is wise to check the Compact disk first before venturing to try other means of solving a problem. Vendor CDs are similar to TechNet generally and can solve a wide range of issues.
11. 6 Other symptoms and factors behind network problems
A detailed and patient look at the symptoms of a network problem can lead a end user to the cause faster. That is generally false since people stress at times of trouble. There are many problems which arrive differently but have the same solution. Table 11. 2 lists a few common problems and possible causes.
Chapter review questions
A consumer has tried to logon more than 3 x and has been unable to do so. To solve this matter the network administrator will______________.
Configure a new user ID
Give the user a new workstation
Check the gain access to list
Reset the user's password
To test if the network problem is replicable the network administrators must ___________ the original workstation with another system which is known to haven't any problems
Configure
Remove
Replace
Connect
By evaluating the ______________of a device, a individual can determine if a network connection is jogging or not.
Structure
Display
Buttons
Link lights
In case the network users cannot hook up to a computer on a remote network the network administrator should check for __________.
Damage in the computer
Password of the user
Configuration of the computer
Routing issues
Determine what has evolved is the _____________ step in the procedure to troubleshoot network problems
Second
Third
Fifth
Last
A visual mistake dialogue box on the computer or an LED error screen on the network device is the form of _____________.
Help window
Error display
Device display
Error log
A device on the machine is not working and network interconnection is extremely hard. The network administrator should check for_________________.
Configuration of the system
Configuration of the NIC
Configuration of Gain access to point
Configuration of the server
The collision light is _________________ whenever a collision mistake is diagnosed.
Red or yellow
Yellow or orange
Orange or red
Red or green
Implement a remedy is the _________________step in the task for troubleshooting a network problem.
Fourth
Sixth
Seventh
Fifth
An Event Viewer is an ______________which is typical to Windows-based OS.
System error
Error logging mechanism
Operator error
Error display
Summary
In this chapter, Network Troubleshooting, you have learnt about:
The treatment of troubleshooting network problems.
Common connectivity issues in a network.
Causes of escalation.
Resources to troubleshoot sites.
