Mon, 3 Jun 2002 15:15:56 -0400
|
On Mon, 03 Jun 2002 12:11:45 PDT, Randy Klumph <[log in to unmask]> said:
> That was what I thought with the first error I received but when I received
> errors from 11 different listserv@domain addresses I thought it might be a
> problem at my Listserv. Thanks
If you get "connection timed out" errors all over the place talking to the
outside world, but you are still able to connect to the machine locally
via SSH (you *are* using SSH instead of telnet, right? ;), this usually means
that your entire site has fallen off the Internet (often because your
off-campus link has fallen over or suffered a backhoe attack or similar).
If you get lots of "unable to resolve hostname" errors, see above, and also
include "your local nameserver has died" in the symptom list.
--
Valdis Kletnieks
Computer Systems Senior Engineer
Virginia Tech
|
|
|