Stop Network Troubleshooting the Wrong Way

1. Start network troubleshooting from the end-user perspective.

Typical network troubleshooting starts with a “prove it’s not the network” mantra but that doesn’t make users cheer for IT.

2. Know the limits of packet capture.

Most laptops can’t capture large enough files. That means you’re looking for packets in a file that’s already got some gaps.

3. DO baseline your network performance.

How can you know what’s normal or slow if you don’t baseline.

4. Assess your troubleshooting toolkit.

Many organizations are using limited or outdated solutions for today’s complex networks.

5. Don’t assume you need more bandwidth.

This may seem like a quick and inexpensive fix but if bandwidth isn’t the real issue, the problems aren’t resolved.

Source: Fluke Networks