Win2k3 - Event ID 5719 domain controller cannot be found
#1
Win2k3 - Event ID 5719 domain controller cannot be found
Anyone know why the Win2k3 server can't talk to the Win2k Domain Controller ?
************************************************** *******
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 9/28/2001
Time: 4:12:55 PM
User: N/A
Computer: Server
Description:
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.
Data:
0000: c000005e
************************************************** ********
We recently moved the server to a new room, but I can't see why this would cause the above to happen.
************************************************** *******
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 9/28/2001
Time: 4:12:55 PM
User: N/A
Computer: Server
Description:
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.
Data:
0000: c000005e
************************************************** ********
We recently moved the server to a new room, but I can't see why this would cause the above to happen.
#4
David, the new location for the 2 servers only had a single wall socket.
I put a small 4 port switch into the wall socket and plugged the 2 servers into the switch.
Would that make a difference ?
Kieran, thanks for the link - will check it out.
I put a small 4 port switch into the wall socket and plugged the 2 servers into the switch.
Would that make a difference ?
Kieran, thanks for the link - will check it out.
#5
Quick update - this seemed to sort the problem:
Event ID 5719 - The system cannot log you on now because the domain "name" is not available."
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\Servic es\NetBT\Parameters. On the Edit menu, click Add Value, and then add the following information:
Value Name: MaxDgramBuffering
Data Type: REG_DWORD
Value: 0x40000
Event ID 5719 - The system cannot log you on now because the domain "name" is not available."
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\Servic es\NetBT\Parameters. On the Edit menu, click Add Value, and then add the following information:
Value Name: MaxDgramBuffering
Data Type: REG_DWORD
Value: 0x40000
Thread
Thread Starter
Forum
Replies
Last Post
Mattybr5@MB Developments
Full Cars Breaking For Spares
12
18 November 2015 07:03 AM