Windows 2003 DC's not replicating, Access is denied
Posted on 2004-10-13
I have a small network with primarily Windows 2000 advanced servers providing web services with a back end MS SQL server cluster. I have two Domain Controllers with Active Directory installed. These two machines are Windows Server 2003 Enterprise Edition. AD is required for the SQL database cluster to work. The first DC machine has DNS services installed. When setting up this machine I just used the default wizard. The second DC was installed as the 2nd DC in the domain.
Machines are able to join the domain but then I keep seeing messages in security log of the DC Event ID 529: Unknown user name or bad password. This has primarily been from the 2nd DC server. I have not been able to reliably get the two machines to talk to each other. AD logon credentials for users work fine.
Using AD Sites and Services I have been able to force replication from the 2nd DC to the primary but not the other way. Right now I can't force a replication either way. I'm consitently getting 529 errors listing the 2nd DC IP address.
I was able to get the system working for about 4 hours today with no error messages. This afternoon the system started having problems again where replication wouldn't work. When I run repadmin /showreps I get the response"DSA operation failed because of a DNS lookup failure." The last successful replication was this morning at about 8am.
I have the 1st DC set up to receive the SQL backups from the server cluster. This has been working for about a week now but the process is now failing with the SQL service no longer able to use the drive. On the primary DC I'm now getting a 529 error Unknown user or Bad password listing the DB server IP address.
When the system failed I showed the DNS server having 4004,4015 errors.
One minute the services work fine, later everything just stops working. I'm at a loss on what to do to get the system stable. This is also on a production system where do to an older server failure we had to move the production DB over to the cluster sooner than I had planned.
Can someone point me in the right direction?
Please let me know if there are diagnostic tools that you need run to assist.