Re: DHCP Clients getting DNS lookup failures
- From: "Dave Nickason [SBS MVP]" <gwdibble@xxxxxxxxxxxxxxxxxxxxxx>
- Date: Mon, 3 Apr 2006 18:33:21 -0400
While you're waiting from a response from someone brilliant, try going to a
workstation and in Network Connections, r-click the NIC and click Repair.
If that doesn't work, open a command prompt and type ipconfig /flushdns.
Make sure the firewall client is enabled on the workstation.
It sounds to me like you had a DNS issue but you fixed it, so I'm wondering
if in the meantime the workstations got some bad info from DHCP. If so, the
above should get rid of it.
"Russ" <russelldipesa@xxxxxxxxxxx> wrote in message
news:1144096184.669177.27540@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
To All:
I posted about this earlier, but got no reply. So, I will update on
the progress I have made. I am currently getting DNS lookup failures
on my client machines. The server can access the Internet without
issues. The server is dual NIC running ISA Server and is acting as the
DNS and DHCP server with NAT enabled. Everything was fine on Friday
afternoon when I left. This morning, all of the clients were unable to
connect to the Internet. There were some automatic updates that
occurred at around 4:03 A.M. Saturday, one of them being the
installation of Service Pack 2 of the ISA Server 2004. Then, I noticed
in the DNS event log the following events that occurred on Saturday at
4:08 A.M.:
EventID 4015
The DNS server has encountered a critical error from the Active
Directory. Check that the Active Directory is functioning properly. The
extended error debug information (which may be empty) is "". The event
data contains the error.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
EventID 4004
The DNS server was unable to complete directory service enumeration of
zone .. This DNS server is configured to use information obtained from
Active Directory for this zone and is unable to load the zone without
it. Check that the Active Directory is functioning properly and repeat
enumeration of the zone. The extended error debug information (which
may be empty) is "". The event data contains the error.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
EventID4004
The DNS server was unable to complete directory service enumeration of
zone _msdcs.doubler.local. This DNS server is configured to use
information obtained from Active Directory for this zone and is unable
to load the zone without it. Check that the Active Directory is
functioning properly and repeat enumeration of the zone. The extended
error debug information (which may be empty) is "". The event data
contains the error.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
EventID 4004
The DNS server was unable to complete directory service enumeration of
zone 1.168.192.in-addr.arpa. This DNS server is configured to use
information obtained from Active Directory for this zone and is unable
to load the zone without it. Check that the Active Directory is
functioning properly and repeat enumeration of the zone. The extended
error debug information (which may be empty) is "". The event data
contains the error.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
EventID 4004
The DNS server was unable to complete directory service enumeration of
zone doubler.local. This DNS server is configured to use information
obtained from Active Directory for this zone and is unable to load the
zone without it. Check that the Active Directory is functioning
properly and repeat enumeration of the zone. The extended error debug
information (which may be empty) is "". The event data contains the
error.
For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
After running a dcdiag and netdiag, I noticed that there were some
issues with the DNS, so I removed the DNS zones in AD and in Server
Management. I recereated them, flushed the DNS and registered the DNS.
Now, when I run dcdiag and netdiag, there are no errors with the DNS.
The DHCP clients all have their Primary DNS set to the local address of
the server. My ISPs DNS addresses are set in the Forwarders tab on the
server. The clients can ping the local server address and the IP
assigned to the 2nd NIC. However, they get no farther than that.
Can some brilliant soul point me in the right direction to get my
clients back up and running on the Internet?
Regards,
Russ
.
- References:
- DHCP Clients getting DNS lookup failures
- From: Russ
- DHCP Clients getting DNS lookup failures
- Prev by Date: Re: Moving used CALs to New Hardware
- Next by Date: Re: SBS software transfer
- Previous by thread: DHCP Clients getting DNS lookup failures
- Next by thread: Re: DHCP Clients getting DNS lookup failures
- Index(es):
Relevant Pages
|
