RE: DNS is Causing real Problems please help..!



Hi PaulK,

I've just had a similar issue here that we've only picked up after the
latest round of patches but your posting pre-dates that.

For us, on restart of a DC/GC, AD failed to start as it could not find a
DC/GC to authenticate to and (AD integrated) DNS wouldn't start because AD
wouldn't start.

I pointed the NIC Primary DNS at another DNS server in our domain and lo -
everything started up on the next 'try again' cycle ie AD restarted itself
and DNS followed a few minutes later.

Info I found implied that this is a known loop for AD integrated DNS on a
DC/GC pointing to itself (at the NIC) as a primary DNS source - there's an MS
KB that sys (for W2k) that this shouldn't be configured like this because of
this problem.

I'm not sure if this would have solved your problem, but since Kerberos
depends on AD authority and it isn't starting up ...

Any thoughts form anyone out there?

Regards,

Nigel Harvey
IT Sys Eng
W2k3 Native domain - 180+ servers

"PaulK" wrote:


Dear all

I think my issue is dns related as no permission changes have changed
on sysvol etc.

Network is running really slow.

Getting the standard errors on workstations
1097
(Windows cannot find the machine account, No authority could be
contacted for authentication. .)
1030
(Windows cannot query for the list of Group Policy objects. A message
that describes the reason for this was previously logged by the policy
engine)
1054
(Windows cannot obtain the domain controller name for your computer
network. (The specified domain either does not exist or could not be
contacted. . Group Policy processing aborted. )

have 3 DCs in total (one is 2000svr)
the 2 Win 2003 DCs act as DNS servers.

when logged on as a std user, i can ping the domain name, the servers
by FQDN, access the sysvol folders by \\DC_servername\sysvol and
\\domainname\sysvol

RSOP.msc (ComputerConfiguration) however returns the error
-----------------------------------------------------------
Group Policy Infrastructure failed due to the error listed below.
No authority could be contacted for authentication.

Note: Due to the GP Core failure, none of the other Group Policy
components processed their policy. Consequently, status information
for the other components is not available.

can anyone please help..!

kr Paul..


--
PaulK
------------------------------------------------------------------------
PaulK's Profile: http://forums.techarena.in/member.php?userid=48567
View this thread: http://forums.techarena.in/showthread.php?t=964016

http://forums.techarena.in


.



Relevant Pages

  • Re: Very strange problem with XP machine reporting ERROR_NO_LOGON_SERV
    ... After restart, removed PC from domain. ... unless DNS is dependent upon kerberos? ... rejoining, which I've already done). ... Manually entered DNS server as DNS server. ...
    (microsoft.public.windows.server.active_directory)
  • Re: event id 1054 and other group policy problems
    ... Before you demote the first DC from BBB have ... of the clients can't access it because of the DNS). ... > Windows cannot query for the list of Group Policy objects. ... I have the ip address of the dns server in AAA as primary> dns on HYPER, ...
    (microsoft.public.win2000.active_directory)
  • Re: After enabling GPO, client pc needs synchronization
    ... correct DNS configuration. ... Server 2003 domain controllers dynamically register information about ... As far as Group Policy troubleshooting you can use rsop.msc on the client ...
    (microsoft.public.windowsxp.security_admin)
  • Re: USERENV error - Group Policy
    ... Check DNS ... -Make sure that each DNS server points to itself under NIC preferred DNS. ... -I've also examined the SMB signing settings, ... Applying Group Policy causes Userenv errors and events to occur on your ...
    (microsoft.public.windows.server.active_directory)
  • RE: logon to domain while dc is colsed
    ... As far I know you cannot use the Group Policies without a DNS server ... Check if the affected machines can correctly perform DNS resolution. ... Probably half of all Group Policy processing issues are related to DNS ... You could check which GPO's are running, installing this tool in your ...
    (microsoft.public.windows.server.active_directory)

Loading