C:\WINDOWS>tracert www.yahoo.com
Tracing route to www6.yahoo.com [204.71.177.71]
over a maximum of 30 hops:
1 3 ms 3 ms 2 ms router1.cyberlink-inc.com [206.64.229.1]
2 10 ms 6 ms 6 ms 206.64.228.1
3 10 ms 11 ms 10 ms Loopback0.GW3.CHI1.Alter.Net [137.39.2.28]
4 * * 217 ms 423.atm1-0.cr2.chi1.alter.net [137.39.13.98]
5 25 ms 11 ms 11 ms 312.atm1-0.br1.chi1.alter.net
[137.39.13.105]
6 21 ms 23 ms 30 ms core3-hssi3-0.WillowSprings.mci.net
[206.157.77.
81]
7 77 ms 68 ms 88 ms bordercore2-loopback.Bloomington.mci.net
[166.48
..176.1]
8 71 ms 69 ms 69 ms internet-connection.Bloomington.mci.net
[166.48.
177.254]
9 80 ms 69 ms 70 ms core1-fe4-0.MV.isi.net [206.251.1.1]
10 73 ms 78 ms 82 ms www6.yahoo.com [204.71.177.71]
Trace complete.
>
>
> 1 * * * Request timed out.
> 2 60 ms 60 ms 60 ms 207.107.201.69
> 3 60 ms 70 ms 60 ms core-spc-van-1-fddi3/0.Sprint-Canada.Net
>
>
> Trace complete.
> ----
>
> The first hop times out *every time*.
>
> * * * * * * ** * *
>
> I have noticed this with every Win95 machine I had. I think there is a
> limit to the microsoft traceroute program. Either that or it doesn't like
> 10base2
>
> David Payer
> www.ia-omni.com
>
>
>
> ----------------------------------------------------------
> NTISP Mailing List listserver@emerald.iea.com
>
Zak Wolfinger - zak@michianatoday.com
Systems Administrator - CyberLink, Inc.
(219)235-1400 (219)674-8279
FAX (219)235-1599