Article ID: 253746
Article Last Modified on 9/23/2005
APPLIES TO
- Microsoft Site Server 3.0 Standard Edition
This article was previously published under Q253746
SYMPTOMS
The GetObjectAsUser method of the Active User Object (AUO) Membership.UserObjects object in Microsoft Site Server succeeds approximately fifty percent of the time when Clear Text/Basic authentication is required on the Lightweight Directory Access Protocol (LDAP) server.
For example, the following code demonstrates the problem:
<%
' Create our AUO object
Set oUser = Server.CreateObject("MemberShip.UserObjects.1")
' Connect to LDAP as the currently logged on user
Set oContainer = oUser.GetObjectAsUser("LDAP://server:389/o=Microsoft")
' Display a list of the main containers
For Each oItem In oContainer
Response.Write oItem.Name & " - " & oItem.ADsPath & "<BR>"
Next
%>
CAUSE
This behavior occurs because the AUO Membership.UserObjects object does not provide the correct authentication information to the LDAP server.
WORKAROUND
To work around this behavior, use Active Directory Service Interfaces (ADSI) rather than the AUO Membership.UserObjects object.
Example (Using Membership Authentication):
<%
' Connect to LDAP as a specified user
Set oLDAP = GetObject ("LDAP:")
Set oContainer = oLDAP.OpenDSObject ("LDAP://server:389/o=Microsoft", "cn=Administrator, ou=Members, o=Microsoft", "password", 0)
' Display a list of the main containers
For Each oItem In oContainer
Response.Write oItem.Name & " - " & oItem.ADsPath & "<BR>"
Next
%>
Alternatively (Using Windows NT Authentication)
<%
' Connect to LDAP as a specified user
Set oLDAP = GetObject ("LDAP:")
Set oContainer = oLDAP.OpenDSObject ("LDAP://server:389/o=Microsoft", "Administrator", "password", 0)
' Display a list of the main containers
For Each oItem In oContainer
Response.Write oItem.Name & " - " & oItem.ADsPath & "<BR>"
Next
%>
RESOLUTION
To resolve this problem, obtain the latest service pack for Site Server version 3.0. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
219292 How to Obtain the Latest Site Server 3.0 Service Pack
STATUS
Microsoft has confirmed that this is a problem in Site Server 3.0. This problem was first corrected in Site Server 3.0 Service Pack 4.
MORE INFORMATION
This problem only occurs on computers running Windows NT version 4.0.
Keywords: kbbug kbfix kbqfe kbsiteserv300sp4fix kbhotfixserver KB253746
