crazy TRACERT and PING reporting (introduced in latest critical patches)

  • Thread starter Thread starter jeff23
  • Start date Start date
J

jeff23

I'm seeing whacky results since the last Microsoft Critical Update
(late April or Early May 2006)

The times it's reporting here and there are impossible, so it's leading

me to believe it's reporting it incorrectly.


1 1 ms 1 ms 1 ms c-65-97-0-123.hsd1.va.comcast.net
[65.97.0.123]
2 10 ms 9 ms 15 ms 73.142.104.1
3 4294967283 ms 9 ms 8 ms 68.86.174.89
4 10 ms 9 ms 17 ms 68.86.172.34
^C
H:\>tracert www.biznet.net


sometimes:


Tracing route to biznet.net [65.246.56.24]
over a maximum of 30 hops:


1 4294967275 ms 4294967275 ms 4294967275 ms
c-65-97-0-123.hsd1.va.comcast.
net [65.97.0.123]
2 9 ms 4294967282 ms 4294967288 ms 73.142.104.1
3 4294967284 ms 4294967288 ms 4294967282 ms 68.86.174.89
4 4294967284 ms 4294967286 ms 4294967282 ms 68.86.172.34
5 4294967285 ms 4294967284 ms 4294967286 ms 68.86.172.81
6 4294967284 ms 4294967284 ms 4294967284 ms 68.86.172.122
7 4294967291 ms 4294967292 ms 4294967290 ms 12.126.174.21
8 4294967289 ms 4294967290 ms 4294967291 ms
gbr5-p30.wswdc.ip.att.net [12.
123.9.66]
9 4294967291 ms 3 ms <1 ms tbr1-p013301.wswdc.ip.att.net
[12.122.11.1
69]
---------------------------------------------


When the problem occurs, my ping is reported to gaming servers as way
to high and I get bumped off of the server, though my throughput is
truly ok...


It seems that there is something corrupt...


Here are the things I've already tried:


1. reinstalled XP from scratch... Probablem did not resurface until I
applied the latest critical updates. Microsoft ignores my information
and will not ackowledge the issue.
2. bought a totally different NIC, thinking maybe it was the onboard
ethernet controller.
3. run network without router connected directly to the cable modem.
4. did a traceroute to 127.0.0.1 and saw the same results
intermittantly.
5. do a ping, and it reports negative numbers as the max ping time, and

millions for the average.
6. updated all NIC drivers.
7. ran with and without microsoft's firewall.
8. ran it without any other programs loaded or running (again, note it
did not resurface in a fresh install until the critical updates were
applied).


If anyone has seen this before, please let me know. (email:
(e-mail address removed)) j e f f 2 3 @ w a d a s i a . c o m

any help is appreciated,

Thanks,


Jeff
 
I'm seeing whacky results since the last Microsoft Critical Update
(late April or Early May 2006)

The times it's reporting here and there are impossible, so it's leading
Click to expand...

All updates installed here, and not seeing this. However, I found a
lot of sites slow around that time; I believe there was a worm
extant.
 
This is the whacky results of traceoutes.... It's not time
dependant... It happens any time... IT even happens when doing a
tracert to 127.0.0.1 (that doesn't even use the NIC):

C:\>tracert cnn.com

Tracing route to cnn.com [64.236.24.28]
over a maximum of 30 hops:

1 4294967275 ms 1 ms 1 ms
c-24-30-250-176.hsd1.va.comcast.net [24.30
..250.176]
2 7 ms 8 ms 11 ms 73.142.104.1
3 9 ms 11 ms 9 ms 68.86.174.89
4 9 ms 7 ms 8 ms 68.86.172.34
5 12 ms 10 ms 15 ms 68.86.172.81
6 10 ms 8 ms 9 ms 68.86.172.126
7 4294967290 ms 16 ms 15 ms 12.126.174.21
8 15 ms 16 ms 17 ms gbr5-p30.wswdc.ip.att.net [12.123.9.66]
9 4294967292 ms 18 ms 15 ms tbr1-p013301.wswdc.ip.att.net
[12.122.11.1
69]
10 16 ms 15 ms 15 ms 12.123.8.97
11 16 ms 15 ms 15 ms pop2-ash-p13-1.atdn.net
[66.185.140.249]
12 4294967291 ms 15 ms 38 ms bb1-ash-p1-0.atdn.net
[66.185.139.208]
13 4294967293 ms 16 ms 17 ms bb1-vie-p11-0.atdn.net
[66.185.152.99]
14 65 ms 9 ms 32 ms bb1-rdu-p4-0.atdn.net [66.185.152.14]
15 32 ms 35 ms 31 ms bb2-rdu-p2-0.atdn.net [66.185.152.3]
16 83 ms 203 ms 206 ms bb2-atm-p6-0.atdn.net [66.185.152.30]
17 28 ms 7 ms 30 ms pop1-atl-p5-0.atdn.net [66.185.136.35]
 
Back
Top