Trouble Reaching Web Sites
Bookmark this page:
 Yahoo!
 Google
 Windows Live
 del.icio.us
 digg
 Netscape
|
|
||||||||||||||||
|
Posted by Shel on August 18, 2006, 5:34 pm
Please log in for more thread options I am having considerable trouble reaching some web sites. A good example is www.pcworld.com. I usually cannot get it to display. My browser, Firefox, says it is "Waiting for images.pcworld.com" or "Looking up ad.doubleclick.net". Internet Explorer does much the same, saying "Opening page http://www.pcworld.com/...', but that is as far as it goes. I can reach my ISP, DSLExtreme, and most other sites with no problem. My download speed from a few test sites averages 730 kbps. I am using Windows XP Home Edition with SP2. My CPU speed is 3.0 GHz. Here are ping and tracert results to pcworld.com. (I am in Los Angeles.) ------ ping pcworld.com Pinging pcworld.com [65.220.224.30] with 32 bytes of data: Reply from 65.200.195.37: Destination net unreachable. Request timed out. Reply from 65.200.195.37: Destination net unreachable. Reply from 65.200.195.37: Destination net unreachable. Ping statistics for 65.220.224.30: Packets: Sent = 4, Received = 3, Lost = 1 (25% loss), Approximate round trip times in milli-seconds: Minimum = 0ms, Maximum = 0ms, Average = 0ms ------ tracert pcworld.com Tracing route to pcworld.com [65.220.224.30] over a maximum of 30 hops: 1 35 ms 34 ms 33 ms netblock-68-183-58-1.dslextreme.com [68.183.58.1] 2 34 ms 34 ms 35 ms LAX1.CR1.Gig9-0-3.dslextreme.com [66.51.203.33] 3 35 ms 35 ms 34 ms GigabitEthernet5-3.GW1.LAX1.ALTER.NET [208.222.10.69] 4 35 ms 34 ms 34 ms 0.so-0-0-0.XL1.LAX1.ALTER.NET [152.63.112.218] 5 47 ms 47 ms 47 ms 0.so-4-0-0.XL1.SJC1.ALTER.NET [152.63.55.121] 6 49 ms 122 ms 49 ms 0.so-6-0-0.GW6.SJC1.ALTER.NET [152.63.56.173] 7 46 ms 47 ms 48 ms pos5-0.ur1.sjc5.web.wcom.net [152.63.54.170] 8 45 ms 45 ms 50 ms 63.66.208.5 9 54 ms 47 ms 49 ms 63.66.208.214 10 65.200.195.37 reports: Destination net unreachable. Trace complete. ------ Here is a reverse tracert from Numion.com to me. Traceroute from the Numion server (Amsterdam, The Netherlands) to you. Please wait, the traceroute is finished when you see "Trace complete". Tracing route to netblock-68-183-58-230.dslextreme.com [68.183.58.230] over a maximum of 30 hops: 1 <10 ms <10 ms <10 ms v870.m7i.transip.net [80.69.70.220] 2 <10 ms 1 ms 1 ms ams-ix.eweka.nl [195.69.144.94] 3 1 ms 1 ms 1 ms ams-sw1-ge-0-2.prp.wvfiber.net [63.223.28.161] 4 8 ms 8 ms 8 ms lon-c00-pos-4-0.OC48-ams-pos11-0.wvfiber.net [63.223.28.201] 5 87 ms 87 ms 86 ms ny60-a00.pos-4-0.OC48-lon-c00-pos-2-0.wvfiber.net [63.223.28.141] 6 91 ms 91 ms 92 ms ash-c00-pos-1-16-1.OC48-nyc-c00-pos-1-26-1.wvfiber.net [66.216.1.1] 7 108 ms 108 ms 108 ms atl-c00-pos-1-34-1.OC48-ash-c00-pos-1-14-1.wvfiber.net [66.216.1.17] 8 123 ms 123 ms 124 ms dal-c00-pos4-0.OC48.atl-c00-pos-1-14-1.wvfiber.net [63.223.0.82] 9 160 ms 160 ms 160 ms law-c00-pos.OC48.dal-c00-pos5-0.wvfiber.net [63.223.0.85] 10 162 ms 162 ms 162 ms ctr-dsle.law-a00-ge-5-0.wvfiber.net [63.223.32.138] 11 161 ms 161 ms 160 ms netblock-66-51-203-36.dslextreme.com [66.51.203.36] 12 * * * Request timed out. 13 * * * Request timed out. 14 * * * Request timed out. 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. ------ Any help will be much appreciated. | ||||||||||||||||
|
Posted by on August 21, 2006, 10:42 am
Please log in for more thread options I'm in TN and having the same issue. Going to www.dogpile.com or www.tennessean.com doesn't work. I can get to other sites just fine. A Tracert to www.tennessean.com results in the "Destination Net Unreachable" after hitting about 10 hops. Very odd. Please update us if you get anywhere and I will do the same. jf Shel wrote: | ||||||||||||||||
|
Posted by Shel on August 21, 2006, 12:18 pm
Please log in for more thread options
A Tech Support 'agent' at my ISP suggested a solution that worked. I cannot explain why it works, but it did. He suggested uninstalling my spyware checker (Spy Sweeper, in my case) -- not just stopping it, but removing it from my computer. I did that and my problem was gone. I reinstalled Spy Sweeper, and everything still works. Please let me know if it works for you. Good luck. On 21 Aug 2006 07:42:34 -0700, jfranks1970@gmail.com wrote: >I'm in TN and having the same issue. Going to www.dogpile.com or
>www.tennessean.com doesn't work. I can get to other sites just fine. >A Tracert to www.tennessean.com results in the "Destination Net >Unreachable" after hitting about 10 hops. > >Very odd. > >Please update us if you get anywhere and I will do the same. > >jf > > >Shel wrote: >> I am having considerable trouble reaching some web sites. A good
>> example is www.pcworld.com. I usually cannot get it to display. My >> browser, Firefox, says it is "Waiting for images.pcworld.com" or >> "Looking up ad.doubleclick.net". Internet Explorer does much the same, >> saying "Opening page http://www.pcworld.com/...', but that is as far >> as it goes. I can reach my ISP, DSLExtreme, and most other sites with >> no problem. >> >> My download speed from a few test sites averages 730 kbps. I am using >> Windows XP Home Edition with SP2. My CPU speed is 3.0 GHz. >> >> Here are ping and tracert results to pcworld.com. (I am in Los >> Angeles.) >> >> ------ >> ping pcworld.com >> >> Pinging pcworld.com [65.220.224.30] with 32 bytes of data: >> Reply from 65.200.195.37: Destination net unreachable. >> Request timed out. >> Reply from 65.200.195.37: Destination net unreachable. >> Reply from 65.200.195.37: Destination net unreachable. >> >> Ping statistics for 65.220.224.30: >> Packets: Sent = 4, Received = 3, Lost = 1 (25% loss), >> Approximate round trip times in milli-seconds: >> Minimum = 0ms, Maximum = 0ms, Average = 0ms >> >> ------ >> tracert pcworld.com >> >> Tracing route to pcworld.com [65.220.224.30] >> over a maximum of 30 hops: >> >> 1 35 ms 34 ms 33 ms netblock-68-183-58-1.dslextreme.com >> [68.183.58.1] >> 2 34 ms 34 ms 35 ms LAX1.CR1.Gig9-0-3.dslextreme.com >> [66.51.203.33] >> 3 35 ms 35 ms 34 ms GigabitEthernet5-3.GW1.LAX1.ALTER.NET >> [208.222.10.69] >> 4 35 ms 34 ms 34 ms 0.so-0-0-0.XL1.LAX1.ALTER.NET >> [152.63.112.218] >> 5 47 ms 47 ms 47 ms 0.so-4-0-0.XL1.SJC1.ALTER.NET >> [152.63.55.121] >> 6 49 ms 122 ms 49 ms 0.so-6-0-0.GW6.SJC1.ALTER.NET >> [152.63.56.173] >> 7 46 ms 47 ms 48 ms pos5-0.ur1.sjc5.web.wcom.net >> [152.63.54.170] >> 8 45 ms 45 ms 50 ms 63.66.208.5 >> 9 54 ms 47 ms 49 ms 63.66.208.214 >> 10 65.200.195.37 reports: Destination net unreachable. >> >> Trace complete. >> >> ------ >> Here is a reverse tracert from Numion.com to me. >> >> Traceroute >> from the Numion server (Amsterdam, The Netherlands) to you. >> Please wait, the traceroute is finished when you see "Trace complete". >> >> Tracing route to netblock-68-183-58-230.dslextreme.com [68.183.58.230] >> over a maximum of 30 hops: >> >> 1 <10 ms <10 ms <10 ms v870.m7i.transip.net [80.69.70.220] >> 2 <10 ms 1 ms 1 ms ams-ix.eweka.nl [195.69.144.94] >> 3 1 ms 1 ms 1 ms ams-sw1-ge-0-2.prp.wvfiber.net >> [63.223.28.161] >> 4 8 ms 8 ms 8 ms >> lon-c00-pos-4-0.OC48-ams-pos11-0.wvfiber.net [63.223.28.201] >> 5 87 ms 87 ms 86 ms >> ny60-a00.pos-4-0.OC48-lon-c00-pos-2-0.wvfiber.net [63.223.28.141] >> 6 91 ms 91 ms 92 ms >> ash-c00-pos-1-16-1.OC48-nyc-c00-pos-1-26-1.wvfiber.net [66.216.1.1] >> 7 108 ms 108 ms 108 ms >> atl-c00-pos-1-34-1.OC48-ash-c00-pos-1-14-1.wvfiber.net [66.216.1.17] >> 8 123 ms 123 ms 124 ms >> dal-c00-pos4-0.OC48.atl-c00-pos-1-14-1.wvfiber.net [63.223.0.82] >> 9 160 ms 160 ms 160 ms >> law-c00-pos.OC48.dal-c00-pos5-0.wvfiber.net [63.223.0.85] >> 10 162 ms 162 ms 162 ms ctr-dsle.law-a00-ge-5-0.wvfiber.net >> [63.223.32.138] >> 11 161 ms 161 ms 160 ms netblock-66-51-203-36.dslextreme.com >> [66.51.203.36] >> 12 * * * Request timed out. >> 13 * * * Request timed out. >> 14 * * * Request timed out. >> 15 * * * Request timed out. >> 16 * * * Request timed out. >> 17 * * * Request timed out. >> 18 * * * Request timed out. >> 19 * * * Request timed out. >> 20 * * * Request timed out. >> 21 * * * Request timed out. >> 22 * * * Request timed out. >> 23 * * * Request timed out. >> 24 * * * Request timed out. >> 25 * * * Request timed out. >> 26 * * * Request timed out. >> 27 * * * Request timed out. >> 28 * * * Request timed out. >> 29 * * * Request timed out. >> 30 * * * Request timed out. >> >> Trace complete. >> >> ------ >> >> Any help will be much appreciated. | ||||||||||||||||
|
Posted by on August 22, 2006, 10:44 am
Please log in for more thread options
> I can reach my ISP, DSLExtreme, and most other sites with
> no problem. In the past I have posted news articles about DSL Extreme's excellent net connectivity. They are full-blown fucking morons when it comes to anything else, but they did have, whether by accident or design, fabulous connectivity. And I am still just 6-8 ms from all the major backbone nets. BUT -- I also run some mailing lists, and I frequently see DSL Extreme users blocked by other ISPs. Their mail gets returned. Then more recently, I ws trying to look at the MAM-A.COM (Mitsui Advanced Media) weeb site. I had no connectivity to it. I then tried some of the other nets I have available - they all worked. Apparently DSL Extreme doesn't police their own net very well, thus they are getting blocked by various people who've had it with them. So, I opened a trouble ticket with DSL Extreme. That was an utter waste of time. Not only did they not fix it, they told me I would have to deal with it myself. How's that for being a full-blown chicken-shit net vendor? Remember this is _THEIR_ address block from which I had the problem... I'll append their last note - you can read it and see for yourself. Billy Y.. Date: Tue, 25 Jul 2006 17:15:26 -0700 >From: support@dslextreme.com
Subject: Re: New DSLExtreme Ticket[#1634861-2336#]
To: billy@MIX.COM X-Mailer: Platypus ISP Billing System - Mabry Hello. We tried adjusting how you route to get you a different path to that site, it made no difference. This is an issue with the host of the site. You will need to contact Godaddy or the Webmaster of that site. for further assistance. Matthew M If you have any further questions, please feel free to contact us 24 hours a day. You can E-mail questions to support@dslextreme.com or call us at (866) 491-7221. Thanks for choosing DSLExtreme! -------Original Message------- To: support@dslextreme.com >From: billy@MIX.COM
Date: 7/20/2006 3:48:27 PM
Subject: Re: New DSLExtreme Ticket[#1634861-2336#] Hi - > We looked into this a bit more, and do not see any
> routing problems on our end. Can you please attach > some traceroutes, so that we can get a better feel > for where it is timing out? The problem here has no connection to responses to probes such as traceroute uses, the problem is no connectivity on TCP port 80 to 68.178.229.85 from 68.183.34.2 or 68.183.34.3 while it works fine when someone in your support offices tries it from some other (source) address block. I suspect the only way to replicate it is for you to connect to the router serving me and try to connect from there, or otherwise make the attempt with a source IP address in the same block as mine. That said, here is what the path looks like with traceroute - billy@netblock-68-183-34-3:500$ tra www.mam-a.com traceroute to www.mam-a.com (68.178.229.85), 30 hops max, 40 byte packets 1 netblock-68-183-34-1 (68.183.34.1) 12.112 ms 7.122 ms 12.03 ms 2 lax1.cr1.gig11-0-20.dslextreme.com (66.51.203.1) 7.67 ms 7.88 ms 10.578 ms 3 law-a00-ge-5-0.ctr-dslextreme.wvfiber.net (63.223.32.137) 7.603 ms 8.422 ms 11.535 ms 4 sjc-c00-pos-1-6-1.oc48-lax-c00-pos-1-36-1.wvfiber.net (63.223.0.177) 19.365 ms 19.827 ms 19.575 ms 5 * * * 6 so-5-0-0.mpr4.sjc2.us.above.net (64.125.30.178) 18.554 ms 24.401 ms 24.362 ms 7 so-4-3-0.mpr1.lax9.us.above.net (64.125.27.6) 26.556 ms 26.817 ms 26.108 ms 8 so-4-0-0.mpr1.phx2.us.above.net (64.125.27.198) 33.678 ms 34.177 ms 34.111 ms 9 64.124.113.58.godaddy.com (64.124.113.58) 34.636 ms 34.065 ms 39.238 ms 10 ip-64-202-161-57.secureserver.net (64.202.161.57) 33.925 ms 34.744 ms 34.373 ms 11 ip-216-69-188-1.ip.secureserver.net (216.69.188.1) 28.164 ms 27.041 ms 26.604 ms 12 ip-216-69-188-18.ip.secureserver.net (216.69.188.18) 41.57 ms 34.431 ms 36.955 ms 13 * * * 14 *^C But -- I see the exact same thing looking at it from other nets where I do have connectivity to it on TCP port 80. Like this - $ tra www.mam-a.com traceroute to WWW.MAM-A.COM (68.178.229.85), 99 hops max, 40 byte packets 1 Firewall (192.245.12.78) 0 ms 1 ms 3 ms 2 Opus-GW (207.182.35.49) 1 ms 2 ms 1 ms 3 login-opus-t3 (204.17.35.105) 2 ms 3 ms 2 ms 4 phv-edge-01.inet.qwest.net (65.121.93.133) 8 ms 8 ms 8 ms 5 65.121.90.66 (65.121.90.66) 9 ms 8 ms 10 ms 6 ip-64-202-161-54.secureserver.net (64.202.161.54) 10 ms 9 ms 9 ms 7 ip-64-202-161-57.secureserver.net (64.202.161.57) 11 ms 10 ms 9 ms 8 ip-216-69-188-1.ip.secureserver.net (216.69.188.1) 11 ms 9 ms 11 ms 9 ip-216-69-188-18.ip.secureserver.net (216.69.188.18) 9 ms 11 ms 8 ms 10 * * * 11 Interrupt Here you may see nothing in my hosts file is affecting this site - billy@netblock-68-183-34-3:501$ grep -i secureserver.net /etc/hosts billy@netblock-68-183-34-3:502$ grep -i mam-a.com /etc/hosts And an example of it not responding - billy@netblock-68-183-34-3:503$ telnet www.mam-a.com 80 Trying 68.178.229.85... Here's what that should look like - $ telnet www.mam-a.com/port=80 Trying... Connected to WWW.MAM-A.COM. quit <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head> <title>501 Method Not Implemented</title> </head><body> <h1>Method Not Implemented</h1> <p>quit to /index.html not supported.<br /> </p> <hr /> <address>Apache/2.0.51 (Fedora) Server at default Port 80</address> </body></html> Connection closed by Foreign Host And all this was done with the computer's ethernet plugged directly into the DSL box - no firewall at all. I also have a notebook computer, and I see identical results with it. Thanks, Billy Y.. > Matthew M
> If you have any further questions, please feel free to contact us 24 hours > a day. You can E-mail questions to support@dslextreme.com or call us at > (866) 491-7221. > Thanks for choosing DSLExtreme!
> -------Original Message-------
> To: support@dslextreme.com > From: billy@MIX.COM > CC: mix@dslextreme.com, billy@MIX.COM > Date: 7/19/2006 1:15:06 PM > Subject: Re: New DSLExtreme Ticket[#1634861-2336#] > > Hello! A new DSLExtreme ticket has been created for your issue:
> > Ticket ID: 1634861
> > Time Created: Jul 19 2006 1:07PM > > Issue: customer cannot get to www.mam-a.com > > Resolution (if completed): > > Please include the subject line in any replies concerning this issue.
> To be sure, this site is reachable from DSL Extreme's southern California
> headquarters, as well as from other nets I have available, but I can not > connect to it with a web browser on port 80 from my own DSL Extreme service > in Burbank. That simply times out, there is no response at all received > at my end. I have very carfully checked my own firewall, there is nothing > on my end blocking this connection. Thus I suspect there is some filtering > being done elsewhere which is blocking this site. > > Current customers can view ticket information online by visiting
http://www.dslextreme.com/access
> Thanks,
> Billy Y..
| ||||||||||||||||
| Similar Threads | Posted |
| Trouble Reaching Web Sites | August 18, 2006, 5:34 pm |
| bought a new router, trouble installing, please help | March 3, 2005, 9:51 am |
| Netopia 4652 PPPoA - trouble understanding how to configure static WAN IP.. | November 7, 2004, 8:30 am |
| DSL lag when switching sites | December 15, 2007, 11:15 am |
| Accessing certain sites on AOL via NETGEAR router | July 7, 2005, 8:12 am |
| Fight back: Join together to oppose Verison's blocking of non US sites | January 4, 2005, 4:46 am |
> example is www.pcworld.com. I usually cannot get it to display. My
> browser, Firefox, says it is "Waiting for images.pcworld.com" or
> "Looking up ad.doubleclick.net". Internet Explorer does much the same,
> saying "Opening page http://www.pcworld.com/...', but that is as far
> as it goes. I can reach my ISP, DSLExtreme, and most other sites with
> no problem.
>
> My download speed from a few test sites averages 730 kbps. I am using
> Windows XP Home Edition with SP2. My CPU speed is 3.0 GHz.
>
> Here are ping and tracert results to pcworld.com. (I am in Los
> Angeles.)
>
> ------
> ping pcworld.com
>
> Pinging pcworld.com [65.220.224.30] with 32 bytes of data:
> Reply from 65.200.195.37: Destination net unreachable.
> Request timed out.
> Reply from 65.200.195.37: Destination net unreachable.
> Reply from 65.200.195.37: Destination net unreachable.
>
> Ping statistics for 65.220.224.30:
> Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
> Approximate round trip times in milli-seconds:
> Minimum = 0ms, Maximum = 0ms, Average = 0ms
>
> ------
> tracert pcworld.com
>
> Tracing route to pcworld.com [65.220.224.30]
> over a maximum of 30 hops:
>
> 1 35 ms 34 ms 33 ms netblock-68-183-58-1.dslextreme.com
> [68.183.58.1]
> 2 34 ms 34 ms 35 ms LAX1.CR1.Gig9-0-3.dslextreme.com
> [66.51.203.33]
> 3 35 ms 35 ms 34 ms GigabitEthernet5-3.GW1.LAX1.ALTER.NET
> [208.222.10.69]
> 4 35 ms 34 ms 34 ms 0.so-0-0-0.XL1.LAX1.ALTER.NET
> [152.63.112.218]
> 5 47 ms 47 ms 47 ms 0.so-4-0-0.XL1.SJC1.ALTER.NET
> [152.63.55.121]
> 6 49 ms 122 ms 49 ms 0.so-6-0-0.GW6.SJC1.ALTER.NET
> [152.63.56.173]
> 7 46 ms 47 ms 48 ms pos5-0.ur1.sjc5.web.wcom.net
> [152.63.54.170]
> 8 45 ms 45 ms 50 ms 63.66.208.5
> 9 54 ms 47 ms 49 ms 63.66.208.214
> 10 65.200.195.37 reports: Destination net unreachable.
>
> Trace complete.
>
> ------
> Here is a reverse tracert from Numion.com to me.
>
> Traceroute
> from the Numion server (Amsterdam, The Netherlands) to you.
> Please wait, the traceroute is finished when you see "Trace complete".
>
> Tracing route to netblock-68-183-58-230.dslextreme.com [68.183.58.230]
> over a maximum of 30 hops:
>
> 1 <10 ms <10 ms <10 ms v870.m7i.transip.net [80.69.70.220]
> 2 <10 ms 1 ms 1 ms ams-ix.eweka.nl [195.69.144.94]
> 3 1 ms 1 ms 1 ms ams-sw1-ge-0-2.prp.wvfiber.net
> [63.223.28.161]
> 4 8 ms 8 ms 8 ms
> lon-c00-pos-4-0.OC48-ams-pos11-0.wvfiber.net [63.223.28.201]
> 5 87 ms 87 ms 86 ms
> ny60-a00.pos-4-0.OC48-lon-c00-pos-2-0.wvfiber.net [63.223.28.141]
> 6 91 ms 91 ms 92 ms
> ash-c00-pos-1-16-1.OC48-nyc-c00-pos-1-26-1.wvfiber.net [66.216.1.1]
> 7 108 ms 108 ms 108 ms
> atl-c00-pos-1-34-1.OC48-ash-c00-pos-1-14-1.wvfiber.net [66.216.1.17]
> 8 123 ms 123 ms 124 ms
> dal-c00-pos4-0.OC48.atl-c00-pos-1-14-1.wvfiber.net [63.223.0.82]
> 9 160 ms 160 ms 160 ms
> law-c00-pos.OC48.dal-c00-pos5-0.wvfiber.net [63.223.0.85]
> 10 162 ms 162 ms 162 ms ctr-dsle.law-a00-ge-5-0.wvfiber.net
> [63.223.32.138]
> 11 161 ms 161 ms 160 ms netblock-66-51-203-36.dslextreme.com
> [66.51.203.36]
> 12 * * * Request timed out.
> 13 * * * Request timed out.
> 14 * * * Request timed out.
> 15 * * * Request timed out.
> 16 * * * Request timed out.
> 17 * * * Request timed out.
> 18 * * * Request timed out.
> 19 * * * Request timed out.
> 20 * * * Request timed out.
> 21 * * * Request timed out.
> 22 * * * Request timed out.
> 23 * * * Request timed out.
> 24 * * * Request timed out.
> 25 * * * Request timed out.
> 26 * * * Request timed out.
> 27 * * * Request timed out.
> 28 * * * Request timed out.
> 29 * * * Request timed out.
> 30 * * * Request timed out.
>
> Trace complete.
>
> ------
>
> Any help will be much appreciated.