Question : Restore of systemstate data and exchange databases. SA no longer comes up with error c007054b

Hello,

hope someone can give me some advices on this problem.
We are doing backups of our Exchange Server 2000, which is also domain controller with NTBACKUP. The Backup includes the system state data (Active Directory) and the whole C: System Partition (programs, winnt etc.) and the exchange databases.
I did a restore on a different computer for testing the case of a disaster:
- installed win2000 with sp4
- installed exchange 2000 with sp3
- did a restore of the systemstate and C: (went through without problems, can access Active Directory users and computers)
- did a restore of the exchange databases (also went through without errors)

Now my problem is, that the MS Exchange System Attendent is no longer starting. Well, I can see in the eventlog that it is starting, but then stopps with the following error:
Eventid 1005:
Unexpected error The specified domain either does not
exist or could not be contacted. Facility: Win32 ID no:
c007054b Microsoft Exchange System Attendant occurred.

Microsoft Knowledge Base says to this error:   http://support.microsoft.com/kb/252137/en-us
RESOLUTION
Ensure that a global catalog server is available. The procedure in the "More Information" demonstrates how make a Microsoft Windows 2000 domain controller a global catalog server.
(...)
4. Right-click the NTDS Settings object in the right pane, and then click Properties.
5. Click to select the Global Catalog check box.
(...)

Well, the check box is selected, so this means the server is a global catalog server. Only Exchange seems not the be able to contact it ... Has anyone an idea how to resolve this problem?
Thanks in advance,
Thomas

Answer : Restore of systemstate data and exchange databases. SA no longer comes up with error c007054b

Hello Thomas,

Run DCDIAG /s: and NETDIAG and check if the Exchange can communicate with the GC or DC.
Kindly pipe the output of DCDIAG to a log file by using command DCDIAG /s: /v  c:\DCDIAG.log   and
NETDIAG /v > c:\netdiag.log

POST the output here and let's find out if there is some config changes in AD...

Regards.