tracert wierd results???

[Guest]

I'll try to keep this as short as possible. I'm getting bizarre results when
doing tracert in cmd. Some quick system specs are:

abit at8 32x mobo
opteron 170 cpu
enermax 620w psu
ocz 2 x 1gb EB platinum ram
ati x1800xl

When doing a trace here are the results I get..

1 1 ms 4294967290 ms 4294967290 ms 192.168.254.254
2 13 ms 7 ms 7 ms 64.230.197.160
3 4294967295 ms 4294967295 ms 4294967295 ms
dis5-sudbury98_Vlan101.net.bell.ca [64.230.226.17]
4 12 ms 1 ms 1 ms core2-sudbury98_GE4-0.net.bell.ca [64.230.226.57]
5 3 ms 3 ms 3 ms core2 toronto63_pos3_0.net.bell.ca [64.230.140.29]

I'm wondering why the out of place pings are not registering or why they
aren't showing properly. I've tried numerous things to test it out including
removing my d-link router and connecting direct as well as trying a different
dsl modem and have gone as far as throwing in a second nic card cause I
thought my onboard realtek rtl8168/8111 pci-e gigabit ethernet nic was
pooched.

Has anyone ever seen this before or could offer some clue as to whats
causing this. I've tried just about everything I can to troubleshoot and am
really stumped at this point.

Thanks for any help

 

[Joe Wright]

I'll try to keep this as short as possible. I'm getting bizarre results when
doing tracert in cmd. Some quick system specs are:

abit at8 32x mobo
opteron 170 cpu
enermax 620w psu
ocz 2 x 1gb EB platinum ram
ati x1800xl

When doing a trace here are the results I get..

1 1 ms 4294967290 ms 4294967290 ms 192.168.254.254
2 13 ms 7 ms 7 ms 64.230.197.160
3 4294967295 ms 4294967295 ms 4294967295 ms
dis5-sudbury98_Vlan101.net.bell.ca [64.230.226.17]
4 12 ms 1 ms 1 ms core2-sudbury98_GE4-0.net.bell.ca [64.230.226.57]
5 3 ms 3 ms 3 ms core2 toronto63_pos3_0.net.bell.ca [64.230.140.29]

I'm wondering why the out of place pings are not registering or why they
aren't showing properly. I've tried numerous things to test it out including
removing my d-link router and connecting direct as well as trying a different
dsl modem and have gone as far as throwing in a second nic card cause I
thought my onboard realtek rtl8168/8111 pci-e gigabit ethernet nic was
pooched.

Has anyone ever seen this before or could offer some clue as to whats
causing this. I've tried just about everything I can to troubleshoot and am
really stumped at this point.

Some sites don't allow that type of packet, or PING. I tried a tracert
to that site and got:

C:\Documents and Settings\Owner>tracert 64.230.226.17

Tracing route to dis5-sudbury98_Vlan101.net.bell.ca [64.230.226.17]
over a maximum of 30 hops:

1 22 ms 23 ms 23 ms loudsl01.lou.02.gateway.iglou.com
[64.253.100.1]

2 25 ms 23 ms 23 ms lou1-fe4-1-0.lou.iglou.com [204.252.74.6]
3 * lou1-fe4-1-0.lou.iglou.com [204.252.74.6] reports:
Destination host unreachable.

Trace complete.

I don't think it's a big deal that you get a wild number though.. the
rest of the tracert gives you the needed information, that there's no
big delay past that location.