KSBS Posted November 18, 2016 Posted November 18, 2016 (edited) We have a problem where one user has a bat file set up with the NET USE command to connect to a network drive on another domain (this is going from a Server 2008 domain to a Server 2003 domain) and about once a week (for the last few months) after typing in their password to connect to the drive and then being able to access the drive for an hour or so they try and access a file and get a message saying their account has been locked out, so to resolve this I have to unlock the account in AD and then log into that domain with their account, once I've done this they are then able to access the drive. I've used Microsoft's lockout status tool and it shows 5 incorrect pw attempts even though they are not re-running the bat file and having looked at the event logs on the DC it only points to the computer that they are attempting to connect to the drive from as the source of the Failed Audit. The logs also showed that 11 attempts were made in the same second to log in, after 5 attempts it was locked out and the error codes went from displaying as 529 & 680 to 539 & 680 Edited November 18, 2016 by KSBS
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now