Exchange 2000 Service Pack 1 DSAccess improvements (304393)

MORE INFORMATION

• Change in slow server timeout
  Each Lightweight Directory Access Protocol (LDAP) request sent from an Exchange 2000 server to an Active Directory server is timed. In Exchange 2000, if the LDAP response takes more than five seconds to complete, that Active Directory server is marked as "slow" in the DSAccess server list. This makes DSAccess send future LDAP requests synchronously (one at a time), rather than asynchronously. This re-balances LDAP requests so the "fast" servers are used more often.
  
  In SP1, the five-second time threshold is reduced to two seconds. After SP1 is applied, potentially, more slow servers will be detected, therefore faster, local servers will be preferred for LDAP requests, making Exchange 2000 more responsive. Conversely, if the only Active Directory servers that your Exchange 2000 can use are over a wide area network (WAN) or are very slow to respond, all requests will be sent synchronously, which will have a severe, detrimental effect on Exchange 2000 performance. Microsoft recommends that Exchange 2000 servers have a high-bandwidth/low-latency network connection to at least one global catalog (GC) server.
• Failures when the first detected GC server is down
  In scenarios where DSAccess has detected that the first GC in the Working GCs list is down, the server acting as the configuration domain controller (DC) can also be marked as down even if it is available. This issue is fixed in SP1.