- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
After several attempts at customer service, I am still having persistent problems with corrupted downloads. Microsoft update is going nuts trying to download updates that are always corrupted. Checksums do not match.
Let me start by stating that the computer has just been reloaded with a pristine OS (not to mention the usual swaptronics tricks: cables, ports, NIC card, etc.), passed all diagnostic scans, and has already been connected to other networks where it downloads just fine. The computer has been eliminated as a source of the problem. The most recent tech call (my 6th call) has resulted in the technical supervisor stating that I have the wrong router.
Yet there is one point that still bugs me that is not being addressed while I wait for the new router to be installed. Trace route keeps hanging intermittently on hop 4 as shown below ...
C:\Documents and Settings\xxx>tracert www.google.com
Tracing route to www.l.google.com [72.14.204.147]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 4 ms 4 ms L100.BLTMMD-VFTTP-21.verizon-gni.net [71.127.152.1]
3 8 ms 6 ms 5 ms 0-3-3-0.BLTMMD-LCR-22.verizon-gni.net [130.81.178.186]
4 * * * Request timed out.
5 14 ms 14 ms 14 ms so-11-1-0-0.RES-BB-RTR2.verizon-gni.net [130.81.19.76]
6 14 ms 15 ms 14 ms 0.xe-10-0-0.BR2.IAD8.ALTER.NET [152.63.34.9]
7 16 ms 15 ms 14 ms xe-4-0-0.edge1.Washington4.level3.net [4.68.63.141]
8 15 ms 16 ms 15 ms ae-1-69.edge1.Washington1.Level3.net [4.68.17.16]
9 20 ms 16 ms 15 ms GOOGLE-INC.edge1.Washington1.Level3.net [4.79.22.38]
10 17 ms 23 ms 17 ms 209.85.240.136
11 26 ms 26 ms 25 ms 66.249.94.54
12 18 ms 17 ms 17 ms iad04s01-in-f147.1e100.net [72.14.204.147]
Trace complete.
C:\Documents and Settings\xxx>tracert www.google.com
Tracing route to www.l.google.com [72.14.204.104]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 4 ms 4 ms L100.BLTMMD-VFTTP-21.verizon-gni.net [71.127.152.1]
3 6 ms 6 ms 6 ms 0-3-3-0.BLTMMD-LCR-21.verizon-gni.net [130.81.178.62]
4 11 ms 11 ms 10 ms so-7-2-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net [130.81.29.120]
5 11 ms 10 ms 11 ms 0.ge-7-0-0.XL3.IAD8.ALTER.NET [152.63.34.201]
6 12 ms 10 ms 11 ms 0.xe-10-1-0.BR2.IAD8.ALTER.NET [152.63.37.153]
7 12 ms 10 ms 12 ms xe-5-1-0.edge1.washinton4.level3.net [4.68.62.97]
8 12 ms 12 ms 12 ms ae-2-79.edge1.Washington1.Level3.net [4.68.17.80]
9 45 ms 12 ms 12 ms GOOGLE-INC.edge1.Washington1.Level3.net [4.79.228.38]
10 14 ms 13 ms 13 ms 209.85.240.136
11 16 ms 20 ms 14 ms 66.249.94.46
12 14 ms 15 ms 13 ms iad04s01-in-f104.1e100.net [72.14.204.104]
Trace complete.
C:\Documents and Settings\xxx>tracert www.google.com
Tracing route to www.l.google.com [72.14.204.104]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 5 ms 4 ms L100.BLTMMD-VFTTP-21.verizon-gni.net [71.127.152.1]
3 10 ms 6 ms 6 ms 0-3-3-0.BLTMMD-LCR-21.verizon-gni.net [130.81.178.62]
4 10 ms 10 ms 10 ms so-7-2-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net [130.81.29.120]
5 12 ms 11 ms 10 ms 0.ge-7-0-0.XL3.IAD8.ALTER.NET [152.63.34.201]
6 11 ms 10 ms 11 ms 0.xe-8-1-0.BR2.IAD8.ALTER.NET [152.63.37.149]
7 13 ms 11 ms 10 ms xe-5-1-0.edge1.washinton4.level3.net [4.68.62.97]
8 14 ms 11 ms 11 ms ae-2-79.edge1.Washington1.Level3.net [4.68.17.80]
9 11 ms 13 ms 12 ms GOOGLE-INC.edge1.Washington1.Level3.net [4.79.228.38]
10 16 ms 14 ms 14 ms 209.85.240.136
11 17 ms 15 ms 19 ms 66.249.94.46
12 15 ms 14 ms 14 ms iad04s01-in-f104.1e100.net [72.14.204.104]
Trace complete.
C:\Documents and Settings\xxx>tracert www.google.com
Tracing route to www.l.google.com [72.14.204.99]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 6 ms 5 ms 4 ms L100.BLTMMD-VFTTP-21.verizon-gni.net [71.127.152.1]
3 28 ms 6 ms 5 ms 0-3-3-0.BLTMMD-LCR-22.verizon-gni.net [130.81.178.186]
4 * * * Request timed out.
5 14 ms 16 ms 15 ms so-11-1-0-0.RES-BB-RTR2.verizon-gni.net [130.81.19.76]
6 15 ms 14 ms 14 ms 0.xe-10-0-0.BR2.IAD8.ALTER.NET [152.63.34.9]
7 15 ms 14 ms 14 ms xe-4-0-0.edge1.Washington4.level3.net [4.68.63.141]
8 16 ms 15 ms 81 ms ae-3-89.edge1.Washington1.Level3.net [4.68.17.144]
9 18 ms 52 ms 17 ms GOOGLE-INC.edge1.Washington1.Level3.net [4.79.228.38]
10 18 ms 17 ms 18 ms 209.85.240.136
11 22 ms 18 ms 18 ms 66.249.94.54
12 17 ms 19 ms 18 ms iad04s01-in-f99.1e100.net [72.14.204.99]
Trace complete.
C:\Documents and Settings\xxx>tracert www.google.com
Tracing route to www.l.google.com [72.14.204.99]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 5 ms 4 ms 4 ms L100.BLTMMD-VFTTP-21.verizon-gni.net [71.127.152.1]
3 7 ms 6 ms 7 ms 0-3-3-0.BLTMMD-LCR-22.verizon-gni.net [130.81.178.186]
4 * * * Request timed out.
5 26 ms 15 ms 15 ms so-11-1-0-0.RES-BB-RTR2.verizon-gni.net [130.81.19.76]
6 13 ms 14 ms 14 ms 0.xe-10-0-0.BR2.IAD8.ALTER.NET [152.63.34.9]
7 14 ms 15 ms 14 ms xe-4-0-0.edge1.Washington4.level3.net [4.68.63.141]
8 16 ms 15 ms 14 ms ae-3-89.edge1.Washington1.Level3.net [4.68.17.144]
9 17 ms 17 ms 16 ms GOOGLE-INC.edge1.Washington1.Level3.net [4.79.228.38]
10 17 ms 17 ms 17 ms 209.85.240.136
11 25 ms 19 ms 19 ms 66.249.94.46
12 17 ms 18 ms 17 ms iad04s01-in-f99.1e100.net [72.14.204.99]
Trace complete.
Needless to say being an IT guy, this is not normal. What do I have to do to ever get this problem corrected? I know that you have to go step by step in your checklist, but this just jumps out and smacks me in the face as something really not right. Either a router should blackhole or it shouldn't. It can't just decide at random intervals to jump between the two states.
Can someone PLEASE check this out and get back to me!
I really like the download rates that Verizon provides, but with constantly broken downloads and broken updates, I really don't want to go back to Comcast.
Solved! Go to Correct Answer
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
AFTER ACTION REPORT:
Looks like Verizon pulled one out at the last minute and decided to keep a customer.
Service tech came out and I was ready to show him how two different computers could download the same file multiple times and each file has a different checksum. After the demonstration, he replaced the router (though I had been told subsequently that Verizon only had one type of router) and everything worked. All the checksums matched! They guy wasn't here more than 20 minutes. The first two routers were Actiontech M24-W while the last router was an Actiontech MI424-WR. Even the router setup menu was different.
The blackholling router that keeps switching in and out did not have any relation to the problem, and yes, its still blackholling.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Switching to a blackholed router?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
So what router do you have that VZ says is the wrong one?
What is a blackholed router?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
@viafax999 wrote:So what router do you have that VZ says is the wrong one?
What is a blackholed router?
A blackholed router is a router programed not to respond to ping requests. Happens all the time. That would be my guess here as when hop 4 doesnt respond, it doesnt respond at all. Generally when you have a router that is dropping packets, you will get a ping through here and there. But on the ones listed, it either always responds or never responds. It looks like a routing change up routing through a black hole router
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
AFTER ACTION REPORT:
Looks like Verizon pulled one out at the last minute and decided to keep a customer.
Service tech came out and I was ready to show him how two different computers could download the same file multiple times and each file has a different checksum. After the demonstration, he replaced the router (though I had been told subsequently that Verizon only had one type of router) and everything worked. All the checksums matched! They guy wasn't here more than 20 minutes. The first two routers were Actiontech M24-W while the last router was an Actiontech MI424-WR. Even the router setup menu was different.
The blackholling router that keeps switching in and out did not have any relation to the problem, and yes, its still blackholling.