Discussion Locked

Intruder Lockout from Server, Netware 4.

0 helpful
2 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
One of my admin equivalent accounts recently had an automatic password change and is constantly being locked out. I checked my backup & virus scan, neither is responsible. The Intruder Lockout address is the main server, but I believe everything that should be running is. I've checked through all the logs & don't see any changes that would have caused this. How can I trace down what service is actually causing the problem?

2 replies

by tomcat-2000

Sounds like you are alrady aware that something (or someone) is locking the account out. I honestly feel that the best way to do this is to create a new admin eq. and delete the old one. This does two things: First, it eliminates the lockout problem, and second it allows you to eventually find out what service it was if it ends up being important, and simply ignoring it if it wasn't.

Eventually you will find something erroring and your answer will be found. We have a hybrid network here with about 250 services throughout the organization and experienced the same problem. We have yet to determine what service it was ... and obviously it wasn't that important.

Good Luck !! Mike Tomasiewicz

by jim_maclachlan

Thanks, but in this case deleting that account isn't possible. I did find the answer by looking at all the .ncf files in my system directory. It turns out that GroupWise WebAccess (strtweb5.ncf) had that password & name in it. It was odd that the service started with an incorrect password & seemed to be working fine. I was on WebAccess last night. I don't understand that, but it's fixed now.

This discussion is closed to new replies.