General Consultant Discussion

This one has my local network boys stumped. Started getting this message about three weeks ago. Happens on all my workstations attached to the network. At first it was slightly annoying, now it is very annoying. I have not changed my PW recently, I am unaware of any changes to the network recently (except MSFT updates). If I keep entering my password, it eventually allows me to log onto the network. I am not YET having those senior moments (although I have managed to forget my ATM pin recently). I can log onto my laptop with ease if it is not attached to the network. The lockout duration is 10 minutes and lockout threshold is 50 attempts.. I wonder if my user account has become corrupted. The other user of the system does not have these issues. TIA for any thoughts.

You should have something in the event log. Do you see a Security ID of null in the event log?

You may be able to disable and re-enable the account or domain account.

Also might try running GPUPDATE /FORCE at a command prompt. Slight chance it will correct the issue - but easy to do and many times chases out gremlins.

@ScottHickman - Looks like I will start with the easy one first and run the gpudate /force. Will keep my fingers crossed...

Well, the gpupdate did not work. Ran it, confirmed that it updated successfully, rebooted the workstation, kept getting the message for five minutes before I was able to log in.....

Yeah - multiple workstations made that a long shot. You came off of SBS, right? Do you know how they migrated you off? Did you migrate the domain? Did you setup a new domain? Was it 2003 or 2008?

Do you have two domain controllers? If so, it sounds like they're not replicating correctly. If you go to a command line and type 'set log' is should show you the name of the domain controller that's authenticating your password.

My other thought was that your Primary DNS server is not assigned correctly. You can check that with an IPCONFIG / ALL and look for ""DNS Servers

Hey Steve - they virtualized his SBS server in 2013. Just FYI. He thought they ""shut down"" active directory as well. He is going to discuss the potential of multiple DCs with his IT group. It is working on his laptop when remote - so it appears to at least cache it correctly locally. DNS might be a culprit where it could sometimes time out and use the local GP cache.

@SteveIwanowski - Thanks for the thoughts. What is bizarre is that server has been running since early 2013 and this is the first issue since that time. I did virtualize my old 2003 SBS server as I was still running programs on it that I didn't want to reinstall. I just checked and two DNS servers do appear. So I will follow that thought into the rabbit hole.

@jeff Schwenk DNS should be the server that houses your Active Directory Domain Controller.

Is there a second DC present? And do those DNS Server entries match the IPs of both DCs?

NOT supposed to be. Might be the original 2003 SBS that was virtualized but everything like this was supposed to have been deactivated in 1/2013... On my list for the IT guy to check.

Not sure if your IT guy has waded through this, but here is a lenghty threas on your issue. https://social.technet.microsoft.com/Forums/office/en-US/f8304099-d0bd-43dd-b0ec-6dfb4362ff44/the-referenced-account-is-currently-locked-out-and-may-not-be-logged-on-to?forum=w7itprosecurity

Finally got it resolved (fingers crossed) Ran through all the suggestions, changed the security lockout to zero which seems to be the solution, though I would like to know why. May be time to decommission the virtual sbs 2003 volume. The reasons for it 30 month ago no longer are present. Time for a new version of QB. Once I get that, time to move into the current decade.

QB?????

Oops, did I say QB??? Yep, the Non Profit that I am treasurer of only had $40 in the budget for QB at TechSoup.org website. I didn't feel like donating a license though I may need it for tier one of these days.....

Decommissioning the 2003 SBS in the next couple of weeks. Good bye old friend.