Discussion Locked

Exchange 5.5 on Win2k and ADC problems

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

We have an Exchange 5.5 server running on a windows 2000 Domain Controller,

It is currently the only DC we have,

However when we migrated from NT4 to 2K we setup a temp domain controller called "temp"

Now the temp domain controller is long gone and at that point I set the new server to the root and removed all instaces of "temp" using ADSI Edit,

Now I am trying to setup the Active Directory Connector for Exchange 5.5 in preperation for our migration to Exchange 2000 and when I run setup I get an error that setup cannot contact server "temp\".

there are still refrences in the registry under \HKLM\System\Current Control Set\Services\NTDS\Parameters, to the server "Temp" and I have even tried temporarly removing these refrences and seeing if it works, of course it doesn't.

So I am wondering two things,

Where is the ADC setup program pulling info about the servers?
how much freedom do I have to modify the NTDS key without blowing up my AD?

Thanks

8 replies

by rabbit_runner

This also happened to me. I am not at the location with the documentation to correct this. You will need to modify your AD. There is a utility to remove the offending computer. When I reach the location, I will find the document and give the details. It will take a few hours.

by rabbit_runner

Hi Again. I cannot find the article I had mentioned earlier. I have looked, but have not found it. Therefore, I am not certain how much I can help. In the meantime, backup the registry and try editing NTDS key. (But you have probably already tried this). Next double check your ADSI Edit for the TEMP computer. Particularlly under the Domain Controllers container. Third, make certain that your current domain controller is the PDC Emulator. To check this, open your Active Directory Users and Computers tool. right click on the Active Directory Users and Computers line and select Operations Master. Make certain that the PDC Emulator is set to your current Domain Controller. If you find that it is still set to the TEMP computer, changeit. Also change the RID master and Infrastructure Master. One last thing, Did you have the Exchange installed while the TEMP domain controller was active? If you did, then there will be some AD exchange settings which will still point to TEMP.

This is all that I can remember to have checked. If I find the article, I will make certain it is attached to this question.

Hope this may help you track down the problem.

by rabbit_runner

Another question...Check your DNS settings. Look under this location......
Forward Lookup Zones

_msdcs.
dc
_sites
Default-First-Site-Name _tcp
Check the hosts on the right hand side. Do you find any refference to the TEMP domain Controller? If you do, you will need to modify these, and also change your DNS to only recognize the current domain controller.

Check the rest of the DNS settings for any reference to TEMP.

Let me know if there is any reference to TEMP.

This discussion is closed to new replies.