How to Specify ADSI Paths

 Keywords:

LDAP

This is a namespace implementation that is compatible with Lightweight Directory Access Protocol (LDAP).

LDAP ADSI Path format: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adsi/adsi/ldap_adspath.asp

Distinguished Names Explained: http://www.ietf.org/rfc/rfc1779.txt?number=1779

The Microsoft LDAP provider ADsPath requires the following format.

LDAP://HostName[:PortNumber][/DistinguishedName]

Note [ ] denotes optional parameters; it is not a literal part of the binding string.

The HostName can be a computer name, an IP address, or a domain name. A server name can also be specified in the binding string. Most LDAP providers follow a model that requires a server name to be specified.

The PortNumber specifies the specific port that should be used for the connection. If no port number is specified, the LDAP provider uses the default port number. The default port number is 389 if not using an SSL connection or 636 if using an SSL connection.

The DistinguishedName specifies the distinguished name of a specific object. A distinguished name for a given object is guaranteed to be unique.

The following table lists examples of binding strings.

LDAP: ;Bind to the root of the LDAP namespace. 
LDAP://server01 ;Bind to a specific server. 
LDAP://server01:390 ;Bind to a specific server using the specified port number. 
LDAP://CN=Jeff Smith,CN=users,DC=fabrikam,DC=com ;Bind to a specific object. 
LDAP://server01/CN=Jeff Smith,CN=users,DC=fabrikam,DC=com ;Bind to a specific object through a specific server.

WinNT

This is a namespace implementation that is compatible with Windows NT�/Windows� 2000.

WinNT ADSI Path format: http://msdn.microsoft.com/library/en-us/netdir/adsi/winnt_adspath.asp?frame=true

The ADsPath string for the ADSI WinNT provider can be one of the following forms:

WinNT:
WinNT://<domain name>
WinNT://<domain name>/<server>
WinNT://<domain name>/<path>
WinNT://<domain name>/<object name>
WinNT://<domain name>/<object name>,<object class>
WinNT://<server>
WinNT://<server>/<object name>
WinNT://<server>/<object name>,<object class>

The domain name can be either a NETBIOS name or a DNS name.

The server is the name of a specific server within the domain.

The path is the path of on object, such as "printserver1/printer2".

The object name is the name of a specific object.

The object class is the class name of the named object. One example of this usage would be "WinNT://MyServer/JeffSmith,user". Specifying a class name can improve the performance of the bind operation.

NDS

This is a namespace implementation that is compatible with Novell NetWare Directory Service (NDS).

NDS ADSI Path format: http://msdn.microsoft.com/library/en-us/netdir/adsi/nds_adspath.asp?frame=true

An ADsPath string for the ADSI NDS provider starts with either "NDS:" or "NDS://<>", where <> is an NDS provider path. For example:

NDS:

NDS://ndsServer/O=Internet/DC=COM/DC=Fabrikam/DC=DEV/CN=TopHat

NWCOMPAT

This is a namespace implementation that is compatible with Novell NetWare 3.x.

NWCOMPAT ADSI Path format: http://msdn.microsoft.com/library/en-us/netdir/adsi/nwcompat_adspath.asp?frame=true

An ADsPath string for the ADSI NWCOMPAT provider starts with either "NWCOMPAT:" or "NWCOMPAT://<>", where <> is an NWCOMPAT provider path. For example:

NWCOMPAT:

NWCOMPAT://binderyServer/TopHat

Article ID:   W15816

File Created: 2006:04:10:11:12:44

Last Updated: 2006:04:10:11:12:44

Database Search

TechHome