Pete, I bought a LinkSys BEFSR11 router. It's a cheap ($100) Ether to Ether box that does NAT and some firewalling. I have the latest version 1.37 firmware.<br><br>When you are running a tracert through the box the first hop (which is the linksys) sometimes the IP address of the DESTINATION.<br><br>Tracing route to [] over a maximum of 30 hops:<br><br> 1 <10 ms <10 ms <10 ms []<br> 2 20 ms 20 ms 20 ms []<br> 3 20 ms 20 ms 20 ms []<br><snip><br> 12 80 ms 91 ms 80 ms []<br><br>Trace complete.<br><br>When you use pingplotter it stops at the first hop as the "destination" is responding. I then set View / Ignore First Hop(1) and restart the trace. I then see the full trace.<br><br>It looks like the Windows NT and 2000 tracert applications continue to trace if they get a TTL expired from the destination. They only stop tracing when the final destination returns an echo-response. PingPlotter stops as soon as any gets any form of response from the destination, even if it was a TTL timeout.<br><br>Also, I said that the LinkSys *sometimes* returns the destination. At other times the box seems to act like a transparent bridge meaning that hop 1 is one step beyond the linksys.<br><br>I'd recommend two things for pingplotter<br>1) If you receive a TTL timeout from the destination then continue incrementing the TTL until you get an normal response.<br>2) Add a readme about the LinkSys that informs people of the first hop behavior.<br><br>