GlennCameron
asked on
Error 5719: on Boot up
Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 11/10/2007
Time: 8:48:17:AM
User: N/A
Computer: SVR-11
Description:
No Domain Controller is available for domain KEYLOGIX due to the following:
There are currently no logon servers available to service the logon request. .
Make sure that the computer is connected to the network and try again. If the problem persists, please contact your domain administrator.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 5e 00 00 c0 ^..À
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 11/10/2007
Time: 8:48:17:AM
User: N/A
Computer: SVR-11
Description:
No Domain Controller is available for domain KEYLOGIX due to the following:
There are currently no logon servers available to service the logon request. .
Make sure that the computer is connected to the network and try again. If the problem persists, please contact your domain administrator.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 5e 00 00 c0 ^..À
Sounds like ISA 2006 could be blocking your network connections outbound to the DC. Can you login as a local user and ping the domain controller?
ASKER
I already have ISA 2006 disabled and can ping both of my domain controllers.
Possible other solutions to look at. I pulled the following from Eventid.net
http://www.eventid.net/display.asp?eventid=5719&eventno=104&source=NETLOGON&phase=1
Anonymous (Last update 2/27/2007):
In my case, the Terminal Server (Windows Server 2003 R2) has two NICs. One of them is connected to the G.SHDSL Router/Modem and the other one is on Ethernet backbone and communicating with DC/DNS (Windows Server 2003 R2). I have received this error after Event ID 5783 from the same source. The problem was resolved after changing the connections order for "Adapters and Bindings" as LAN was on the top (Network Connections-Advanced Settings).
Since you are setting up ISA server, I would try disabling the NIC that is configured to go out of the network.
http://www.eventid.net/display.asp?eventid=5719&eventno=104&source=NETLOGON&phase=1
Anonymous (Last update 2/27/2007):
In my case, the Terminal Server (Windows Server 2003 R2) has two NICs. One of them is connected to the G.SHDSL Router/Modem and the other one is on Ethernet backbone and communicating with DC/DNS (Windows Server 2003 R2). I have received this error after Event ID 5783 from the same source. The problem was resolved after changing the connections order for "Adapters and Bindings" as LAN was on the top (Network Connections-Advanced Settings).
Since you are setting up ISA server, I would try disabling the NIC that is configured to go out of the network.
ASKER
I disabled all but one Nic, still the same problem.
Since its' a new box. Have you tried removing it from the domain, verify it's deleted at AD, then rejoin the domain?
ASKER
Same issue after rejoining the domain
So you can actually join the domain successfully and the computer account is created OK. But then at re-logon you can not longer see the domain?
Sounds like a local firewall setting or something in the ISA server setup isn't truely disabled. If you can see it to join, you should be able to see it to login. Something fishy there,
Sorry at a lose for what to test. Maybe try changing which nic is enabled? shot in the dark.
Sounds like a local firewall setting or something in the ISA server setup isn't truely disabled. If you can see it to join, you should be able to see it to login. Something fishy there,
Sorry at a lose for what to test. Maybe try changing which nic is enabled? shot in the dark.
ASKER
No joy, however just found something interesting. My internal clients (workstations all XP) can ping the new server however my servers can not
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Sorry for the delay, yes both are on the same subnet, client can ping both the name or ip successfully, another one of the servers cannot ping either. If you attempt to ping svr-11 it does resolve the IP correctly so it does not look like a DNS problem
ASKER
In summary it was a DNS and switch issue. A DNS reverse lookup was missing and I found an issue with the port groupings on my Cisco swtiches
ASKER