Ask the Expert

Problems on a mixed Exchange 5.5 and 2000 network

We have a mixed Exchange 5.5 and 2000 network. Currently, we have one Exchange 5.5 server and one Exchange 2000 server. On the Exchange 2000 server, by default SRS is installed. Recently, we introduced a second Exchange server into the site. While configuring the SRS on the second E2K server it, simply hangs and gives the below error. We could not see this E2K server from Exchange 5.5 admin console, but we can see it from Exchange 2000 ESM.
=================================
Attempting to add the replica for the /o=testorg/ou=site/cn=Microsoft DMD
Naming Context, to server MSsite2
[00:22:43] Entering ScAddNCReplica
[00:22:43] Entering Sc_dra_replica_add
[00:22:43] Attempting to add a replica of naming context
/o=testorg/ou=site/cn=Microsoft DMD, from Server MSsite3 to Server MSsite2
[00:22:44] Replication encountered a connection failure error.
[00:22:44] Replication encountered a recoverable error. About to sleep for 1 seconds.
[00:22:45] Attempting to add a replica of naming context
/o=testorg/ou=site/cn=Microsoft DMD, from Server MSsite3 to Server MSsite2
[00:22:46] Replication encountered a connection failure error.
[00:22:46] Replication encountered a recoverable error. About to sleep for 3
seconds.
===============================
Running netdiag on the second E2K server shows everything is fine, but on the first E2K server we are getting the below error.
===============================
Kerberos test. . . . . . . . . . . : Failed
        [FATAL] Kerberos does not have a ticket for srv3$.
LDAP test. . . . . . . . . . . . . : Failed
    [WARNING] The default SPN registration for 'HOST/srv3.site.testorg.com'
is missing on DC 'dc3.site.testorg.com'.
    [WARNING] The default SPN registration for 'HOST/srv3.site.testorg.com'
is missing on DC 'dc1.site.testorg.com'.
    [WARNING] The default SPN registration for 'HOST/srv3.site.testorg.com'
is missing on DC 'dc2.site.testorg.com'.
         [FATAL] The default SPNs are not properly registered on any DCs.

=======================================

    Requires Free Membership to View

The symptoms listed in the excerpt of your setup log file seem to indicate some sort of network issue. There are several different networking issues that could cause this problem, including host name resolution failures, incorrect DNS settings, etc. Given that your system also failed some of the basic NetDiag tests, I would start by resolving the failed tests.

For example, can the new Exchange server and your DC ping each other by their IP address? How about by their fully-qualified domain names? If you use NSLookup, do you see the appropriate records in DNS for the new Exchange server? If, after examining everything, you don't find anything that is configured incorrectly, you might want to run a network capture while re-running Setup on this system. This will show you what systems the new server is communicating with and it will also show you any problems that you might have (e.g., name resolution errors, etc.)

This was first published in February 2004

There are Comments. Add yours.

 
TIP: Want to include a code block in your comment? Use <pre> or <code> tags around the desired text. Ex: <code>insert code</code>

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
Sort by: OldestNewest

Forgot Password?

No problem! Submit your e-mail address below. We'll send you an email containing your password.

Your password has been sent to: