F
flya750
I have two AD domains.
Server A (Domain controller, first AD server in Forest, running "abcinc.com"
Server B is an upgraded NT 4.0 PDC running "abc.com" domain
However when Server B was upgraded to Windows 2000 and AD was installed the
server name had an incorrect DSN domain name suffix. abc.xxx.net
Server B was running and authentication was working but not fully because of
the bogus domain suffix.
This is where a dumb thing happened. I went into the the registry Server B
the "abc.com" domain controller server and found all entries of
"abc.xxx.net" and change it to "abc.com". Trying to essential remove all
"abc.xxx.net" references. Well now I have broken AD. When I start AD
application I get an error saying:
"Naming services cannot be located because the server is not operational. "
I tried to go back into the registry and undo the dumb thing...but that
didn't fix it. I deleted the DNS zone "abc.com" and recreated it. But
still did not fix it. I'm still seeing remnants of the bogus abc.xxx.net
suffix.
This server was the PDC of the second domain and I still have a BDC running
NT 4.0. Can I just run DCPROMO on the screwed up server....remove AD and
reinstall AD again? Will this fix it.
I'm Assuming that since Server A was the first server in the forest that is
will remain the Global Catalog server and all will be fine.
Please help and ...yes I know not to hack at the registry....silly me.
d
Server A (Domain controller, first AD server in Forest, running "abcinc.com"
Server B is an upgraded NT 4.0 PDC running "abc.com" domain
However when Server B was upgraded to Windows 2000 and AD was installed the
server name had an incorrect DSN domain name suffix. abc.xxx.net
Server B was running and authentication was working but not fully because of
the bogus domain suffix.
This is where a dumb thing happened. I went into the the registry Server B
the "abc.com" domain controller server and found all entries of
"abc.xxx.net" and change it to "abc.com". Trying to essential remove all
"abc.xxx.net" references. Well now I have broken AD. When I start AD
application I get an error saying:
"Naming services cannot be located because the server is not operational. "
I tried to go back into the registry and undo the dumb thing...but that
didn't fix it. I deleted the DNS zone "abc.com" and recreated it. But
still did not fix it. I'm still seeing remnants of the bogus abc.xxx.net
suffix.
This server was the PDC of the second domain and I still have a BDC running
NT 4.0. Can I just run DCPROMO on the screwed up server....remove AD and
reinstall AD again? Will this fix it.
I'm Assuming that since Server A was the first server in the forest that is
will remain the Global Catalog server and all will be fine.
Please help and ...yes I know not to hack at the registry....silly me.
d