kishore_peddi
asked on
How to get the path to LDAP directory server on Local Machine ?
Hi,
I have followed the below link for Forms Authentication using Active Directory (ASP.NET using VB.NET).
http://support.microsoft.com/default.aspx?scid=kb;EN-US;326340
Can you please tell me how to make this sentance :
Dim adPath as String = "LDAP://DC=..,DC=.." 'Path to your LDAP directory server
for my local computer ?
As i am using my local computer how can i pass the path ?
Thanks,
Kishore
I have followed the below link for Forms Authentication using Active Directory (ASP.NET using VB.NET).
http://support.microsoft.com/default.aspx?scid=kb;EN-US;326340
Can you please tell me how to make this sentance :
Dim adPath as String = "LDAP://DC=..,DC=.." 'Path to your LDAP directory server
for my local computer ?
As i am using my local computer how can i pass the path ?
Thanks,
Kishore
You can use:
localhost
127.0.0.1
or your IP Address
localhost
127.0.0.1
or your IP Address
ASKER
Hi michaelitrn ,
Can you please provide me whole syntax for this :
Dim adPath as String = "LDAP://DC=..,DC=.." 'Path to your LDAP directory server
by using
localhost
127.0.0.1
Thanks,
Kishore
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
If you do have it up and running it is like aponcealbuerne stated:
LDAP://localhost:389/DC=yo
LDAP://127.0.0.1:389/DC=yo
Be sure you have the DC correct.
Taken from:http://www.aspspider.com/rss/Rss15456.aspx
DC= should be followed by a domain nameDN, not a servername. If you want to
bind to DC1 in domain domain.com, you would use this:
LDAP://DC1/DC=domain,DC=co
If you use serverless binding, you would just use:
LDAP://DC=domain,DC=com
LDAP://localhost:389/DC=yo
LDAP://127.0.0.1:389/DC=yo
Be sure you have the DC correct.
Taken from:http://www.aspspider.com/rss/Rss15456.aspx
DC= should be followed by a domain nameDN, not a servername. If you want to
bind to DC1 in domain domain.com, you would use this:
LDAP://DC1/DC=domain,DC=co
If you use serverless binding, you would just use:
LDAP://DC=domain,DC=com
Hi Kishore
Unless the program will be running on your production AD server, it wouldn't be meaningful to have another instance of AD running locally in development machine. Because, during development there are some AD behaviours cannot be simulated locally.
Most importantly, this is the required LDAP path format
LDAP://HostName[:PortNumbe
Host name can be an ip address, a server name, a short dns name or a full qualified dns name. Rightfully, using full qualified dns is the best way so as to avoid some "unexpected" behaviours to happen. To use serverless path, the machine needs to join the domain.
PortNumber here, usually you can just ignore it. Unless your AD server uses non-default port number or using SSL connection.
DistinguishedName, can be any AD object (user, group, ou or rootDSE) depending on what you're trying to do.
Henry
Unless the program will be running on your production AD server, it wouldn't be meaningful to have another instance of AD running locally in development machine. Because, during development there are some AD behaviours cannot be simulated locally.
Most importantly, this is the required LDAP path format
LDAP://HostName[:PortNumbe
Host name can be an ip address, a server name, a short dns name or a full qualified dns name. Rightfully, using full qualified dns is the best way so as to avoid some "unexpected" behaviours to happen. To use serverless path, the machine needs to join the domain.
PortNumber here, usually you can just ignore it. Unless your AD server uses non-default port number or using SSL connection.
DistinguishedName, can be any AD object (user, group, ou or rootDSE) depending on what you're trying to do.
Henry
I do something like that using Azman
LDAP://yourdomain.com:389/
I think that if you aren't using azman just get rid of the OU like
LDAP://yourdomain.com:389/
hope helps.