Simultaneous trace causes packet loss in hop 2.

Hi,

Everytime I try a new trace with the bbol.embanet.com one, I get subtantial packet loss in hop 2.

The tracerts;

http://ispzone.ca/pingplotter-forum/tracert-server3.ispgeeks.com.pp2

http://ispzone.ca/pingplotter-forum/tracert-www.cahpionline.ca.pp2

Effect on hop 2 of the bbol.embanet,com tracert;

http://ispzone.ca/pingplotter-forum/tracert-issue-bbol.embanet.com.pp2

>Any insight for me on this? Doesn't seem to be affecting any other hops.

Thank you,

The pattern you're seeing looks a lot like a piece of hardware that doesn't like responding to multiple ICMP requests with TTL=0. We have a router here that does this - and if you trace to multiple targets one of the hops toggles between packet loss in the different targets. It always responds right on one target, but the other ones time out.

The fact that it doesn't affect downstream hops is an indication that you shouldn't put much weight on it. More details here:

http://www.nessoft.com/kb/24

I tought something weird was happening there for sure.

I read your entire manual, support section, plus the forum. I'm going over it a second time now. I really want to get the software down patt. I will be using quite often.

That's one thing that stuck with me, the fact about the final destination being the most important hop. When I didn't see any loss in the other hops, I felt confident that it was ok, just didn't know what was causing it.

Thank you for your response.