TROUBLESHOOTING NETWORK PROBLEMS
Overview
The routine of troubleshooting your network involves a methodology which starts with cabling and functions by the OSI indication to the focus layer. The network inclination have a network wire which terminates at a connected switch. Cabling is a source of a lot of network problems.
The key with troubleshooting is to establish what has changed. Sometimes it is hardware which isn’t operative or a little shift was done such as brand brand new software, configured apparatus or one some-more employees stressing the network. It could be a specific emanate or multiform problems. Start with the customer adapter, establish the specific symptoms and go from there.
The following is a array of questions which can used as a guideline during the troubleshooting process:
1. Can you ping the switch IP address?
2. Can you ping the router?
3. Can you ping the DHCP server?
4. Does the customer acquire an IP address?
5. Is the WAN circuit available?
6. Has brand brand new program been commissioned on the customer or server?
7. Do all clients knowledge the problem?
8. Is it pointless or a specific pattern?
9. Is the complaint server specific or focus specific?
10. Is the DNS server IP residence environment correct?
11. Is there a firewall which is filtering traffic?
12. Ran traceroute and carefully thought about routing behaviour?
TOOLS:
1) Windows carry out row shows network adapter settings, firewall pattern etc.
2) Ping and traceroute will establish which network routing is working.
3) Examine the ARP list on the desktop, switch and router confirming the device MAC residence is there.
4) Network parcel sniffers inspect parcel report such as protocols, filtered programs or errors with applications.
5) Verify shift government activities and establish what if any device was altered and how.
6) Show interfaces at the router will exhibit any interface errors indicating to a wire or hardware problem.
7) Examine router interface function patterns.
Working from the wire turn and last if the complaint is inspiring a singular user, a department, office office building or city far-reaching is a great place to start. A city far-reaching complaint infrequently indicates a interpretation core outage. A office office building infrequently points to a circuit, router or first switch. A dialect can prove a complaint with their network switch or essential element cabling. The singular user complaint could be a innumerable of issues from a bad wire to network permissions. Because companies have in a little cases hundreds of applications, network switches and routers the complaint becomes some-more formidable when it is a cranky dialect issue. Not all employees have the same network permissions and make use of a accumulation of applications opposite departments, cities and countries.
Determining who is influenced by the complaint can be a key cause in solution the issue. The ping is a renouned apparatus given it verifies to the network covering all is working. In which box your afterwards focusing on focus issues nonetheless not always. Traceroute verifies how packets have been roving in between source and destination. You could have packets regulating non optimal routing paths which have been causing opening problems.
Network Planning and Design Guide is accessible at amazon.com and eBookmall.com
Shaun Hummel is an writer of assorted technical books and has a web site focused on report record pursuit poke solutions and certifications.
http://www.networkjobsolutions.com
Shaun Hummel, CCNP, is a Senior Network Engineer with eleven years knowledge in craving network planning, design, and implementation. He has worked for assorted in isolation and open companies in Canada and the United States mending infrastructure, security, and management. He has created Network Planning and Design Guide, Cisco Wireless Network Design Guide and Network Assessment Guide. www.networkjobsolutions.com
