gc didn't found.

[hemina.modi]

hello,
We have one server as domain controller named as PDC
second one is additional domain controller named as ROOT
then we first transfer all role .then after 15 mins change ip of both
server.
so it shows error that domain controller coudn't found.
Then we again make change and set it is as before then after we
transfer gc.
bt now sysvol didn't share bydefault after role transfer and logon
script is not running.
then we run dcdiag it show's gc couldn't located and all gc are down.
and also frs service stop autometically...
now users suffer no problem b'coz both pdc and root is on bt as we
shutdown pdc
they indicate error in logon script.
wt should we do to stable our domain controller.

 

[Mike Shepperd]

Wow!

I'm not sure why you would take those steps in the first place, but assuming
you had a compelling reason to do so, lets try to get it working again.

First, pick one DNS server to point both DC's at and only use that one
server, don't have an alternate. Then go into the DNS Management console
and delete all of the entries for those DC's (you'll have to dig all the way
down through the DNS hierarchy to make sure you get it all), then on each DC
(one at a time) run the following commands:
net stop netlogon
ipconfig /flushdns
ipconfig /registerdns
net start netlogon

That will flush the DNS Resolver cache, then register the machine's IP
address with the DNS Server. Then when NETLOGON starts it registers the
Active Directory specific DNS records.

Give it a few minutes and see if you can access each DC from the other, as
well as replicate AD. If that works, then reboot the clients and make sure
that they're working fine.


--
Mike Shepperd
Sunfire Solutions LLC
Seattle, WA

[This posting is provided AS-IS, with no warranties and confers no rights]

 

[hemina.modi]

hai...thanks a lot for rly...
bt untill and unless one root server working ok i can't shutdown
another one.
b'coz so many users suffer problem related logon script and mapping
drive.
and there was no sharing of sysvol in Root server which is new domain
controller.
in Dcdiag it indicate the error 1533 and also GC coudn't located all GC
down..


hai tell me one thing it is surly related DNS problem or smthing else.
b'coz frs service is also not working.even if i open domain controller
security policy by domain admin it shows u do not have sufficent right
or i can't check resultant set of policy on administrator to check
rights.it shows same error.

waiting for rly..

Wow!

I'm not sure why you would take those steps in the first place, but assuming
you had a compelling reason to do so, lets try to get it working again.

First, pick one DNS server to point both DC's at and only use that one
server, don't have an alternate. Then go into the DNS Management console
and delete all of the entries for those DC's (you'll have to dig all the way
down through the DNS hierarchy to make sure you get it all), then on each DC
(one at a time) run the following commands:
net stop netlogon
ipconfig /flushdns
ipconfig /registerdns
net start netlogon

That will flush the DNS Resolver cache, then register the machine's IP
address with the DNS Server. Then when NETLOGON starts it registers the
Active Directory specific DNS records.

Give it a few minutes and see if you can access each DC from the other, as
well as replicate AD. If that works, then reboot the clients and make sure
that they're working fine.


--
Mike Shepperd
Sunfire Solutions LLC
Seattle, WA

[This posting is provided AS-IS, with no warranties and confers no rights]

hello,
We have one server as domain controller named as PDC
second one is additional domain controller named as ROOT
then we first transfer all role .then after 15 mins change ip of both
server.
so it shows error that domain controller coudn't found.
Then we again make change and set it is as before then after we
transfer gc.
bt now sysvol didn't share bydefault after role transfer and logon
script is not running.
then we run dcdiag it show's gc couldn't located and all gc are down.
and also frs service stop autometically...
now users suffer no problem b'coz both pdc and root is on bt as we
shutdown pdc
they indicate error in logon script.
wt should we do to stable our domain controller.

 

[Paul Bergson [MVP-DS]]

Unless you have multiple domains, just make both Domain Controllers, Global
Catalog Servers.

Which DC(s) are dns servers? Make sure that the client properties on your
DC's point to a dns server and if the dc is running dns services, point it
to itself.

run netdiag /fix (Or restart the NetLogon Service) to clear up any dns
issues related to the dc.

From your dc try running dnslint /ad /s "ip address of your dc"
The above will list any errors relating to Active Directory and DNS

See how this plays out

--
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.