Tom,
it seems you uncovered a problem. When I try what you suggest I get
this: I changed things as far as the machine name but I used the Fully
Qualified name.

 telnet webserver.fqdn.org 80
Trying xxx.xx.xx.99...
telnet: connect to address xxx.xx.xx.99: No route to host
telnet: Unable to connect to remote host: No route to host

So to make sure things are correct I did the same thing to a Web Server
on a different machine on the same network and got this:

# telnet different.webserver.org 80
Trying xxx.xx.xx.110...
Connected to different.webserver.org (xxx.xx.xx.110).
Escape character is '^]'.
bye
Connection closed by foreign host.

I did this from the same host on the same network.  So something is
whacky on the routes.




>>> Tom Limoncelli <[email protected]> 1/12/2011 2:09 PM >>>
Generally when I see "Host Unreachable" I think it is a routing
problem or (if they are on the same LAN segment) a broken cable /
disabled interface.

If the system works by hijacking port 80, then ping and traceroute
can't really help you.  However, you can at least connect to port 80
via telnet.  Type "GET /" and press RETURN twice:

$ telnet whatexit.org 80
Trying 2607:f2f8:a9c0::2...
Connected to whatexit.org.
Escape character is '^]'.
GET /
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
...
...
...

Tom
_______________________________________________
Tech mailing list
[email protected]
https://lists.lopsa.org/cgi-bin/mailman/listinfo/tech
This list provided by the League of Professional System Administrators
 http://lopsa.org/

Reply via email to