Before we get started, let's check out the most commons problems in the troubleshooting of a desktop user's network connection.
What is a Complete Connectivity Test? 1.
Link/Speed/Duplex Ethernet to the desktop now runs at three different speeds (10M, 100M, and 1 Gig) and three different duplex settings (half/full/auto).
Depending on how the switch and PC are configured, one of three things can happen.
First, everything works perfectly - the most common scenario.
Second, it doesn't work at all - may take a while to solve, but will eventually be fixed.
Third, the Ethernet works to a degree.
2.
Mislabeled cable The most common cabling error isn't a broken one, it's a mislabeled one.
If the use is connected to the wrong switch, port, or VLAN, he/she may experience a total breakdown in communication or just suffer with slow response time.
3.
Cabling Problems Cabling is one of the most common causes of network problems.
It's one of the few parts of the network that end users can get their hands on, so it's not surprising things go wrong.
4.
Power over Ethernet The number of devices powered by Ethernet is exploding as companies deploy technology to support VoIP phones, security cameras, and wireless access points.
If a deivce doesn't power up, is the problem the cable, the device or the switch sourcing the power? And what if the power source is marginal because the cable is bad or too long or the switch is simply overloaded? Testing the PoE can answer these questions.
5.
Network services Being unable to access network services such as DNS or DHCP from the user's desktop can result in symptoms ranging from slow performance to a total lack of communications.
A quick test of these services can rule out these problems.
6.
Connectivity to key resources Once all the basics in 1-5 are addressed, the final issue is whether the network will carry the user's traffic to the places it needs to go.
For example, can the user reach the corporate intranet, email servers, cloud? Or is something blocking access? >> What Can LinkRunner Help You Do? Fluke's LinkRunner AT provides the answers you need to quickly troubleshoot connectivity problems.
It can answer all the following questions.
1.
Where does this cable or jack go? 2.
How is this switch port provisioned? 3.
Can I negotiate a Gigabit link? 4.
Are there 802.
1x security conflicts? 5.
Are the DHCP and DNS servers working? 6.
Can I get enough power from this port? 7.
Can I connect to servers and the Internet with IPv4 and IPv6? 8.
Can I connect over copper or fiber links? 9.
Is this patch cable good?
What is a Complete Connectivity Test? 1.
Link/Speed/Duplex Ethernet to the desktop now runs at three different speeds (10M, 100M, and 1 Gig) and three different duplex settings (half/full/auto).
Depending on how the switch and PC are configured, one of three things can happen.
First, everything works perfectly - the most common scenario.
Second, it doesn't work at all - may take a while to solve, but will eventually be fixed.
Third, the Ethernet works to a degree.
2.
Mislabeled cable The most common cabling error isn't a broken one, it's a mislabeled one.
If the use is connected to the wrong switch, port, or VLAN, he/she may experience a total breakdown in communication or just suffer with slow response time.
3.
Cabling Problems Cabling is one of the most common causes of network problems.
It's one of the few parts of the network that end users can get their hands on, so it's not surprising things go wrong.
4.
Power over Ethernet The number of devices powered by Ethernet is exploding as companies deploy technology to support VoIP phones, security cameras, and wireless access points.
If a deivce doesn't power up, is the problem the cable, the device or the switch sourcing the power? And what if the power source is marginal because the cable is bad or too long or the switch is simply overloaded? Testing the PoE can answer these questions.
5.
Network services Being unable to access network services such as DNS or DHCP from the user's desktop can result in symptoms ranging from slow performance to a total lack of communications.
A quick test of these services can rule out these problems.
6.
Connectivity to key resources Once all the basics in 1-5 are addressed, the final issue is whether the network will carry the user's traffic to the places it needs to go.
For example, can the user reach the corporate intranet, email servers, cloud? Or is something blocking access? >> What Can LinkRunner Help You Do? Fluke's LinkRunner AT provides the answers you need to quickly troubleshoot connectivity problems.
It can answer all the following questions.
1.
Where does this cable or jack go? 2.
How is this switch port provisioned? 3.
Can I negotiate a Gigabit link? 4.
Are there 802.
1x security conflicts? 5.
Are the DHCP and DNS servers working? 6.
Can I get enough power from this port? 7.
Can I connect to servers and the Internet with IPv4 and IPv6? 8.
Can I connect over copper or fiber links? 9.
Is this patch cable good?
SHARE
