Problem with replicating AD and DNS
in [Active Directory]
|
Prev: Warning: DcGetDcName(PDC_REQUIRED) call failed, error 1355
Next: "MS DTC could not correctly process a DC Promotion/Demotion event.
From: Eon Blue on 14 Oct 2005 10:47 I manually added the records with no luck. The only record I did not add was the CNAME record in the _msdcs folder. The name for the record in there pointing to the 2000 server is a string of characters and I'm not sure where it pulled those from. The 2003 server is currently functioning as the primary dns server. It's resolving everything fine. It's receiving updates just fine from the 2000 server. The problem is just in the reverse with the 2000 server not receiving updates from the 2003 server. When running netdiag on the 2003 server I get this: DNS test . . . . . . . . . . . . . : Failed [WARNING] Cannot find a primary authoritative DNS server for the name 'VERISERV.MVESC.'. [RCODE_SERVER_FAILURE] The name 'VERISERV.MVESC.' may not be registered in DNS. [WARNING] The DNS entries for this DC are not registered correctly on DNS se rver '10.19.33.201'. Please wait for 30 minutes for DNS server replication. [FATAL] No DNS servers have the DNS records for this DC registered. (The domain name is just MVESC.) When running netdiag on the 2000 server I get this: DNS test . . . . . . . . . . . . . : Passed [WARNING] Cannot find a primary authoritative DNS server for the name 'MVESCDC.MVESC.'. [RCODE_SERVER_FAILURE] The name 'MVESCDC.MVESC.' may not be registered in DNS. PASS - All the DNS entries for DC are registered on DNS server '10.19.33.201 ' and other DCs also have some of the names registered.
From: Brandon McGarvey on 14 Oct 2005 14:55
I'd suggest using replmon to diagnose the replication problem, but most likely it will return similar results as netdiag. Can you connect to shares on the 2003 domain controller from the 2000 domain controller? If you haven't tried, map a drive to the 2003 server using the FQDN of the server to ensure it using connecting over port 445, rather 139. Command - net use \\domaincontroller.domain.com\c$. Port 139 is SMB over NetBT and that won't validate that DNS resolution to the server is working from the 2000. It is difficult to troubleshoot a problem like this without being at the server. Most problems with Active Directory are caused from DNS problems or misconfigurations. "Eon Blue" wrote: > I manually added the records with no luck. The only record I did not > add was the CNAME record in the _msdcs folder. The name for the record > in there pointing to the 2000 server is a string of characters and I'm > not sure where it pulled those from. > > The 2003 server is currently functioning as the primary dns server. > It's resolving everything fine. It's receiving updates just fine from > the 2000 server. The problem is just in the reverse with the 2000 > server not receiving updates from the 2003 server. > > When running netdiag on the 2003 server I get this: > > DNS test . . . . . . . . . . . . . : Failed > [WARNING] Cannot find a primary authoritative DNS server for > the name > 'VERISERV.MVESC.'. [RCODE_SERVER_FAILURE] > The name 'VERISERV.MVESC.' may not be registered in DNS. > [WARNING] The DNS entries for this DC are not registered correctly > on DNS se > rver '10.19.33.201'. Please wait for 30 minutes for DNS server > replication. > [FATAL] No DNS servers have the DNS records for this DC registered. > > (The domain name is just MVESC.) > > When running netdiag on the 2000 server I get this: > > DNS test . . . . . . . . . . . . . : Passed > [WARNING] Cannot find a primary authoritative DNS server for > the name > 'MVESCDC.MVESC.'. [RCODE_SERVER_FAILURE] > The name 'MVESCDC.MVESC.' may not be registered in DNS. > PASS - All the DNS entries for DC are registered on DNS server > '10.19.33.201 > ' and other DCs also have some of the names registered. > > |