bos2420 wrote:
Apparently, this happens with any 'Old Timey' website. :smileyvery-happy:
Just tried to look at a link on Yahoo. Same error message. Figured it was just the link. Tried to go to Yahoo.com. Nope.
Went to the phone hotspot. Loads right up.
E-mail sent to Customer Service, requesting to test a new modem.
Ah, the plot thickens! Here's what I get running traceroute to aol.com:
traceroute to aol.com (106.10.218.150), 30 hops max, 60 byte packets
1 192.168.42.1 (192.168.42.1) 0.278 ms 0.249 ms 0.231 ms
2 100.67.205.153 (100.67.205.153) 0.470 ms 0.523 ms 0.610 ms
3 dpc6935186182.direcpc.com (69.35.186.182) 627.393 ms 687.188 ms 687.168 ms
4 dpc6935188058.direcpc.com (69.35.188.58) 687.121 ms 707.026 ms 707.022 ms
5 ae13-575.edge3.Denver1.Level3.net (4.28.103.141) 706.975 ms 725.744 ms 725.895 ms
6 * * *
7 PCCW-level3-30G.Dallas1.Level3.net (4.68.110.246) 791.410 ms 791.437 ms 791.389 ms
8 TenGE0-1-0-17.br02.hkg12.pccwbtn.net (63.218.174.61) 981.199 ms 786.976 ms 766.663 ms
9 63-216-176-170.static.pccwglobal.net (63.216.176.170) 756.616 ms 766.603 ms 744.669 ms
10 et-3-3-0.pat1.sgy.yahoo.com (183.177.82.40) 764.490 ms 774.403 ms 838.837 ms
11 ae-5.msr1.sg3.yahoo.com (203.84.209.87) 838.634 ms 789.498 ms 789.302 ms
12 ae-2.clr2-a-gdc.sg3.yahoo.com (106.10.128.5) 789.140 ms ae-2.clr1-a-gdc.sg3.yahoo.com (106.10.128.3) 879.374 ms 779.340 ms
13 lo0.fab1-3-gdc.sg3.yahoo.com (106.10.131.217) 865.655 ms lo0.fab2-3-gdc.sg3.yahoo.com (106.10.131.216) 855.578 ms lo0.fab4-3-gdc.sg3.yahoo.com (106.10.131.214) 889.348 ms
14 lo0.usw2-1-lba.sg3.yahoo.com (106.10.128.239) 889.240 ms lo0.usw1-1-lba.sg3.yahoo.com (106.10.128.238) 869.501 ms lo0.usw2-1-lba.sg3.yahoo.com (106.10.128.239) 859.566 ms
15 w2.src4.vip.sg3.yahoo.com (106.10.218.150) 779.505 ms 779.419 ms 789.324 ms
As you can see, yahoo.com shows up several times. Like I said before I'm not sure about what all of this means, but it looks like yahoo.com is on the way to aol.com. Or maybe I should say it's in the way. :>)>
I doubt the modem is your problem. I think the problem is past the Hughes gateway. I'm surprised you haven't heard from a mod about this yet. Like I said, I've seen problems that were similar before.
BTW if you upgrade to gen5, make sure you don't plug the modem in to your system until the bonus period, otherwise you'll take a big hit to your anytime data just for the modem to initialize.