Windows 2012 boot up Event ID 5719 Netlogon

This computer was not able to set up a secure session with a domain controller in domain <domain name> 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.  

ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
bergquistcompanyAsked:
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.

aindelicatoCommented:
Is the DNS server the IP of your domain controller?
bergquistcompanyAuthor Commented:
There is a static IP assigned and the DNS is configured to the IP of the domain controller in that domain.  It is happening on reboot, but I still think it shouldn't be :)
aindelicatoCommented:
You are correct, it shouldnt be.  This error usually indicates a dns resolution error when it can't find the domain controller.

Make sure in DNS that you have proper records for your DCs.  Is it only this one machine that is having this issue?
Your Guide to Achieving IT Business Success

The IT Service Excellence Tool Kit has best practices to keep your clients happy and business booming. Inside, you’ll find everything you need to increase client satisfaction and retention, become more competitive, and increase your overall success.

bergquistcompanyAuthor Commented:
No I installed Windows 2012 on 3 new servers that will be replacing the 2003 DCs eventually but after installing the OS and rebooting they all get this error on reboot of the server.
aindelicatoCommented:
Was this an older domain?  2012 servers can't see domains that aren't at least at a 2003 Domain Functional Level.
bergquistcompanyAuthor Commented:
They are 2003 functional level and I have one with nothing in the static DNS and is DHCP as it's just a fresh 2012 install no promotions yet and that too gets error on reboot.
aindelicatoCommented:
Seems like the Netlogon service is starting before the network is actually ready.

See this article:
http://support.microsoft.com/kb/938449


Resolution 1

To resolve this issue, install the most current driver for the Gigabit network adapter. Another approach may be to enable the "PortFast" option on the network switches.


Resolution 2

Set this registry entry to a value that is safely beyond the time it takes to retrieve a working IP address:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netlogon\Parameters
Value Name: ExpectedDialupDelay
Data Type: Reg_Dword
Data Value is in seconds (default = 0)
Data Range is between 0 and 600 seconds (10 minutes)


Also configure this setting (details in KB 244474):

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\ Kerberos\Parameters
MaxPacketSize to 1

Resolution 3

Acconrding to KB 239924, disable media sense for TCP/IP:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters
Add the following registry value:
Value Name: DisableDHCPMediaSense
Data Type: REG_DWORD -Boolean
Value Data: 1 (False, True)
Default: 0 (False)


Resolution 4

There is a known problem with DHCP client code in Windows 7. A hotfix is going to be released using this KB article: http://support.microsoft.com/?kbid=2459530

Resolution 5

To resolve this issue, reduce the Netlogon negative cache period (the NegativeCachePeriod registry entry). When you do this, the Netlogon service does not behave as if the domain controllers are offline for 45 seconds. The event 5719 is still logged, but there is little negativ eside-effect from that. The setting enables domain controllers to connect earlier.

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
819108 Settings for minimizing periodic WAN traffic
bergquistcompanyAuthor Commented:
Ok tried 1, 2 & 3 yet same event on reboot.
Didn't do 4 as I'm on windows 2012.  
I don't have the NegativeCachePeriod key

Any other suggestions?
bergquistcompanyAuthor Commented:
called Microsoft and they made registry change and lost all networking so had to run restore to recover.  Going to rebuild it at this point.

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
bergquistcompanyAuthor Commented:
too much time and recovery it would be easier to reimage at this point and run.
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 2012

From novice to tech pro — start learning today.