2008 R2 Member Server and 2003 DC - Netlogon 5719 and 5783 on 2008 R2 member servers

Dear Experts,
 
Here's the scenario:
 
5 DCs in one site all 2003 DCs
10 member servers 2008 R2 that are occassionally reporting netlogon 5719 and 5783 netlogon errors.
What could be the issues leading to this?
 
 
EVENT ID: 5719
This computer was not able to set up a secure session with a domain controller in domain CORP due to the following:

There are currently no logon servers available to service the logon request.

This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

 
EVENT ID:  5783
The session setup to the Windows NT or Windows 2000 Domain Controller \DC08.FTS.ADS.FOXTV.COM for the domain CORP is not responsive.  The current RPC call from Netlogon on \SERVER02 to \DC08.FTS.ADS.FOXTV.COM has been cancelled.'
 
Thank you!
mmoyaAsked:
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.

Darius GhassemCommented:
Most of the time the issue is with DNS.

Make sure all member servers and domain controllers only point to DCs for DNS in their TCP\IP settings.

Make sure you have any secondary network cards disabled

On Windows 2008 Servers make sure IPv4 is listed first in binding order http://theregime.wordpress.com/2008/03/04/how-to-setview-the-nic-bind-order-in-windows/

Run dcdiag post results.
baraneCommented:
There are are problem with the DNS Settings

Kindly perform the Dcdiag and netdiag on the server listed on the event and check if you find any errors.
mmoyaAuthor Commented:
@dariusq and barane - our domain controllers are all DNS servers but do not point to itself. We have two main DNS servers that they point to. This is how it's setup in this environment. Could that be it?

I changed the binding orders in the advanced TCP/IP settings on our 2008 R2 members servers and will seee if that will solve the issue...
Price Your IT Services for Profit

Managed service contracts are great - when they're making you money. Yes, you’re getting paid monthly, but is it actually profitable? Learn to calculate your hourly overhead burden so you can master your IT services pricing strategy.

Darius GhassemCommented:
DC should point to themselves.

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
mmoyaAuthor Commented:
DC is pointing to a proxy DNS server and it sends the connection right back to itself. Do you think that's the issue in here? Thanks again.
Darius GhassemCommented:
Could be
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 2008

From novice to tech pro — start learning today.