Event ID 1097 Windows cannot find the machine account. The Local security Authority cannot be contacted.

I have a 2003 multihomed server. It is also a 2nd DNS backup server.  Every week or so I receive an Event ID 1097: Windows cannot find the machine account. The Local security Authority cannot be contacted.  in the event log.  I have to use the netdom resetpwd command and reset the account pw for the dc , then reboot in order for the server to come back up without errors.  The time is correct on all 4 DC in the domain.  Net logon is started on all 4 DC.  All 4 dc have 2 nic cards for access to the 2 networks and FSMO roles. When the error occurs the applications on the server are not accessible for users.  Does anyone know what I can check in order to keep this DC on the network?
amullee44Asked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
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.

NJComputerNetworksCommented:
Active Directory communication fails on multihomed domain controllers
http://support.microsoft.com/kb/q272294

http://support.microsoft.com/?kbid=191611


I usually try, at all costs, to avoid multihoming my DC's..

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
amullee44Author Commented:
I've been fighting the browse issue for multi-homed dc for some time now.  But budgetary contraints have let to adjusting the IsDomainMaster to No on all DC except the pdc emulator.  The article #272294 , disabling the round robin feature of DNS and readding the entry seemed to do the trick. Also I noticed the Kerberos Key Distrubution service was set to Manual.  I changed that to Automatic, rebooted with the above DNS changes and the machine account has stayed for the past 24 hours.  Thanks again for your help and research.
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
Windows Server 2003

From novice to tech pro — start learning today.