Where to Buy News and Events Training and Workshops Knowledge Base About Us Contact Us Canada: Change location/language



Home Products and Accessories Technical Documentation Support and Downloads Community

Basic Ethernet Troubleshooting

PRODUCTS
AnalyzeAir Wi-Fi Spectrum Analzyer
NetTool Inline Network Tester
LinkRunner Network Multimeter
EtherScope Series II Network Assistant
OptiView Series III Integrated Network Analyzer

TECHNICAL DOCUMENTATION
Guides
Frontline LAN Troubleshooting Guide, 115 pg how to

White Papers
Improve VLAN Performance Through Best Practices
Fixing Ethernet and Fast Ethernet Link Problems White Paper
Troubleshooting Switched Environments White Paper

Application Notes
Eliminating Sources and Causes of Unwanted Network Traffic
Frontline Network Troubleshooting - Practical Procedures and Methods

VIDEOS
View short video clips on solving network issues

SUCCESS STORIES
Manheim Auctions
Home Federal Bank
Vigo County Schools
Eaton Corporation
New York Times
Buncombe County Schools
Catalina Restaurant Group
Seattle Mariners

EVENTS
Webcast Series: Solving Network Issues
Webcast: Securing Network from Internal Threats

POSTER
Auto Negotiation Technical Reference Poster
Users can't connect. Devices stop talking to each other. Physical layer changes are causing problems. New networking technologies have caused even more. When everyday problems like these come up, the network technician has the simplest job description around: make it work. In today's business climate, making it work quickly and economically is the top priority. In any network environment, giving technicians proper training, the right tools, and a solid methodology for using them makes network troubleshooting faster, saving technician time and getting network users back to productivity faster. Basic Ethernet troubleshooting techniques and tools help minimize network downtime and user complaints. 

The basic troubleshooting sequence consists of five steps:

1. Document your network: A diagram of the parts of the network, as well as the signal flow paths between the various devices, is enormously helpful in visualizing the problem and saving valuable time. Theory and practical experience will determine which test to perform first. Consider experience with the same or similar equipment and related symptoms, as well as the probability of what is likely to fail or what suffers from repeated failures. A good practice however, is to start with the physical layer first, and work your way up the protocol stack.

2. Collect all available information, and analyze the symptoms of the failure.


3. Localize and isolate the problem:
It's best to subdivide or isolate a problem into a smaller functional section - removing the largest convenient section first (divide and conquer approach). Start at any convenient spot near the center point of the problem and divide the problem in half. Continue halving the problem until you've isolated it to the smallest possible section.

4. Correct the problem and verify problem resolution: Don't assume that the user is providing complete and accurate information. It's best to verify it yourself, or have the user show you how the problem was discovered.

5. Document what you did

Keeping the network running optimally requires IT professionals equipped with the right combination of tools and knowledge. Fluke Networks' LAN Testers provide frontline technicians with the ability to quickly resolve link, cable and connectivity issues - reducing problem escalation. For more difficult Ethernet problems, our portable analyzers give technicians and engineers deep vision into LAN, WLAN, VLAN and WAN networks. The links above contain useful information about the products, technology and success stories for Basic Ethernet Troubleshooting to help you become a more powerful problem solver.

   What's Next?
  Print this Page
  More Topics...