Windows Server 2003 Event ID 5719

ratler · May 17, 2006

During the boot sequence, member servers (Windows 2003 Server 32 bit edition) fails to properly authenticate to the domain controller - the error text indicates that no domain controller is available to process the login or the network is down. System is a Dell PowerEdge 2650 with Broadcom NetXtreme GE NICs. Found a Technet article about GE NICs indicating some known problem and tried those fixes, also updated the NIC drivers to latest version but neither solution worked. Anyone seen this issue and have any idea how to resolve?

Thanks.

theefool · May 17, 2006

Can the member servers ping the domain controller?

Have you tried replacing the NIC? Has this issue just started happening?

Not sure all the steps you have taken.

Have you tried:

Symptoms: when attempting to logon a domain, you keep getting an error that "The system cannot log you on now because the domain "name" is not available." Also, Event viewer shows Event ID: 5719. No Windows NT or Windows 2000 Domain Controller is available for domain <domain name>. The following error occurred: There are currently no logon servers available to service the logon request.

Resolutions: One possible cause of this error is that you have run out of buffer space in the NetBT datagram buffer. To resolve this problem, increase the MaxDgramBuffering value from 128 KB to 256 KB. Run Regedt32.exe, go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NetBT\Parameters. On the Edit menu, click Add Value, and then add the following information:

Value Name: MaxDgramBuffering
Data Type: REG_DWORD
Value: 0x40000
Click to expand...

http://support.microsoft.com/kb/898060/en-us

Log in or Sign up

Windows Server 2003 Event ID 5719

ratler Private E-2

theefool Geekified

Log in or Sign up

Windows Server 2003 Event ID 5719

ratler Private E-2

theefool Geekified

Useful Searches