AD Replication

[summit]

Hello All-

We have small network: 1 DC, 1 member server, and 6 workstations running
w2k pro. I decided to make the member server another DC for redundancy so I
did dcpromo and the upgrade seemed to work fine. When I checked AD Users
and Computers on the new DC I saw that all the Computers and Users were
accounted for. However, when the new DC is powered on, the W2k pro machines
can not log on. As soon as I turn off the server, everything is fine.
What did I forget to do or what did I do wrong. Thanks in advance for any
help.

 

[Guest]

Did you make the new DC a member of the existing domain?
What error do you receive when the clients logon? Can a
domain admin logon even though the users cannot?

 

[Cary Shultz [A.D. MVP]]

Summit,

I might start by making the 'new' Domain Controller a Global Catalog Server.
This way you will have two in your smaller environment. I would also add
DNS to the 'new' Domain Controller and make sure that both are running AD
integrated DNS. Additionally, I would make sure to update the DHCP Server
'Options' so that the 'new' Domain Controller - which is now running DNS -
information is included in the IP Address lease information. You might want
to then reboot the client systems and see what happens.

I do not think that you forgot anything thing or did anything incorrectly.
I would do the Global Catalog thing and DNS thing and go from there.

As 'anonymous' stated, can a user account that is a member of the Domain
Admins log on with the second DC up and running? while the 'regular' user
accounts can not?

Here is a good general tip: install the Support Tools on both of your
WIN2000 Domain Controllers. The Support Tools can be found on the WIN2000
Server CD as well as on the WIN2000 Service Pack CD ( in both cases in the
Support | Tools folder ) or download the Support Tools from the MS website.
Then run dcdiag /v and netdiag /v. I would also run repadmin /showreps to
check out the replication objects. Again, these are general tips.