Verizon DSL blocked? Options

[KevinPacheco]

I can reach this site (and foobar2000.org, which appears to resolve to the IP address) from work, but not from home. This has been going on for at least three weeks, even after I renew the IP address. I haven't noticed any other problems with my service, and I do use it quite heavily. FWIW, traceroutes always die at the penultimate hop.

Details
=====

Home (problems)
Place: Brooklyn, New York, U.S.A.
ISP: Verizon DSL (residential ASDL at 1.5 Mbps down / 384 Kbps up)
My IP address: 70.18.49.59 (dynamic)
Traceroute output: link

Work (no problems)
Place: New York, New York, U.S.A.
ISP: Intellispace (business T-1 at 1.5 Mbps full duplex)
My IP address: 160.79.69.130 (static)
Traceroute output: link

[CiTay]

Don't know what's happening, no 70.x address is banned.

[paranoos]

That's funny.

When I'm connected through my router, Rogers DHCP would give me a 70.x address, and I couldn't access hydrogenaudio. When I'm connected to the modem directly, I would get a 69.x address, and I can access the site normally.

I was blaming my ISP, and then I was blaming my router, but it turns out to be neither's fault... although it is strange that my router would get a different address. Also, I can't successfully trace-route the site past hop 18 (66.0.192.252), so perhaps the problem exists at the router at hop 19? I can ping hydrogenaudio just fine though.

Edit: unlike the above post, trace-route doesn't work even when I can access the site. Which is quite strange.

This post has been edited by paranoos: Sep 27 2004, 20:40

[ven42]

Sorry to resurrect an old thread, but I only just now figured out a way around my not having been able to access the HA site at all for the past couple of months, and it is related to KevinPacheco's problem.

I recently moved about two months ago, and with the move, my ISP changed from Comcast Cable Internet to Verizon DSL. I never had any problem using HA from Comcast, but (until now) I have been completely unable to access the HA site via my new Verizon DSL connection. No other sites have been a problem for me, just HA. My hardware and software has not changed, only the ISP. I have no other form of internet access, so I had almost assumed that HA had gone belly-up (I was very distressed at this prospect!), until it occurred to me to try to access the site through a proxy server, and lo and behold, HA is alive and well and perfectly accessible for me.

So, what's going on here? I don't have enough expertise in the intracacies of internet networking to do any troubleshooting on my own, but I can tell you this:

Verizon DSL -> HA (inaccessible); My IP: 70.17.x.x, IP location: Annapolis, MD
Verizon DSL -> Cox Communications proxy server -> HA (accessible): My IP: 68.104.x.x, IP location: ?

While this proxy is a functional workaround, it's inconvenient to turn it on and off, it's slow, and I have no idea what the security is like.

Is this a Verizon problem or a HA problem? What can I do about it? I wonder how many other people are having this problem as well.

Please let me know if I can provide any other useful information about my connection. Thanks.

[Sebastian Mares]

I use to have problems with T-Com Germany and the IP address 80.*.*.*. 217.*.*.* and 84.*.*.* work flawlessly, however.

[CiTay]

Verizon DSL -> HA (inaccessible); My IP: 70.17.x.x, IP location: Annapolis, MD
Verizon DSL -> Cox Communications proxy server -> HA (accessible): My IP: 68.104.x.x, IP location: ?

While this proxy is a functional workaround, it's inconvenient to turn it on and off, it's slow, and I have no idea what the security is like.

Is this a Verizon problem or a HA problem?

Maybe it's really some router before HA that's rejecting packets from those addresses, no idea. But all i can do is check the banlists and it's not in there.

I use to have problems with T-Com Germany and the IP address 80.*.*.*

Would be good to know the second numbers as well.