Archived from groups: microsoft.public.win2000.active_directory (
More info?)
"TOM" <anonymous@discussions.microsoft.com> wrote in message
news:0b4501c50f13$c93b0210$a401280a@phx.gbl...
> Thanks for the replies everyone! Okay that advice
> resolved the replication issues. Thanks. I do believe
> that DNS is somehow causing this, how can I get resolve
> this error (from Netdiag):
>
> DNS test . . . . . . . . . . . . . : Passed
> [WARNING] The DNS entries for this DC cannot be
> verified right now on DNS server 192.168.5.6,
> ERROR_TIMEOUT.
This one implies that 192.168.5.6 is listed IN THE ZONE
as an NS (DNS) server but is either down, has the DNS
service OFF, or the zone not configured.
DNS thinks it is one of the DNS Servers but that server
is not functioning. Thus the error when it Times-Out.
> PASS - All the DNS entries for DC are registered on
> DNS server '192.168.5.20
> ' and other DCs also have some of the names registered.
--
Herb Martin
"TOM" <anonymous@discussions.microsoft.com> wrote in message
news:0b4501c50f13$c93b0210$a401280a@phx.gbl...
> Thanks for the replies everyone! Okay that advice
> resolved the replication issues. Thanks. I do believe
> that DNS is somehow causing this, how can I get resolve
> this error (from Netdiag):
>
> DNS test . . . . . . . . . . . . . : Passed
> [WARNING] The DNS entries for this DC cannot be
> verified right now on DNS server 192.168.5.6,
> ERROR_TIMEOUT.
>
> PASS - All the DNS entries for DC are registered on
> DNS server '192.168.5.20
> ' and other DCs also have some of the names registered.
>
>
>
>
>
>
>
>
> >-----Original Message-----
> >Follow Herb's advice re. reregistering in DNS.
> >
> >Good to see you again Herb!!! Nice holiday/ consulting
> job???
> >
> >
> >So you're not holding a zone for the parent DNS domain?
> You should be
> >really. You should probably delegate the sub-domain from
> the parent to your
> >DNS servers. You should also hold a secondary copy of
> the parent domain's
> >DNS.
> >
> >One your DCs (DNS servers) add a secondary zone that is
> the parent domain's
> >zone.
> >Once you've followed Herb's instructions and re-
> registered all the DCs in
> >DNS, flush the event log, restart DNS and then run
> netdiag /test:dns and
> >nltest /dsgetdc:domain-name.com. If the results aren't
> all good, post them
> >again...
> >
> >
> >> How can I make KCC pick the bridgehead? I really don't
> know what can be
> >> wrong, how can I fix this?
> >
> >Undo the option to make the machine a preferred
> bridgehead and wait fifteen
> >minutes for the KCCs on each server to run. You can
> force this using sites
> >and services (check replication topology -context
> sensitive menu item) or
> >replmon.
> >
> >--
> >
> >Paul Williams
> >
> >http://www.msresource.net/
> >http://forums.msresource.net/
> >
> >"TOM" <anonymous@discussions.microsoft.com> wrote in
> message
> >news:219501c50e5d$ecdd9860$a501280a@phx.gbl...
> >Also, in our child domain we have one Forward lookup zone
> >for our domain and a reverse lookup zone for our domain.
> >These are the only two zones on our DNS servers.
> >
> >
> >
> >
> >>-----Original Message-----
> >>Thanks for your reply,
> >>
> >>I am getting a DNS error in netdiag on DC1 and DC2. Here
> >>is the one from DC1:
> >>
> >>DNS test . . . . . . . . . . . . . : Passed
> >> [WARNING] The DNS entries for this DC cannot be
> >>verified right now on DNS <--- This is the error
> >> server 192.168.5.6, ERROR_TIMEOUT.
> >> PASS - All the DNS entries for DC are registered on
> >>DNS server '192.168.5.10
> >>' and other DCs also have some of the names registered.
> >>>-----Original Message-----
> >>
> >>We are a child domain with 2 DC's as I said and we
> >>replicate with HQ which is on a 192.168.1.x subnet. We
> >are
> >>on a 192.168.5.x subnet. We are on a high spped
> >connection
> >>and there are three sites, us, HQ and other. I have my
> >DNS
> >>servers both pointing at themselves (DC1 and DC2) and
> >they
> >>replicate to DC's in our domain(we are a child domain). I
> >>did set the bridgehead server myself (DC1) and now I have
> >>read that KCC should have done that. How can I make KCC
> >>pick the bridgehead? I really dont know what can be
> >>wrong, how can I fix this?
> >>
> >>
> >>
> >>
> >>>Tom,
> >>>
> >>>You'll need to give us some info about your sites,
> >>subnets, and physical
> >>>connections. This looks like a DNS problem... but to
> >>give you anything
> >>>more specific about the topology and relationship to the
> >>parent domain.
> >>>
> >>>--
> >>>Ryan Hanisco
> >>>MCSE, MCDBA
> >>>Flagship Integration Services
> >>>
> >>>"TOM" <anonymous@discussions.microsoft.com> wrote in
> >>message
> >>>news:213001c50e51$23d18280$a501280a@phx.gbl...
> >>>>I have 2 DC's in a child domain both running AD
> >>integrated
> >>>> DNS. 1 DC, DC1, is a bridgehead server and DC2 is just
> >a
> >>>> DC. Both are GC's, DC1 holds the RID, PDC roles. DC2
> >>holds
> >>>> the infrastructure role. These two DC's just replaced
> 2
> >>>> W2k Dc's. The problem is I dont think that replication
> >>is
> >>>> working correctly. I am getting event ID 1864 in DC1
> >>and
> >>>> in DC2 when I run dcdiag it states that the ISTG is
> not
> >>>> running and RPC server is not responding and that DC2
> >is
> >>>> not responding to directory requests. I also get this
> >in
> >>>> DCdiag:
> >>>> Testing server: CHILD\DC2
> >>>> Starting test: Connectivity
> >>>> * Active Directory LDAP Services Check
> >>>> The host d7f787fa-c111-4f3b-9b64-
> >>>> 695e79d36650._msdcs.parent.org could not be resolved
> >to
> >>an
> >>>> IP address. Check the DNS server, DHCP,
> server
> >>>> name, etc
> >>>> Although the Guid DNS name
> >>>> (d7f787fa-c111-4f3b-9b64-
> >>>> 695e79d36650._msdcs.parent.org)
> >>>> couldn't be resolved, the server name
> >>>> (DC2.child.parent.org) resolved to the IP
> >>address
> >>>> (192.168.5.7) and was pingable. Check that
> the
> >>>> IP address is
> >>>> registered correctly with the DNS server.
> >>>> ......................... DC2 failed test
> >>>> Connectivity
> >>>>
> >>>> My question is (A) How do I resolve this? and (B) How
> >>can
> >>>> I verify that replication is actually occurring
> >>>> correctly? I have run replmon and I do not see any
> >>>> errors?! Please help
Thanks
> >>>>
> >>>
> >>>
> >>>.
> >>>
> >>.
> >>
> >
> >
> >.
> >