Nagarjuna,
I suspect the problem could be due to DNS lookups. But the server in question runs a local DNS, so at least local logins should be allowed. It was not allowing logins even from the console.
Was it still possible to switch the virtual consoles? Could you see what you type on the console? Was it possible to connect to the network servers, but there was no response (looks like: $ telnet gangmail 22 Trying 192.168.0.1... Connected to gangmail. Escape character is '^]'. ...but then nothing more shows up?)
Any clues would be welcome!
We need to know if the kernel really got stuck or not. Does the machine send syslog datagrams to somewhere else over the network? If we find out what happened, it could very well turn out to be a security problem, too.
Thanks in advance!
Nagarjuna
A kernel upgrade isn't a mistake in the first place, but is it a modem or a leased line? Viele Grüße, Roman. -- _ _ | Roman Drahtmüller "The best way to pay for a | CC University of Freiburg lovely moment is to enjoy it." | email: draht@uni-freiburg.de - Richard Bach | - -