Troubleshooting Speaker Saengsan Tinarak Channel

Slides:



Advertisements
Similar presentations
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Introduction to IPv4 Introduction to Networks.
Advertisements

Configuring and Troubleshooting Network Connections
METEOROLOGICAL TELECOMMUNICATION AND METCAP A GLANCE TO NETWORK BRIEFLY Ömer Hüdai ALBAYRAK 2010ALANYA.
SYSTEM ADMINISTRATION Chapter 19
11 TROUBLESHOOTING Chapter 12. Chapter 12: TROUBLESHOOTING2 OVERVIEW  Determine whether a network communications problem is related to TCP/IP.  Understand.
Troubleshooting TCP/IP COSC513 FALL By :Ming Wei.
Operating Systems Concepts 1/e Ruth Watson Chapter 11 Chapter 11 Network Maintenance Ruth Watson.
Nassau Community College
Chapter 13: Troubleshooting network connectivity Unit objectives Identify TCP/IP troubleshooting tools Discuss the Telnet utility and its functions Discuss.
Module 4: Configuring Network Connectivity
MCDST : Supporting Users and Troubleshooting a Microsoft Windows XP Operating System Chapter 13: Troubleshoot TCP/IP.
CPSC 441 Tutorial - Network Tools 1 Network Tools CPSC 441 – Computer Communications Tutorial.
Chapter 8 Administering TCP/IP.
TCP/IP Tools Lesson 5. Objectives Skills/ConceptsObjective Domain Description Objective Domain Number Using basic TCP/IP commands Understanding TCP/IP3.6.
Click to edit Master subtitle style Chapter 17: Troubleshooting Tools Instructor:
CT1304 LAN L AB Rehab AlFallaj. TCP\IP U TILITIES Objectives: To understand the following TCP\IP utilities: Hostname Ipconfig Ping Arp Tracert Netstat.
Monitoring and Troubleshooting Chapter 17. Review What role is required to share folders on Windows Server 2008 R2? What is the default permission listed.
Chapter Twelve Using TCP/IP on the Network. Objectives Here, we’ll examine how to configure TCP/IP. The concepts of subnetting will be examined in detail.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public ITE PC v4.0 Chapter 1 1 Troubleshooting Your Network Networking for Home and Small Businesses.
Module 7: Configuring TCP/IP Addressing and Name Resolution.
Hands-on Networking Fundamentals
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public ITE PC v4.0 Chapter 1 1 Troubleshooting Your Network Networking for Home and Small Businesses.
Managing Network connections. Network Cabling Ethernet Topology Bus topology – Connects each node in a line – Has no central connection point Star topology.
Connecting Networks © 2004 Cisco Systems, Inc. All rights reserved. Exploring How IP Address Protocols Work INTRO v2.0—4-1.
Robert E. Meyers CCNA, CCAI Youngstown State University Manager, Cisco Regional Academy Cisco Networking Academy Program Semester 4, v Chapter 7:
Network Tools TCP/IP interface configuration query - MAC (HW) address and IP address – Linux - /sbin/ifconfig – MS Windows – ipconfig/all 1.
Module 5: Isolating Common Connectivity Issues. Overview Determining the Causes of Connectivity Issues Network Utilities That You Can Use to Isolate Connectivity.
 Ping - Transmits four 32 byte packets to target computer ◦ Measures response time ◦ Returns IP address of target computer ◦ Example: ping uottawa.ca.
KIS – Cvičenie #5 IP konfigurácia v prostredí OS Windows Marián Beszédeš, B506
70-291: MCSE Guide to Managing a Microsoft Windows Server 2003 Network Chapter 6: Name Resolution.
70-291: MCSE Guide to Managing a Microsoft Windows Server 2003 Network, Enhanced Chapter 6: Name Resolution.
Connecting to a Network Lesson 5. Objectives Understand the OSI Reference Model and its relationship to Windows 7 networking Install and configure networking.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public ITE PC v4.0 Chapter 1 1 Troubleshooting Your Network Networking for Home and Small Businesses.
© 2007 Cisco Systems, Inc. All rights reserved.Cisco Public 1 Version 4.0 Troubleshooting Your Network Networking for Home and Small Businesses – Chapter.
Monitoring Troubleshooting TCP/IP Chapter 3. Objectives for this Chapter Troubleshoot TCP/IP addressing Diagnose and resolve issues related to incorrect.
Network Management CCNA 4 Chapter 7. Monitoring the Network Connection monitoring takes place every day when users log on Ping only shows that the connection.
ERICSON BRANDON M. BASCUG Alternate - REGIONAL NETWORK ADMINISTRATOR HOW TO TROUBLESHOOT TCP/IP CONNECTIVITY.
© ExplorNet’s Centers for Quality Teaching and Learning 1 Resolve common problems with wired and wireless networks. Objective – 2%
11 MAINTAINING A NETWORK INFRASTRUCTURE Chapter 9.
Chapter 5e.  Upon completion of this chapter, you should be able to:  Find IP configuration settings on Windows & Linux  Troubleshoot IP configuration.
Discovery Internetworking Module 9 JEOPARDY K. Martin.
Lecture#6:Connectivity Verification
LESSON Networking Fundamentals Understand TCP/IP.
Click to edit Master subtitle style
Troubleshooting a Network
Troubleshooting ip Chapter 5e.
CompTIA Network+ N Authorized Cert Guide
TCP/IP Utilities Richard Goldman May 29, 2003.
Connectivity Verification
Lab #1 ,Ipconfig & ping commands
Network Tools and Utilities
Instructor Materials Chapter 9: Testing and Troubleshooting
Planning and Troubleshooting Routing and Switching
Troubleshooting Network Communications
Planning and Configuring IPv4
Resolving Issues with Network Connectivity
Part1: Ipconfig ping command Tracert command Getmac command
Introduction to Networking
Troubleshooting IP Communications
Lecture#7:Connectivity Verification
NETWORK TROUBLESHOOTING COMMANDS
Troubleshooting IP Addressing
Chapter 9 Objectives Understand TCP/IP Protocol.
ITL Simple Diagnostic Tools
Lecture#6:Connectivity Verification
Networking Lab.
Troubleshooting ip Chapter 5e.
Module 12 Network Configuration
Windows Name Resolution
Networking Lab.
Presentation transcript:

