Quote:
Originally Posted by spuggy
No virtual web server can respond appropriately if you simply hit it via the IP address, as they need the name of the site encoded in the URL in order to decide what content to serve.
|
This is true. Although I can hit it using IP address from my network. (comcast)
Quote:
Originally Posted by spuggy
The traceroute output doesn't show that he can't hit it with a web browser; what it demonstrates that network hops after a certain point are having ICMP (either requests or replies) filtered, or a router is choosing to drop packets with the ICMP_TIME_EXCEEDED flag set. Very common across network boundaries.
|
This is also correct. However, i can tracert to the server and the OP cannot. Since he is the one having the problem that is a good indicator that something is being blocked/filtered or there's some routing issue.
Quote:
Originally Posted by spuggy
Also, ICMP != TCP. So a failure to get an ICMP response from an IP tells you zip about the state of TCP connections you may (or may not) be able to establish to that same IP or port - the only way is to try to connect using the appropriate protocol and/or ports - eg TCP/80 or TCP/443.
For example:
Broadly speaking, "connected" means you can reach it fine via TCP; any error after that is either a server-side configuration issue or a problem with the URL you provided.
A firewall filtering connections most often just times out w/ no handshake.
"connection refused" means a TCP reset was issued; usually means nothing listening on that port at the far end (so issued by the hosts' TCP stack), although sometimes a firewall is configured to reset instead of just quietly dropping packet(s).
|
All of this is also correct. However, when the OP tries connecting he gets a server timeout error.
Looking at OP tracert output, his trace route is getting bounced around Zayo network.
OP - try visiting
http://69.63.128.6 (I got lucky) and
https://www.woodmenlife.org. If you have the same problem with these websites then that's a pretty good indicator there's a routing issue to that network. Then you can tell COX that you cannot access any websites in the range 69.63.128.0/19.