Why does this happen? (network)

[Sharksfan]

I am in a hotel right now - an Embassy Suites with WiFi.

When I connect to the WiFi most - in fact, the vast majority of sites - work just fine. But my tracking domain and any other domain on LiquidWeb Storm Hosting just time out when I try to go to them in a browser. Itl's also consistent between browsers. WinSCP and even standard "ping" also do not work.

If I RDP into a remote machine and try it everything is fine.

If I pop in my Verizon wireless card everything is fine.

If I do tracert using the hotel's wireless I get the entire route up to Liquid Web - it consistently times out at step 15:

1 38 ms 39 ms 39 ms 12-187-129-1.att-inc.com [12.187.129.1]
2 40 ms 38 ms 39 ms 12.89.169.237
3 64 ms 61 ms 68 ms cr2.dvmco.ip.att.net [12.122.144.130]
4 63 ms 60 ms 60 ms cr2.dlstx.ip.att.net [12.122.31.89]
5 62 ms 61 ms 60 ms ggr3.dlstx.ip.att.net [12.122.138.25]
6 * 65 ms 59 ms 192.205.35.226
7 67 ms 72 ms 71 ms ae-72-70.ebr2.Dallas1.Level3.net [4.69.145.115]
8 87 ms 74 ms 87 ms ae-2-2.ebr1.Denver1.Level3.net [4.69.132.105]
9 79 ms 74 ms 89 ms ae-1-100.ebr2.Denver1.Level3.net [4.69.132.38]
10 79 ms 79 ms 78 ms ae-3-3.ebr1.Chicago2.Level3.net [4.69.132.62]
11 80 ms 79 ms 79 ms ae-1-51.edge2.Chicago2.Level3.net [4.69.138.131]
12 83 ms 80 ms 80 ms GLOBAL-INTE.edge2.Chicago2.Level3.net [4.59.29.7
8]
13 87 ms 86 ms 85 ms lw-core4-te91.rtr.liquidweb.com [209.59.157.206]
14 94 ms 85 ms 86 ms lw-dc3-dist7-po5.rtr.liquidweb.com [69.167.128.1
29]
15 * * * Request timed out.


I sincerely doubt LiquidWeb is the problem - I am on their Storm hosting and it's been solid. It's only using the hotel WiFi that I get problems - but it consistent, and it's always to any domain I am hosting at LW.

I'm baffled - it makes no sense to me.

Thanks in advance -

B.

 

[BigWill]

You can run a trace with a network that it works on and see what it should hit next. That would be where your connectivity problem is. Someone has it blocked though.

 

[subigo]

It's making it to Liquidweb and then dropping. So it's being blocked at their level. Contact them.

 

[jryan21]

Can you connect to other domains using https? Is everything running over standard ports 80, 443?

Try running wireshark and see if you find anything in there that may be causing it.

 

[Sharksfan]

It turns out the hotel IP was being blocked at the firewall for some reason.

I haven't set up any special firewall rules for my server - not sure if the hotel IP(s) is in a bad neighborhood or what the deal is.

 

[Sharksfan]

Further information reveals that at some point the hotel's IP was trying to access my stuff via SSH too many times and locked this IP out.

Might have been me on a previous visit...not sure.