Microsoft KB Archive/193375

= LDAP Bind Fails if Computer Name Is Longer Than 11 Characters =

Article ID: 193375

Article Last Modified on 4/15/1999

-

APPLIES TO


 * Microsoft Site Server 3.0 Standard Edition

-



This article was previously published under Q193375



SYMPTOMS
The following Site Server Membership Broker errors may occur in Event Viewer if the computer name is longer than 11 characters and dynamic data replication is enabled:

Event ID 4107: The Site Server Authentication Service could not do an LDAP bind. Error: 49, virtual server number 2. If this happened during a reboot of the machine and the LDAP server is on the same machine, it is not critical. The Authentication Service will automatically recover from this problem when the first authentication happens.

Event ID 4102: The Site Server Authentication Service could not connect to the LDAP server. Error: 49, virtual server number 2. If this happened during a reboot of the machine and the LDAP server is on the same machine, it is not critical. The Authentication Service will automatically recover from this problem when the first authentication happens.



CAUSE
The computer name is greater than 11 characters.



WORKAROUND
Shorten the computer name to 11 characters or less, or make the first three to five characters of every computer name (NetBIOS name) unique.



STATUS
Microsoft has confirmed this to be a problem in Microsoft Site Server version 3.0.



MORE INFORMATION
The computer name is appended to MBSBRKR_ when the Membership Broker account is created during the setup of a membership instance. If the sum of the characters of this account exceeds the 20 character Windows NT account maximum, the account is truncated to 20 characters. This causes the Site Server Membership Broker errors to be generated when Membership servers participating in dynamic data replication attempt to communicate.

Keywords: kbbug kbpending KB193375

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.