Question : Massive Account Lockouts

I have read the other posts pertaining to account lockouts, and have not been able to resolve my current problem in my network. It's a fairly small network- 6 Servers(2003 server and 2000 server) (2 DCs) and 20 workstations(2000 and XP). We recently migrated our secondary WINS server to another server and stop and disabled the service on the previous secondary server. I made the necessary adjustments on the Primary WINS server to point to the new Secondary WINS server and visa versa. Everything seems to be fine with replication between partners, and I can see the the netbios names it resolves. Ever since I migrated the secondary WINS server to the new server, we have been getting account lockouts all over the place.

I will go into AD USers and Computers and see that evry single account is locked account (yes- even the administrator account) and then I have to unlock all of them. A few minutes later, I see that they are ALL locked out again. A user brought it to my attention when it happened and I went to their computer and saw a box pop up asking for a Login name, password, and domain name. They had Outlook open while this happened as well. Then on another user's computer (while their account was locked out, but the user was currently logged in), when they tried to open up Outlook, it asked them for Login name, password and domain name. The accounts keep locking out- and there is NO policy making them do this. The only policy is to unlock after 3 failed attempts, and then to reset after 30 mins. We did not have this problem before the migration.

Recently I configured all workstations to static IP's and configured them properly in DNS (this was requested by my supervisor). The lockout problems occured before I set the static IP's on the workstations. Do I still need WINS if I am going static and their host files are set to their static IP and Comp name? Thanks, and please help!!

Answer : Massive Account Lockouts

Actually, WINS is the solution to the LMhosts file.
You either need one or the other in a netbios world for name resolution.
You can still test if WINS is the issue, tho. Build an LMHosts fiel for each machine, with the correct name mapping in place. Then, disable WINS, say over the weekend, and logon with several accounts and see if everything works.
THEN! make the penny-pinching bean counters by a better bean sorter! 8-) THere's probably an update for the program available, but not free.
Good luck!
Random Solutions  
 
programming4us programming4us