Terminal server and Active Directory replication issues
Posted on 2005-03-24
It's been a long and winding road to get where I am now sow I'll skip all that and get right to the current status. My client has a pair of W2000 servers. #1 contains SQL 2000, DNS, TS licensing server, DHCP and ADC. #2 contains Exchange 2000, DNS, and ADC. The also have a Terminal Server.
The AD replicas between #1 and #2 are not syncronized. I suspect the rest of the sysptoms I'm going to describe are related to this.
1. When login as Administrator, bring up DNS on #1 and attempt to manage #2 I get an "Access Denied" error. Going from #2 to #1 works OK. From the Terminal server if I bring up Computer Management and try to connect to #2 it says Access Denied. #1 comes up OK.
2. Periodically the log on #2 contains a 13508 FRS error.
3. Exchange System Attendant would not start until I changed it from System account to Administrator.
Exchange then worked except that no one had access to Public folders. Mid afternoon it stopped sending and recieving mail. I restarted the server and now the System Attendant will not start.
4. Every couple of hours the log has a "couldn't contact the global catalog" error.
5. All the logs are filled with 3034 errors.
6. Terminal server was giving a "can't find a licensing server" error. I added the registry value to point to it and that error went away. However, everytime a non-2000 client trys to connect it refuses and puts an "unable to issue a Terminal server license" error in the log.
I am going out tomorrow with the idea of demoting #1 and promoting it again to see if it will replicate. I am offerring 500 points for urgency and difficulty. My questions are:
Is it reasonable to think that all these problems stem from the AD inconsistancy?
Is the demote-promote idea to restablish replication also reasonble?
Is there any other problem that these symptoms would point to?
Is there a way to tell exchange to use the other DC as a global catalog?