Hey Serg,

Thanks for getting in touch!

That sounds pretty frustrating, but I bet PingPlotter can help with that! You'll need to know a bit of background first - PingPlotter uses traceroute to provide results. For this reason, you can absolutely perform a PingPlotter trace to a device you're having troubles with, and you should be able to monitor it with no problem. However, if the only thing between you and the problem device are switches, those switches won't decrement TTLs, even if they have IP addresses, because the switches will probably be operating on layer 2 - so the switches won't show up in your traceroute. However, you can pinpoint them directly if they have an IP address (they just won't show up if traffic is going through them because of that multilayer functionality).

So, what does this mean for you? If you're having trouble on your LAN getting to other devices, I would recommend tracing to the device you're having troubles with. See how many hops show up in between you and the device, and then add some direct traces to any multilayer switches that might not have shown up in the PingPlotter trace. This should help you get eyes on every point of your network - and you should be able to narrow down from there where the poorly responding device is. You can also copy this strategy if you're having problems with the Internet - all the way up to your edge device.

Feel free to send us share pages if you wish via File -> Share -> Create Share Page. We're always happy to take a look!