DaveAtIFG - 2:57 pm on Jun 30, 2001 (gmt 0)

Robert, try simply using a trace route. On W2k, from a command prompt (DOS box), I use "tracert www.webmasterworld.com."

For me the first few hops are from my system to my router then to the ISP as below:
C:\>tracert www.webmasterworld.com

Tracing route to www.webmasterworld.com [216.71.185.24]
over a maximum of 30 hops:

1 <10 ms <10 ms <10 ms 192.168.123.254
2 50 ms 30 ms 40 ms 10.252.66.1
3 80 ms 60 ms 50 ms XXX-XX-XX-XX-XX.az.sprintbbd.net [XX.XXX.XXX.XX]
4 51 ms 50 ms 30 ms 10.254.3.1
5 * 70 ms 31 ms host-217.genuity.net [207.240.103.217]
6 30 ms 50 ms 30 ms gigabitethernet5-0.phxcolo-dbe1.bbnplanet.net [1
28.11.199.85]

In this trace the first hop is to my router, 192.168.123.XXX usually indicates a device providing DHCP addressing. The second hop is to my ISP's router, the third is to the ISP's system. Next a router, then a concentrator, and then onto the backbone.

NeoTrace is a visual trace route program that does DNS lookups, whois lookups, etc, all in one package and makes seeing and understanding these relations quite a bit easier. Check out the trial version here [neoworx.com].