Ldap search capabality attribute search failed on server

Small network (50 users), 2 DCs(both are Global Catalog servers), single office.
Symptoms:
First symtom was a couple weeks ago, our Exchange server stopped responding to email.  I logged in and noticed some 5719 errors, and also noticed that the mapped file share couldn't be accessed from the Exchange server.  I restarted the server and all was back to normal.

Fast forward to last week.  I created some new distribution lists on the Exchange 2010 server using the EMC.  Once created, I couldn't send email to them, and got an error that the email address did not exist.  I also created a test USER in Exchange, which was created fine, and I could see the user in ADUC, but when I clicked on "Member Of" tab, I got an error saying that the membership information could not be found in the global catalog, which led me to check the DCs.

DC2 checks out fine when running dcdiag.

DC1 gives me the following error when running dcdiag, right off the bat:
Ldap search capabality attribute search failed on server.  Error -81

Please help!
tenoverAsked:
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.

tenoverAuthor Commented:
Update:
On DC1, if I try and map a drive to another server using name OR IP address, I get the following error:
"The name limit for the local computer network adapter card was exceeded"
0
tenoverAuthor Commented:
Hmmm.....Looks like this may be the TCP offload issue.  I will upgrade the DC to SP2, which includes the hotfix and see if it happens again.
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:
Are your NIC teamed, if yes then this could be one of the cause. Ensure that tcp ofload are disable correctly.http://support.microsoft.com/kb/951037

Checked that dns is set correctly as this
Best practices for DNS client settings on DC and domain members.
http://abhijitw.wordpress.com/2012/03/03/best-practices-for-dns-client-settings-on-domain-controller/
0
tenoverAuthor Commented:
Figured it out myself.
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.

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.