Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Categories

In this Discussion

› › Site not accessible from home/work, but is elsewhere...eh?
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

Site not accessible from home/work, but is elsewhere...eh?

raindog308raindog308 Administrator, Veteran
edited November 2012 in Help

There's a forum I read on a regular basis. A few days ago, I couldn't read it from home...timed out.

Stayed that way for a while. Asked on another forum and people said "works fine for me". Looked at it from a VPS and sure enough, it works fine.

  • From my home (CenturyLink DSL) using various PCs, iOS devices - timeout.
  • From work (totally different network setup, big company) - timeout.
  • down or just me says it's OK.
  • wget/lynx from VPS in California - OK.
  • iOS device on AT&T 3G - OK

So...what could cause this? When I lookup the DNS it returns the same IP in all places I've tried.

If it was just my home, I'd understand maybe something goofy on my end...but work as well, which is a different network and ~15 miles from me.

The forum is hosted by LiquidWeb. Last bit of traceroute from home:

 8  lw-border6-te1-4.rtr.liquidweb.com (209.59.157.215)  186.832 ms  186.963 ms  187.057 ms
 9  lw-dc2-core4-te9-1.rtr.liquidweb.com (209.59.157.226)  168.678 ms  169.150 ms  169.180 ms
10  lw-dc3-dist8-po6.rtr.liquidweb.com (69.167.128.135)  121.291 ms  123.071 ms  124.743 ms
11  * * *
12  * * *

From a BuyVM VPS:

 7  lw-border6-te1-4.rtr.liquidweb.com (209.59.157.215)  55.647 ms  54.710 ms  54.223 ms
 8  lw-dc2-core4-te9-1.rtr.liquidweb.com (209.59.157.226)  62.829 ms  60.591 ms  60.846 ms
 9  lw-dc3-dist8-po6.rtr.liquidweb.com (69.167.128.135)  65.302 ms  94.118 ms  62.269 ms
10  69.167.176.141 (69.167.176.141)  63.734 ms  62.585 ms  65.22 ms

Comments

  • TazTaz Member

    Wht?

  • juanjuan Member

    try clearing your cache, i had the same problem and did the same solution.

  • VictorVictor Member
    edited November 2012

    @Taz said: Wht?

    No, it's a firearms forums.

    69.167.176.141

  • CiriumCirium Member

    The only thing I can think of is that you were lucky enough to be iptable'd on both your home and work networks although the chances of that happening are probably 0.00000001%.

    Did you have a user account on the site and by chance an administrator decided he didn't like you?

  • kbeeziekbeezie Member
    edited November 2012

    Routes fine from my RootBSD server

    traceroute to 69.167.176.141 (69.167.176.141), 64 hops max, 40 byte packets

    1 199.48.135.97 (199.48.135.97) 0.531 ms 0.439 ms 0.440 ms
    2 204.109.62.109 (204.109.62.109) 0.491 ms 0.605 ms 0.451 ms
    3 204.109.62.105 (204.109.62.105) 0.703 ms 0.537 ms 0.509 ms
    4 66.18.0.57.databank.com (66.18.0.57) 0.640 ms 0.693 ms 0.712 ms
    5 4.28.153.9 (4.28.153.9) 0.675 ms 0.732 ms 0.648 ms
    6 vlan80.csw3.Dallas1.Level3.net (4.69.145.190) 0.810 ms
    vlan90.csw4.Dallas1.Level3.net (4.69.145.254) 1.489 ms 0.803 ms
    7 ae-81-81.ebr1.Dallas1.Level3.net (4.69.151.150) 0.743 ms
    ae-61-61.ebr1.Dallas1.Level3.net (4.69.151.126) 1.139 ms
    ae-91-91.ebr1.Dallas1.Level3.net (4.69.151.162) 1.329 ms
    8 ae-14-14.ebr2.Chicago2.Level3.net (4.69.151.117) 19.957 ms 19.971 ms 19.768 ms
    9 ae-201-3601.edge2.Chicago2.Level3.net (4.69.158.49) 19.847 ms
    ae-202-3602.edge2.Chicago2.Level3.net (4.69.158.53) 19.751 ms
    ae-203-3603.edge2.Chicago2.Level3.net (4.69.158.57) 19.764 ms
    10 CWIE-LLC.edge2.Chicago2.Level3.net (4.59.29.82) 20.134 ms 19.925 ms 20.119 ms
    11 lw-core4-te91.rtr.liquidweb.com (209.59.157.206) 25.252 ms 25.354 ms 25.312 ms
    12 lw-dc3-dist7-po5.rtr.liquidweb.com (69.167.128.129) 25.386 ms 25.759 ms 25.377 ms
    13 69.167.176.141 (69.167.176.141) 25.399 ms 25.710 ms 25.491 ms

    Maybe your ISP is having routing issues.

  • mikhomikho Member, Host Rep

    I had almost the same problem once, couldnt connect to my ipx vps from home.
    Turned out to be blocked by an 'intrusion problem' then.

    A ticket then to ipx let me in.
    Not saying that it is the same with you but it could.

  • WintereiseWintereise Member

    Liquidweb is blocking those ranges, for whatever reasons.

    Your best bet is getting in contact with the forum staff, who can then maybe ask Liquid web.

  • raindog308raindog308 Administrator, Veteran

    I guess I'll have to do that, Wintereise.

    • clearing cache does no good
    • different browers/operating systems makes no difference
    • I'm definitely not banned at the forum (no reason they would, and I can login to it from my phone)
  • WintereiseWintereise Member

    It's a routing issue, @raindog308.

    No need to try client side stuff, straight up contact them =)

  • raindog308raindog308 Administrator, Veteran

    So much for heroic support:

    "Thank you for the information. I can assure you that our network is
    functioning just fine."

Sign In or Register to comment.