Answer to Connection Refused
This is the answer to Connection Refused
Inetd wasn't running. That's what listens for new network connections and spawns off the appropriate daemon. More modern systems use Xinetd, but the concept is the same.
What apparently killed this turned out to be a Linux machine trying to add a network printer located on this box. Tracing back in syslog showed inetd complaining about something that machine was sending just before it stopped working. This is an older (5.0.5) SCO box, and has never been brought up to date with security patches, so I suspect that some accidental buffer overflow killed inetd. This may have been it: Bugtraq: Security Update: [CSSA-2001-SCO.33] OpenServer 5.0.5: nmap port scanner can kill inetd.
Inetd can be restarted with "tcp stop;tcp start".
Got something to add? Send me email.
(OLDER) <- More Stuff -> (NEWER) (NEWEST)
Printer Friendly Version
Increase ad revenue 50-250% with Ezoic