Discussion Locked

Problems adding Second Domain Controller

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have a Windows 2000 server domain controller. It's the only one in the office. We have a freeBSD computer and it works as a DHCP, gateway and DNS server. The workstation's network setting are set to: obtain automatic IP and DNS, DHCP enable. The server has a static IP and the DNS settings point to the freeBSD DNS server. Everything works fine. I added a second windows 2k server domain controller. The initial installation goes fine. I assigned to it a static IP and the DNS setting point to the freebsd DNS server.
I promoted the new box to "additional domain controller". It starts the Active directoty transfer and then it says there was an error and needs to restart and it will continue after the reboot. Everything seems to work fine but I can only logon as administrator. I can't logon as another user even if the user has administrative rights. Once I logon, I go to AD of users and computers and when I try to see the properties of Administrator I get an error message sayingthat the Global Catalog server couldn't be found. I am sure the first server is the Global Catalog. I then tried to demote the new server but I can't. I get an error message about problems with the DNS zones. Looks like the new server is not synchronized with the other server. Any ideas?

5 replies

by 4u21der

You need to point your BDC to the DNS server of your Win2k network. It sounds like you are pointing it to the FreeBSD DNS server and that server has no knowledge of the Internal AD DNS structure.

You need to be running a seperate DNS server for your internal stuff and have a forward lookup record on your External DNS Server.

All your Win2k clinets should point to the internal DNS server and let it forward unknow host request to the FreeBSD server.

Hope this helps.

Good Luck!

by 4u21der

You need to point your BDC to the DNS server of your Win2k network. It sounds like you are pointing it to the FreeBSD DNS server and that server has no knowledge of the Internal AD DNS structure.

You need to be running a seperate DNS server for your internal stuff and have a forward lookup record on your External DNS Server.

All your Win2k clinets should point to the internal DNS server and let it forward unknow host request to the FreeBSD server.

Hope this helps.

Good Luck!

This discussion is closed to new replies.