|
|
|
#1 |
|
Messages: n/a
Hébergeur: |
I have three sites connected by Cisco VPNs. Site A has three DCs and site B
has 1 DC. I am attempting to add another DC at Site C. All sites are different OUs but the same domain. After adding (dcpromo) the 5th DC at Site C, the Site C DNSMGMT tool does not show the ch.local zone. The zone is present on the othe DC DNSMGMT tools. Active Directory Users and Computers shows everything as does Sites and Services. I have tried net stop/start netlogon, manually creating the zones, and other things, but to no avail. Anyone know why this is and what I can do to rectify the problem? |
|
|
|
#2 |
|
Messages: n/a
Hébergeur: |
Try reloading your zone
While in the mmc console for dns, connect to the dc. Drill down to the zone in question and right click on it and select "Reload." Not sure if this is it, but give it a shot. -- Paul Bergson MVP - Directory Services MCT, MCSE, MCSA, Security+, BS CSci 2003, 2000 (Early Achiever), NT http://www.pbbergs.com Please no e-mails, any questions should be posted in the NewsGroup This posting is provided "AS IS" with no warranties, and confers no rights. "Burt" <Burt@discussions.microsoft.com> wrote in message news:1E150ECE-7380-4978-9498-A70966DA8D6D@microsoft.com... >I have three sites connected by Cisco VPNs. Site A has three DCs and site B > has 1 DC. I am attempting to add another DC at Site C. All sites are > different OUs but the same domain. After adding (dcpromo) the 5th DC at > Site > C, the Site C DNSMGMT tool does not show the ch.local zone. The zone is > present on the othe DC DNSMGMT tools. Active Directory Users and Computers > shows everything as does Sites and Services. I have tried net stop/start > netlogon, manually creating the zones, and other things, but to no avail. > Anyone know why this is and what I can do to rectify the problem? > |
|
|
|
#3 |
|
Messages: n/a
Hébergeur: |
Tried that initially. I think I figured out the problem. In my test
environment, my first AD DC was not storing DNS zone info in AD. I do not know why this was. Consequently every subsequent DC was not pulling any of the AD records or folders. Once I changed the settings on the zone on the first DC, everything replicated within 45 minutes. As far as my problems in the production environment, I believe the problem stems from a slower replication time between Site C and the other sites. More patience on my part and the problem may have resolved itself. Any ways, . . . "Paul Bergson [MVP-DS]" wrote: > Try reloading your zone > > While in the mmc console for dns, connect to the dc. Drill down to the zone > in question and right click on it and select "Reload." > > Not sure if this is it, but give it a shot. > > -- > Paul Bergson > MVP - Directory Services > MCT, MCSE, MCSA, Security+, BS CSci > 2003, 2000 (Early Achiever), NT > > http://www.pbbergs.com > > Please no e-mails, any questions should be posted in the NewsGroup > This posting is provided "AS IS" with no warranties, and confers no rights. > > "Burt" <Burt@discussions.microsoft.com> wrote in message > news:1E150ECE-7380-4978-9498-A70966DA8D6D@microsoft.com... > >I have three sites connected by Cisco VPNs. Site A has three DCs and site B > > has 1 DC. I am attempting to add another DC at Site C. All sites are > > different OUs but the same domain. After adding (dcpromo) the 5th DC at > > Site > > C, the Site C DNSMGMT tool does not show the ch.local zone. The zone is > > present on the othe DC DNSMGMT tools. Active Directory Users and Computers > > shows everything as does Sites and Services. I have tried net stop/start > > netlogon, manually creating the zones, and other things, but to no avail. > > Anyone know why this is and what I can do to rectify the problem? > > > > > |
|
![]() |
| Outils de la discussion | |
|
|