We've finished a migration from Exchange 5.5 to 2003 on a Windows 2000 AD domain. During the move, I had installed temporary domain controller servers in each of our 2 sites, with plans to promote the old 5.5 servers to domain controllers after removing Exchange 5.5 from them.
The old 5.5 servers are now DCs, with all FSMO roles transferred to them. I've demoted the temporary DC in one of the sites, and now the Exchange server in that site gives the following error from the "MSExchangeAL" source:
"LDAP Bind was unsuccessful on directory tempdc.domain.org for distinguished name ''. Directory returned error:[0x51] Server Down."
This error pops up roughly every six hours, and the following Windows error appears about every 2 hours (from the source "Lsasrv"):
"The Security System could not establish a secured connection with the server cifs/tempdc.domain.org. No authentication protocol was available."
Do I somehow need to force the server to start looking directly at the permanent DC in that site?
The old 5.5 servers are now DCs, with all FSMO roles transferred to them. I've demoted the temporary DC in one of the sites, and now the Exchange server in that site gives the following error from the "MSExchangeAL" source:
"LDAP Bind was unsuccessful on directory tempdc.domain.org for distinguished name ''. Directory returned error:[0x51] Server Down."
This error pops up roughly every six hours, and the following Windows error appears about every 2 hours (from the source "Lsasrv"):
"The Security System could not establish a secured connection with the server cifs/tempdc.domain.org. No authentication protocol was available."
Do I somehow need to force the server to start looking directly at the permanent DC in that site?