[NTLUG:Discuss] no route to host and ...
George E. Lass
George.Lass at osc.com
Mon Jul 17 13:22:12 CDT 2000
> > 3. connection closed by foreign host.
>
> This message is presumably from telnet? Couple of reasons:
>
> 1) Telnet usually displays this after you log out of the remote session.
> If this is the case, this is expected and not an error.
>
> 2) If, on the other hand, you're getting this message before you get a
> chance to log on to the remote session, then the remote machine is most
> likely configured to prevent you from logging on from your source
> address. (Note for the interested: I don't think the Linux firewalling
> code will generate such a message; this is usually a result of using
> the tcp_wrapper package.)
>
I have been fighting a problem lately that might shed some light on your
"connection closed..." problem. I have a Linux PC at home that I use to
dial up my Linux PC at work via PPP. Every once in a while I have
problems
trying to telnet from my home PC to my work PC, even though the PPP
connection
is up and running just fine! Last night I had just such a problem, and
when
I got to work this morning, the first thing I tried to do is check
/var/log/messages & /var/log/secure in order to see what was going on.
Much to my suprise, both files were empty! I then determined that
syslogd
was no longer running on my work PC. Don't know why, but after
re-starting
syslogd I was able to telnet just fine.
Hope this helps,
George
P.S. If anyone knows why telnet didn't work when syslogd wasn't running
please let me know.
G
More information about the Discuss
mailing list