[Gator]

I have been unable to connect with THR, and a couple other forums, from home. I get a message that says "unable to connect with the server at.......". (I'm sneaking in this post from work).

I have deleted cookies, cleared the cache, and checked my firewall and anti-virus programs....any other suggestions?

[Henry Bowman]

format c:\

[scout26]

Gator,

As much fun as Mr. Bowman's suggestion might sound like, I wouldn't try it. :rolleyes:

I'm having the same problem at home. Which I posted about in the Tech Help forum. (No replies to date.) I'm on SBC/Yahoo DSL. I can get on NRA, Gunsamerica, TFL, Gunbroker, ISRA.org, AR15.com etc. But not THR nor APS. I've reset connections, cleared my cache, etc, etc, etc, etc, and still no THR.

Let me know if you figure it out and if I stumble accross something that works, I'll let you know.

[Gator]

Will do, Scout26. Sounds like we are in the same area, I'm in the SW burbs of "Crook" Co. I also have SBC/Yahoo DSL.

Mods: Sorry for posting in the wrong forum, thanks for moving it.

[Derek Zeanah]

Try it again this evening. PM me if you're still having problems.

[hrb02]

Take a really big magnet and run it around the entire outside of your PC. That should clear out the gunk.:evil:

[Gator]

Would a 36 watt electromagnet work? :what:

----------------------------------------------------

Thanks Derek, I'll try this evening.

[kirby]

I know, I know it's likely not the fault of the THR's hosting. But just in case...


Here's a traceroute from home (not THR from there)
1 192.168.1.1 (192.168.1.1) 0.635 ms 0.585 ms 0.628 ms
2 192.168.0.1 (192.168.0.1) 1.086 ms 1.092 ms 1.058 ms
3 adsl-75-6-255-254.dsl.pltn13.sbcglobal.net (75.6.255.254) 8.847 ms 9.561 ms 9.093 ms
4 dist1-vlan60.pltn13.pbi.net (64.164.97.130) 9.118 ms 9.469 ms 9.095 ms
5 bb1-g3-0.pltnca.sbcglobal.net (151.164.43.54) 9.861 ms 11.119 ms 9.979 ms
6 bb1-p4-0.crsfca.sbcglobal.net (151.164.41.5) 11.349 ms 15.004 ms 11.055 ms
7 ex1-p14-0.eqsjca.sbcglobal.net (151.164.41.10) 12.061 ms 12.732 ms 11.844 ms
8 ge-6-13.car4.SanJose1.Level3.net (151.164.250.181) 11.314 ms 12.532 ms 12.536 ms
9 ae-32-56.ebr2.SanJose1.Level3.net (4.68.123.190) 22.173 ms ae-31-53.ebr1.SanJose1.Level3.net (4.68.123.94) 20.289 ms ae-31-51.ebr1.SanJose1.Level3.net (4.68.123.30) 18.549 ms
10 ae-1.ebr1.SanJose1.Level3.net (4.69.132.1) 23.408 ms ae-2.ebr1.LosAngeles1.Level3.net (4.69.132.10) 23.019 ms ae-1.ebr1.SanJose1.Level3.net (4.69.132.1) 28.764 ms
11 ae-1.ebr2.LosAngeles1.Level3.net (4.69.132.6) 23.098 ms 22.299 ms 37.398 ms
12 ae-3.ebr2.Dallas1.Level3.net (4.69.132.78) 58.284 ms ae-1.ebr2.LosAngeles1.Level3.net (4.69.132.6) 39.766 ms ae-3.ebr2.Dallas1.Level3.net (4.69.132.78) 57.358 ms
13 ae-1.ebr1.Dallas1.Level3.net (4.69.132.45) 61.753 ms 59.937 ms ae-3.ebr2.Dallas1.Level3.net (4.69.132.78) 69.240 ms
14 ae-3.ebr1.Atlanta2.Level3.net (4.69.132.82) 82.217 ms 78.649 ms ae-1.ebr1.Dallas1.Level3.net (4.69.132.45) 69.446 ms
15 ae-12-55.car2.Atlanta1.Level3.net (4.68.103.131) 78.432 ms ae-12-51.car2.Atlanta1.Level3.net (4.68.103.3) 80.595 ms ae-12-53.car2.Atlanta1.Level3.net (4.68.103.67) 78.121 ms
16 4.78.210.6 (4.78.210.6) 71.831 ms 72.308 ms ae-12-53.car2.Atlanta1.Level3.net (4.68.103.67) 78.149 ms
17 209.51.149.109 (209.51.149.109) 70.834 ms 71.128 ms 71.438 ms
18 209.51.137.34 (209.51.137.34) 70.406 ms 209.51.149.109
(209.51.149.109) 71.607 ms 209.51.137.34 (209.51.137.34) 69.957 ms
19 * * 209.51.137.34 (209.51.137.34) 71.095 ms
20 * * *


The problem started last weekend (April 1st-ish)

[tyme]

kbyrd, there's nothing helpful in that traceroute. THR doesn't send ICMP port unreachables for unused ports. That's the expected output.

What happens when you do:
nmap -p22,80,443 www.thehighroad.org

All filtered? Web filtered? Just port 80 filtered?

[kirby]

Fine. Didn't now someone in the middle or the host wasn't returning ICMP.


> nmap -p22,80.443 www.thehighroad.org
Note: Host seems down.

I bet that's because it's blocking pings.

> nmap -P0 -p22,80,443 www.thehighroad.org
PORT STATE SERVICE
22/tcp filtered ssh
80/tcp filtered http
443/tcp filtered https


I also did a wider scan (sorry)
> nmap -sS -O -F -P0 -T4 www.thehighroad.org
All 1231 scanned ports on wellbuiltnetworks.net (209.51.144.70) are: filtered

[tyme]

It's not blocking pings for me, nor are those three ports filtered. Either your IP is blocked for some reason at THR, or THR's IP is blocked by your ISP. Or maybe there's a routing problem from THR to your IP... but then I would expect traceroute to die earlier that it did.

[Larry Ashcraft]

I had the same problem a couple years ago. Derek couldn't figure it out and I finally resorted to using anonymizer.com for a couple weeks.

Then, on a whim, I unplugged my DSL box for a couple minutes and plugged it back in. That solved the problem.

[kirby]

See, the traceroute was useful :D

It tells me that either there's a routing problem close to wellbuiltnetworks, or that something close to wellbuiltnetwork/THR isn't responding to the ICMP that traceroute uses.

I agrees that it's likely that my IP or netblock is blocked or THR's IP or netblock is blocked. I'm using SBC Yahoo DSL and I didn't know they blocked things. Could they admins see if I'm blocked? My IP is either in the traceroute.

[tyme]

Can you get to www.wellbuiltnetworks.net and www.wellbuiltnetworks.com? They're in the same /24... In addition, I think .net is the same physical box as THR and APS, just a different IP.

That should narrow it down some.

If you have a dynamic ip, try Larry's solution. You may get a new IP and it may solve things.

[kirby]

I can get to wellbuiltnetworks.com, but not wellbuiltnetworks.net
I got a new dynamic IP (now 75.7.15.254), that didn't help.

[Gator]

I was able get to www.wellbuiltnetworks.net and www.wellbuiltnetworks.com, but not THR.

I just installed The Anonymizer and am able to get THR! But it's only a seven day trial. I previously re-booted my DSL modem but that didn't help.

If The Anonymizer works, does that mean that somewhere my ISP is getting blocked?

[Tim Burke]

I've been having the same problem intermittently since the beginning of March. When my dynamic IP is 74.227.xxx.xxx I can't access THR, and my trace route hangs up at exactly the same point that kbyrd's does, one step before the connection to THR. Sometimes my dynamic IP will randomly be assigned in the 66.21.xxx.xxx range, and I can connect. Plugging and unplugging the DSL will result in an IP change, but if it doesn't change the the range from 74.x.x.x to 66.x.x.x it doesn't change whether or not I can connect.
Using an online anonymizer allows me to get in even when my IP is in the 74.227.xxx.xxx range. It seems almost as if certain IPs are being blocked.

[kirby]

- First: The traceroute crapping out is normal. Some boxes/routers don't respond to ICMP.

- Second: With Anonymizer, your IP from THR's point of view isn't your actual IP, it's the IP of the node you're pop out of the anonymizing cloud from.

- Third: Try 'tor' instead of Anonymizer. It's free (speech & beer). Works great if you don't mind bouncing around Europe.

- Forth: It's seems kinda clear to me that THR is blocking some IPs in the 74/75.x.x.x range. I'm curious to see who Tim Burke's ISP is and what the subnet is. I'm from SBC Yahoo DSL. Mayber THR is using a black list that our ISP ended up on.

[tyme]

Hmm... are those ex-bogon netblocks? If so, they might be filtered by THR or by the routers of whatever colo Derek uses.

[Tim Burke]

The traceroute crapping out is normal. Some boxes/routers don't respond to ICMP. Normal, or not unusual? When I have a 66.x.x.x IP my traceroute runs all the way to 209.51.144.70. When I have a 74.x.x.x IP it hangs at the same point yours does. However, if I do a web based traceroute it will run to 209.51.144.70 regardless of my IP. Of course, that traceroute doesn't originate from my IP.
I'm curious to see who Tim Burke's ISP is and what the subnet is. I'm from SBC Yahoo DSL. Mayber THR is using a black list that our ISP ended up on.I'm on a BellSouth DSL connection out of Charlotte.Hmm... are those ex-bogon netblocks?Huh? What's that in English?

[kirby]

Tyme claimed that THR doesn't return ICMP for unused ports. That's why I thought it was normal. Apparently, that's not true. If some traceroutes get thru, then the traceroute narrows the problem down pretty well, right? Also, doesn't it seem to indicate the IP address blocking isn't at my end because even though it's showing each hop, the destination is still the THR IP? If it was blocked by my ISP wouldn't we see traceroute choke earlier?

I don't know if 66.x.x.x and 67.x.x.x are formerly bogus (ex-bogon) addresses. They aren't now. Is there anyone in a position to check?

[BamBam-31]

Most, if not all, of this technical jargon's way over my head, but I haven't been able to log onto THR, either. I'm on SBC Yahoo DLS also, FWIW. :(

[tyme]

Tyme claimed that THR doesn't return ICMP for unused ports.
After trying a few more web-based traceroutes, it seems that a small percentage of sites can get a complete traceroute. I can't, from any machine I have access to, but I can get to both THR and APS websites with no problem. So even if the last-hop-missing traceroute represents some sort of issue, it isn't clearly related to web access.

I think maybe sites that work are using tcp traceroutes.

[Tim Burke]

If you go to this site (http://projectip.com/) it will tell you from what IP it thinks you are originating. I wouldn't be surprised if it is 75.x.x.x.

[Gator]

Yeah, my IP starts with either a "74" or "75", usually it's a "75".

Using Anomyizer works, but not well. I can't see a lot pics and can only read the posts on the first page.

My provider says my DSL line is just fine and could offer no help. Of course they told me this after almost two hours on the phone with an Indian woman I could hardly understand!

[Gator]

Well, I don't know what happened but the problem has disappeared :)

[kirby]

I forgot to update this thread, but I got an email from Derek Z stating he would look into the problem, but could not get to it until Monday, today. I won't be able to test from home until tonight.

[Top_Notch]

I too am blocked from Home. I get the page like the server doesn't exist. I've gone through all my browser settings and haven't found anything to fix it. I'm in Suburban Crook County...and I think it's a conspiracy!

I'll try the 'anomyizer' website from home to see if I can surf THR from home.

Open to any other suggestions?

(I'm posting this from work in Kane Cty) :scrutiny:

[Gator]

I posted too soon....I must have been temporarily assigned an IP that started with something other than the usual "74" or "75" for that session. So I'm blocked again and am back to using a proxy server (http://proxymod.com/).....bummer!

[Derek Zeanah]

Finally have my head above water for a bit. Will pass this on to my colo facility and see what they can find out...

[popeye]

About a month to 6 weeks ago SBC had a DSL major failure in Illinois and N.W. Indiana. Since then I can't log onto THR without using a proxey like Anonymouse.org. Since I use a cheapo DHCP ADSL hookup I seem to be screwed. Reseting my modem always asigns me an I.P. with the first octet as 75.

[scout26]

WOO HOO !!! I'm back !!! After jonesing THR-less for three weeks, Derek and Oleg have worked their black magic and I can finally get my THR fix.

Thanks you so very much gentlemen. I really missed this place. :o

[Derek Zeanah]

Nothing changed on this end. My changes are waiting until later this week.

Glad you're back, tho.

[kirby]

So there IS a solution in the works?

[kirby]

Still no THR love at home for me (as of 4/30/06).

[Derek Zeanah]

Patience, dear Byrd. Hopefully this week -- just need to find the time to make a day trip...

[Barbara]

I've been having the same problem, also with DSL.

[sm]

Derek,

You know this stuff, I'm the guy just trying to NOT sweat bullets for Cisco Exams and Practicals .

-I know with some mergers locally folks were having connection problems they did not have. Routers config-ed wrong. [I can do that already :p ] Once config-ed correctly, Routing Protocols ,ACLs...done, good to go.

-Some Routers,Switches, had viruii...upset let go folks getting one last dig in...

-Personally I could not access a homepage for instructor, been griping, as have others, seems I accidently hit on the troubleshoot. New version coming out , so the new server w/ > bandwith, + a Layer 1 problem.
Derek understands, for the rest deals with outside coming inside, and distance...bad case of attenuation. Landscape work screwed the pooch. [proper tech term] add cabling guys did not adhere to standards. [no plenium in crawl space for instance.

FWIW I get "slow" sometimes here on THR and other sites, whether I use Cable, DSL, College 100Mbs or home dial up ISP.

One of them / some hops not config-ed right my guess. With merger of some phone companies and such, add disgruntled let go employees.

Gotta go get more brain dead now...

Right now, 52Kbps using dial up from home, THR is faster loading now than earlier today from College at 100Mbps.

I know where one hop is in town...and I know why it screws up, been bought out and one "former employee" left a little something to remember him by. I know the person that found and fixed it.

Pass the Tylenol...

[Larry Ashcraft]

I've been having the same problem, also with DSL.
Barbara, try my solution, unplug the power to the DSL modem, let it sit for a couple minutes, plug it back in.

I'm about as computer illiterate as they come, but it works for me.

[Barbara]

Yep, tried that, but no dice. I can only get here through an anonymiser. Tried both Mozilla and IE and can't get here. Sounds like its some kind of incompatibility with SBC DSL?

[tyme]

Chances are that Derek's hosting provider is blocking 75.x.x.x. It was only recently allocated. It might also be blocking other formerly-reserved networks. (Or maybe the THR server itself has those netblocks firewalled, but I really doubt it.)

Derek, do you really have to drive there to resolve this?

[Derek Zeanah]

Derek, do you really have to drive there to resolve this?It'd be nice to. Things to do while there include: Double the memory
Disable the software firewall (it could be that, though I also doubt it)
Throw an OpenBSD machine in front of the server to act as the new firewall.Once on-site I'll get a chance to talk with the technical folks and verify that the 75. netblocks are actually accessible -- my colo provider's response is "we don't block any IPs," but I can't get a clear answer on whether newly available blocks are routed properly. The tech staff on-site rock, though -- I'm just technically not their client so I'll need to be onsite to start the conversation...

[scout26]

Derek,

According to SBC, THR and APS have 75.xx.xx blocked. That's why everyone (including me) with SBC DSL can't get in.

[kirby]

I wonder how SBC knows what THR is blocking? I mean, they can guess. But how would they "know"?

[cosine]

Derek,

According to SBC, THR and APS have 75.xx.xx blocked. That's why everyone (including me) with SBC DSL can't get in.

It must be a regional thing though. I have SBC DSL up here near Milwaukee, IP 69.xx.xx, and have no problem accessing THR.

[Barbara]

Today I can get here. Yay me!

[Spot77]

Sorry to hear about your cases of withdrawl. I thought I had it bad when THR stopped sending me new post notifications.


But now for some reason after over a year of not getting them, they're working again.

How cool!

[kirby]

I'm able to access from home as well. Just to be sure, I checked my public IP: 75.7.4.150.

Thanks to Derek. What was the story?

[John Rogers]

Hooray! It has been weeks since I could log in, I am also on SBC with a 75.* IP address. Thanks so much to Derek for working to resolve the problem!

John

[tyme]

I wonder how SBC knows what THR is blocking? I mean, they can guess. But how would they "know"?
I'm sure the SBC techs have access to test machines on every major SBC IP block.

[popeye]

I can get straight to THR without proxy as of today. 5 WEEKS NO THR.

[Tim Burke]

Something has clearly changed. Direct connection today from 74.x.x.x.
Thanks to Oleg & Derek for the help.

[Gator]

Hey it works! Thanks Derek!

[popeye]

05/15/2006 CST 2019 hrs. no more THR except through proxy. Again.

[Gator]

Yep, same here :(

It was nice while it lasted.........

[Derek Zeanah]

It seems to be a firewall issue. You should be able to get in, now.

[popeye]

YEP! 05/16/2006 0503 CST I'm in w/o proxy EVERYTHING back to normal. Thanks Derek!

[popeye]

BTW: I checked the firewall in my pickup truck, so it ain't on my end.