We just replaced one of our domain controllers with a brand spankin new rack mounted IBM eServer. We were like kids at Christmas time opening the huge box and gawlking at the beautifull insides. Installation went well, for the most part.

Server2003

The server we replaced had Microsoft Exchange running on it, DNS and IIS hosting a website. The Exchange database had some corruption to it and had to be repaired but it went well. Once we got it up and running and made it a domain controller, installed Exchange, restored the Exchange database, got the website up and running and a couple of other applications it needed it purred away and was right at home. Then a couple of days later we added the first user to our domain since the upgrade and for some reason we couldn’t log on with it. After some looking and checking out the event viewer we noticed errors with the Active directory replication service. Apparently the two domain controllers were not on speaking terms with one another. Research was pointing to DNS as the cause and how Windows Server 2003 handles active directory replication following an unsuccessful DNS lookup.

eserver

From Microsoft’s support site it appears that Server 2003 with Service Pack 1 (which I thought was on both boxes) handles this much better. So after I figured out that one of the servers didn’t have Service Pack 1 I installed it rebooted and the two Servers decided they were on speaking terms after all. I think we need to do some diving into the workings of the DNS problem but for now it’s working!