This problem will be quite evident by the GC and the RUS counters being greyed out, logs show that LDAP bind is failing.
The IP Address listed in the Logs is not the correct IP Address for Exchange
Manual LDAP Binding works fine.
11/10/2006 15:26:15 PM TID(4040) e2kproxy.exe UtilityFunctions.cpp(36) : Server name is <Netbios Name>
11/10/2006 15:26:15 PM TID(4040) e2kproxy.exe UtilityFunctions.cpp(83) : The domain name is <Domain Name>
11/10/2006 15:26:15 PM TID(4040) e2kproxy.exe UtilityFunctions.cpp(84) : The domain controller name is <IP ADDRESS>
11/10/2006 15:26:15 PM TID(4040) e2kproxy.exe Connection.cpp(105) : Trying to connect to Active Directory on on <IP ADDRESS> on port 389
11/10/2006 15:26:36 PM TID(4040) e2kproxy.exe Connection.cpp(126) : ldap_bind_s failed because Server Down (81)
This can happen when there is more than one Network Connection configured. We use the default address to connect to LDAP, and therefore the GC and the RUS.
To resolve this issue, you must set the proper connection to be the default in windows.
This is done by following the steps below:
Open up Network Connections.
Click the Advanced Pull Down Menu.
Choose Advanced Settings.
You should see all of your connections under the Adapters and Bindings Tab.
Move the connection to the top that you want to be the default connection.
There are other reasons why these counters are grayed out, ie Authentication and Physical Connectivity.
This solution assumes that there is connectivity to the Exchange Server, and LDAP is binding fine manually from the SOE system.
If this does not resolve your issue, please contact Quest Support at firstname.lastname@example.org.