sounds more like a WindowsXP exploit to me…

Ah. The blame game again.

If it’s accurate, I don’t see how that could be anything but a network auth issue. Kerberos (to take an example and assuming it’s configured properly) won’t allow you to use any services if you can’t authenticate with each server providing the service. You can’t get the initial auth tickets if you never provided the correct password in the beginning. So Kerberos, short of bugs or some other failure, would not have this problem no matter what the client did… a….

OK, I take that back partially. If the client is compromised with inside information from the server (ie, a server breach happened already, possibly due to leaked information from insiders), then that client can compromise the system as described if so programmed. Essentially, this means whoever compromised the client knows the admin passwords (or whatever info is needed) so that the client at login can work on your behalf to pull off this “trick”.

Of course, the method described can’t happen if the auth server info is secure no matter what a rogue client does.. unless the protocol or the implementation are faulty, which is, I think, what is being suggested is the case here for Netware.