DHCP randomly is getting unauthorized

We have sites all over the globe and AD/DNS 2008 R2 servers all over the globe too.  Today several of our 2003 member servers lost DHCP authorization.  At the local 2003 server, the error is that it cannot contact directory services.  Yet all tests come back OK.  To add to the mystery, DHCP servers elsewhere show that these servers are, in fact, authorized.

I swear it is a network timeout issue but how can I prove this?  What tools can I use to dig deep into AD to check this out.

Any help would be great.  Thanks.
LVL 1
stowyoAmericas Regional IT ManagerAsked:
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.

AnuroopsunddCommented:
Deauthorize of DHCP is mostly due to unable to contact Domain controllers.

you can setup performance counters, provide Event logs (Event Viewer) to network team..

below link have more information about the event id and setting up counters for monitoring and performance..
Hope this helps..

http://www.tech-faq.com/monitoring-and-troubleshooting-the-dhcp-server.html
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
WORKS2011Austin Tech CompanyCommented:
agree it's network, the probability of two or more 2003 DHCP servers changing state to unauthorized at the same time is close to zero.

you could do a simple ping test between servers, run "ping -t ip address" to keep the connection open. You may find the time increasing from 10ms, 12ms, 25ms until it eventually times out.
0
stowyoAmericas Regional IT ManagerAuthor Commented:
Thank you.  The problem ended up being a Virus on the local LAN at the remote site across the WAN.  This site did not have a DC.  The virus was flooding the WAN link with DNS requests.  You both led me to the solution.
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
DNS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.