Trouble Reaching Web Sites

I'm in TN and having the same issue. Going to

or doesn't work. I can get to other sites just fine. A Tracert to 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:

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.

In the past I have posted news articles about DSL Extreme's excellent net connectivity. They are full-blown f****ng 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

Subject: Re: New DSLExtreme Ticket[#1634861-2336#] To: snipped-for-privacy@MIX.COM Message-id: 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 snipped-for-privacy@dslextreme.com or call us at (866) 491-7221.

Thanks for choosing DSLExtreme!

-------Original Message------- To: snipped-for-privacy@dslextreme.com

Date: 7/20/2006 3:48:27 PM Subject: Re: New DSLExtreme Ticket[#1634861-2336#]

Hi -

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

traceroute to (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

traceroute to (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

80 Trying 68.178.229.85...

Here's what that should look like -

$ telnet

Trying... Connected to

quit 501 Method Not Implemented Method Not Implemented quit to /index.html not supported. Apache/2.0.51 (Fedora) Server at default Port 80

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..