Troubleshooting Speaker Saengsan Tinarak Channel Demo Inssider netstumbler

THE EIGHT STEPS The most important part of troubleshooting any problem is to divide the tasks of problem resolution into a systematic process of elimination. Cisco has broken this process into eight steps: 1. Define the problem. 2. Gather detailed information. 3. Consider probable cause for the failure. 4. Devise a plan to solve the problem. 5. Implement the plan. 6. Observe the results of the implementation. 7. Repeat the process if the plan does not resolve the problem. 8. Document the changes made to solve the problem. Channel Demo Inssider netstumbler

DEFINE THE PROBLEM AND GATHER FACTS How many times have you heard this: “My computer does not work”? Which leads us to the network administrator’s response: “Could you please be more vague?” Channel Demo Inssider netstumbler

Consider the possibilities After a problem has been identified, the next step is to consider all of the possible causes. Connectivity issues can be very difficult to trace to a single point of failure. In most situations, there are several possible causes for a network error, and the administrator should identify each probable cause.

CREATE AND IMPLEMENT AN ACTION PLAN Once the network problem and possible causes have been identified, it’s time to produce a solution. When developing a solution, it’s critical to thoroughly analyze the proposed solution and brainstorm with your peers the potential impacts your solution may have.

CREATE AND IMPLEMENT AN ACTION PLAN Here are a few of the most important guidelines to follow when implementing a solution: Make one change at a time. Make transparent changes first. This means if there are multiple possible causes for a problem, solve those problems that have the least impact on your users first. Do not create security holes when implementing your changes. Finally, and most importantly, always be sure you can back out of any changes you make.

OBSERVE THE RESULTS Observe results and, if necessary, try another solution Some changes may take time to trigger. Observe the results of your solution. Go back to the fact-gathering phase and determine if your solution solved the problem. If the trouble still exists, reference your list of possible causes and attempt to resolve the next most likely cause of the problem.

TROUBLESHOOTING TOOLS Ipconfig Ping Tracert Pathping Nslookup Netstat ARP Channel Demo Inssider netstumbler

IPCONFIG Displays all current Transmission Control Protocol/Internet Protocol (TCP/IP) network configuration values, and refreshes Dynamic Host Configuration Protocol (DHCP) and DNS settings. ipconfig /? ipconfig /flushdns

PING Ping Command Syntax ping [-t] [-a] [-n count] [-l size] [-f] [-i TTL] [-vTOS] [-r count] [-s count] [-w timeout] [-R] [-S srcaddr] [-4] [-6] target [/?]

TRACERT The tracert command is a Command Prompt command that's used to show several details about the path that a packet takes from the computer or device you're on to whatever destination you specify. Tracert Command Syntax tracert [-d] [-h MaxHops] [-w TimeOut] [-4] [-6] target [/?]

PATHPING Combines the functions of Traceroute and Ping to identify problems at a router or network link. The pathping command functions much like the tracert command but will also report information about network latency and loss at each hop.

NSLOOKUP nslookup is a network utility program used to obtain information about Internet servers. As its name suggests, the utility finds name server information for domains by querying C:\>nslookup Default Server: caching-dns1.rmutp.ac.th Address: 202.29.104.2

NETSTAT The netstat command is a Command Prompt command used to display very detailed information about how your computer is communicating with other computers or network devices. Specifically, the netstat command can show details about individual network connections, overall and protocol-specific networking statistics, and much more, all of which could help troubleshoot certain kinds of networking issues. Netstat Command Syntax netstat [-a] [-b] [-e] [-f] [-n] [-o] [-p protocol] [-r] [-s] [-t] [-x] [-y] [time_interval] [/?]

ARP converts an Internet Protocol (IP) address to its corresponding physical network address.