Security EventID 676

Currently the eventlogs on our Win2k SP4 server has a number of security logs in the middle of the night and they are referenceing eventID 676 with the info below.

Authentication Ticket Request Failed:
       User Name:      barbara
       Supplied Realm Name:      FNBHAYS.COM
       Service Name:      krbtgt/FNBHAYS.COM
       Ticket Options:      0x40810010
       Failure Code:      0x12
       Client Address:      172.16.1.210

The usernames vary and sometimes are blank. Logins are disable from 7pm to 7am and there is nobody present on-site etc.

Any insight would be appreciated on what may be happening
nextech01Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

tonyteriCommented:
Sometimes a logon fails not because of a bad password but because the user mistyped the username or tried to guess someone else's username.
If a logon fails because of an invalid username, Windows 2000 logs event ID 676 (authentication ticket request failed) with Failure Code 6. This event is another important logon auditing advance because in NT you can't distinguish logons that failed because of a bad password from logons that failed because of a bad username. Windows 2000 uses event ID 676 with other failure codes to identify several other types of failed-logon situations.

Failure Code 12 indicates the logon failed because of time-of-day or workstation restrictions. Failure Code 18 signifies that the account was locked out because of failed logons, disabled by the administrator, or expired.
Failure Code 23 means the user's password had expired.
Failure Code 37 occurs when a workstation's clock was too far out of synchronization with the DC's clock.

See Audit Account Logon Events for more details.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
nextech01Author Commented:
I would agree that  it is a failed user logon but when this is happening there is no one on-site because it happens in the middle of the night a lot of times, I have included another bit from one of the logged events;

Service Ticket Request Failed:
       User Name:      FNBPDC$
       User Domain:      FNBHAYS.COM
       Service Name:      krbtgt/FNBHAYS.COM
       Ticket Options:      0x2
       Failure Code:      0x20
       Client Address:      127.0.0.1

In this case the server name is FNBHAYS and happened at 5:17am and what is confusing is the username FNBPDC$ which may be a service but it is occuring on this server named FNBPDC.

Thanks
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Security

From novice to tech pro — start learning today.