Connecting to same public IP from different locations yields different results

Posted by DHall on Super User See other posts from Super User or by DHall
Published on 2012-06-28T14:32:07Z Indexed on 2012/06/28 15:18 UTC
Read the original article Hit count: 238

Filed under:
|

Since yesterday I've been unable to access one of my favorite time-wasting sites, boston.com. It starts to load but then it gets redirected to pagesinxt or something like that.

After some investigation, I've narrowed it down to an issue with cache.boston.com, but only from my work location. I found the IP (216.38.160.107) , but even that doesn't work correctly from here at work.

When I do a

telnet 216.38.160.107 80

GET http://cache.boston.com/universal/css/hp_bgcom.css

from another location, I get a nice long CSS, as expected.

From here, I get an error (trimmed for size):

HTTP/1.1 400 Bad Request
Your request could not be processed. Request could not be handled
This could be caused by a misconfiguration, or possibly a malformed request.
For assistance, contact your network support team.

Is there any way I can troubleshoot this further on my end? Tracert doesn't tell me anything too useful:

Tracing route to vwrpx1.ttn.xpc-mii.net [216.38.160.107]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.

Since it's not really work-related, I don't really want to bring it up to our network team unless I know what's going on, or if there's some risk to the network (ex. malware or something)

© Super User or respective owner

Related posts about networking

Related posts about ip