On 09/13/2011 02:28 PM, Bryan Burke wrote:
...with zero successful connections to that IP. The connectivity failure is
entirely reproducible by hand:
% telnet 88.198.67.125 80
Trying 88.198.67.125...
telnet: connect to address 88.198.67.125: Connection refused
telnet: Unable to connect to remote host
I should say that when I did this, I got the same, but the connection seemed to
be timing
out, not being refused (despite what telnet says). Was it the same for you?
I ask because that would indicate either that the web server on that IP is
down, or that
some firewall is silently dropping packets.
This is a good question. I had a problem with my ISP in that I could not
access my work servers from home. My ISP stated that they were not
filtering my work IPs and a traceroute seemed to confirm this. It seemed
that some router along the way determined it did not like traffic with
my originating IP and my office's terminating IP. Like many users, my
IP address is not static but .... very rarely changes. Forcing an IP
address change (method more OT then the rest of my post) from my ISP
made all the traffic get through. I bring this up only because the
symptoms are similar, some traffic like ICMP would make it fine while
other traffic like HTTP and SSH were being blocked along the route.
--
Jim Preston
jimli...@commspeed.net
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://www.clamav.net/support/ml
