In article <1995Apr19.183902.44164@miavx1>, [log in to unmask] (Bob
Williams) writes:
> I tried to finger someone on another system, but I got the following
> message:
>
> connect: %MULTINET-F-EHOSTUNREACH, No route to host
>
> I get the same thing when I try to telnet there. What does this mean? I
> normally have no trouble.
 
This generally means that the system knows that the host exists, but it's
not able to reach it currently.  A helpful tool in diagnosing this is the
TRACEROUTE command.  This command will show you all of the hops between our
site and the site you're trying to contact.  This can show you where
slowdowns or problems are occurring.  For example, here is the result of
the command: TRACEROUTE WUARCHIVE.WUSTL.EDU
 
    $ traceroute wuarchive.wustl.edu
    traceroute to WUARCHIVE.WUSTL.EDU (128.252.135.4), 30 hops max, 40 byte
    packets
     1  r-uph-culler.muohio.edu (134.53.7.254)  3 ms  2 ms  2 ms
     2  r-rob-bb.muohio.edu (134.53.247.253)  2 ms  5 ms  2 ms
     3  134.53.253.253 (134.53.253.253)  3 ms  2 ms  5 ms
     4  clp1-s1.cincinnati.oar.net (199.18.107.5)  14 ms  9 ms  6 ms
     5  oeb4-s2/2.columbus.oar.net (199.18.105.157)  12 ms  10 ms  12 ms
     6  sl-dc-8-H2/0-5M.sprintlink.net (144.228.28.5)  27 ms  33 ms  29 ms
     7  sl-dc-7-F0.sprintlink.net (144.228.20.7)  37 ms  30 ms  26 ms
     8  sl-starnet-1-S0-T1.sprintlink.net (144.228.27.6)  59 ms  59 ms  51 ms
     9  128.252.41.1 (128.252.41.1)  58 ms  87 ms  55 ms
    10  wuarchive.wustl.edu (128.252.135.4)  48 ms  68 ms  95 ms
    $
 
--
                                     Kent Covert, Software Coordinator
                                     Miami Computing and Information Services
                                     Miami University, Oxford, OH
                                     [log in to unmask]  (internet)
                                     kacovert@miavx1                 (bitnet)