Re: Clients unable to locate the DC

Yes, the lack of reverse lookup zone caused:

DNS request timed out ****can't
find server name for address 192XXX


The other problem is fixed by ensuring the zone accepts dynamic updates and
the DC is pointing to it and configured to register in DNS - the NETLOGON
process will re-register SRV records every hour, and the A and PTR RRs every
12 hours.

Sorry for the delay - I've been on an extended holiday ;-)

--
Paul Williams
Microsoft MVP - Windows Server - Directory Services
http://www.msresource.net | http://forums.msresource.net


.

Relevant Pages

  • RE: DHCP and DNS dynamic update
    ... you want to use Secure Dynamic Updates feature for Windows ... For Windows Server 2003, DNS update security is available only for zones ... available in the DNS snap-in to add or remove users or groups from the ACL ... Windows Server 2003 DNS clients try to use nonsecure dynamic updates first. ...
    (microsoft.public.windows.server.migration)
  • Re: Folder Redirection Trouble Win2003
    ... These errors occur because the DNS server doesn’t have a Reverse Lookup Zone Configured. ... If it's a private address it will say cannot establish a secured connection with the server prisoner.iana.org. ... -Start Registry Editor. ... > There is a Folder Redirection policy for My Documents in Default Domain ...
    (microsoft.public.windows.server.active_directory)
  • Re: RWW not connecting to desktop BOSS
    ... Open DHCP server, right click the server's FQDN and select Properties. ... Navigate to DNS tab. ... To configure the zone to permit dynamic updates, ... click Non-secure and secure in the Dynamic updates ...
    (microsoft.public.windows.server.sbs)
  • Domain not seen in DNS Snap in after migrating to AD integrated
    ... I switched "pdc" to native mode and the ... When I went to the 2nd DNS Server which was running as ... I went to switch the REVERSE LOOKUP Zone, ...
    (microsoft.public.win2000.dns)
  • Re: Not able to establish trust with another window 2003 domain
    ... Although Active Directory doesn't need Reverse Lookup Zone to function, the Windows 2003 and XP tries to make a secure PTR registration, and because the Reverse Lookup Zone isn't configured, the OS tries to make a secure PTR registration at the External DNS that is Authoritative over the reverse lookup of the IP on the machine's local interface. ... If it's a private address it will say cannot establish a secured connection with the server prisoner.iana.org. ... > I had follow exactly the same that stated in your article but still> fail. ... > I try to remove the trust that created at my Source and re-create> again. ...
    (microsoft.public.windows.server.active_directory)