Event ID 5722 in SYstem logs on Windows 2008 R2 domain controller

Hi All

We have a single domain with a number of a 2008 R2 DC's, we also have 1 2003 DC still floating around so we are still at windows 2003 DFL.

On one of my 2008 DC's I am seeing a number of errors for netlogon (pasted below)  I had a quick Google and it implied it was when you have a trust with NT 4 domains which we do not.

The machines referenced in these errors are all Windows 7 Pro in the same domain

Log Name:      System
Source:        NETLOGON
Date:          02/10/2013 06:25:58
Event ID:      5722
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      LONDC01.mydomain.com
Description:
The session setup from the computer LON4INT27 failed to authenticate. The name(s) of the account(s) referenced in the security database is LON4INT27$.  The following error occurred:
Access is denied.



Anyone have any idea why these are happening?

Thanks
LVL 5
ncomperAsked:
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.

unknown_routineCommented:
You have to  update you domain functional level to Windows 2003 native mode(from the mixed mode)
0
becraigCommented:
Try running
Nltest /server:ComputerName /sc_query:DomainName

Based on the fact you indicated these are win7 domain members it is likely the machine account may need to be reset by rejoining the member computer to the domain.

Here is a link to an msn article on this issue:

http://support.microsoft.com/kb/810977
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
SandeshdubeySenior Server EngineerCommented:
The abaove log indicates that secure channel of the cleint computer is broken and you need to rejoin the client computer to domain to fix the same as suggested by becraig.Also ensure correct dns setting on DC and client as this:http://abhijitw.wordpress.com/2012/03/03/best-practices-for-dns-client-settings-on-domain-controller/
0
ncomperAuthor Commented:
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
Active Directory

From novice to tech pro — start learning today.