?
Solved

Error 5719: on Boot up

Posted on 2007-10-10
12
Medium Priority
?
522 Views
Last Modified: 2010-05-18
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               ^..À    
0
Comment
Question by:GlennCameron
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 7
  • 5
12 Comments
 

Author Comment

by:GlennCameron
ID: 20052287
The server is a new Dell Poweredge within GB nics. I have installed windows 2003 and ISA 2006 on it and am recieving the error above. Tested all of the cables to the switch etc. Set the GB nic and the switch to be 100/ FULL. All tried http://support.microsoft.com/kb/938449.
0
 
LVL 3

Expert Comment

by:DPAIT
ID: 20052349
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?
0
 

Author Comment

by:GlennCameron
ID: 20052389
I already have ISA 2006 disabled and can ping both of my domain controllers.
0
Enterprise Mobility and BYOD For Dummies

Like “For Dummies” books, you can read this in whatever order you choose and learn about mobility and BYOD; and how to put a competitive mobile infrastructure in place. Developed for SMBs and large enterprises alike, you will find helpful use cases, planning, and implementation.

 
LVL 3

Expert Comment

by:DPAIT
ID: 20052437
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.  
0
 

Author Comment

by:GlennCameron
ID: 20052565
I disabled all but one Nic, still the same problem.
0
 
LVL 3

Expert Comment

by:DPAIT
ID: 20052577
Since its' a new box.  Have you tried removing it from the domain, verify it's deleted at AD, then rejoin the domain?
0
 

Author Comment

by:GlennCameron
ID: 20052860
Same issue after rejoining the domain
0
 
LVL 3

Expert Comment

by:DPAIT
ID: 20052912
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.
0
 

Author Comment

by:GlennCameron
ID: 20053238
No joy, however just found something interesting. My internal clients (workstations all XP) can ping the new server however my servers can not
0
 
LVL 3

Accepted Solution

by:
DPAIT earned 1500 total points
ID: 20053451
That is strange.

Are they on same subnet?

Are you pinging by name or by IP?
0
 

Author Comment

by:GlennCameron
ID: 20059176
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
0
 

Author Comment

by:GlennCameron
ID: 20165715
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
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

A quick step-by-step overview of installing and configuring Carbonite Server Backup.
ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
This video Micro Tutorial explains how to clone a hard drive using a commercial software product for Windows systems called Casper from Future Systems Solutions (FSS). Cloning makes an exact, complete copy of one hard disk drive (HDD) onto another d…
Windows 8 comes with a dramatically different user interface known as Metro. Notably missing from the new interface is a Start button and Start Menu. Many users do not like it, much preferring the interface of earlier versions — Windows 7, Windows X…
Suggested Courses

762 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question