I am trying to view our Base Dn with LDP, so when I go to connectionless enter the server info, then Bind enter the information I get this error message "res = ldap_bind_s(ld, NULL, &NtAuthIdentity, 1158); // v.3 {NtAuthIdentity: User='Administrator'; Pwd= <unavailable>; domain = ''.} Error <2>: ldap_bind_s() failed: Protocol Error. Server error: <empty>" Do you guys know what this could mean?

Hello, you can try to ask here: http://social.technet.microsoft.com/Forums/fr-FR/ITCG/threads This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration

Thanks, if I cannot get the LDP program to work can I use Adsi edit to view my base DN?

Hi, Please provide us more information on the issue and your requirements. For more information on how to use the LDP tool, please refer to the following link: Using Ldp.exe to Find Data in the Active Directory http://support.microsoft.com/kb/224543 If any error is received when using the tool as instructed or any error in the LDP printout, please write down the detailed error message here for research. Thanks. NinaPlease remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

Just try to pass on the credentials. If that works you know what the problem is.

Well the reason I need to find out our DN is because I need to know this information because we are trying to setup HTTPS/Profiles with our firewall for authentication. So our firewall must know which users to allow access to certain websites, the firewall must know what is the name of our AD database, so this is why our firewall must know the name of our Base DN. But like I said when we try to use LDP.exe to find this info out when I try to bind to that server this error message keeps coming up. res = ldap_bind_s(ld, NULL, &NtAuthIdentity, 1158); // v.3 {NtAuthIdentity: User='Administrator'; Pwd= <unavailable>; domain = ''.} Error <2>: ldap_bind_s() failed: Protocol Error. Server error: <empty>"

I am trying to view our Base Dn with LDP, so when I go to connectionless enter the server info, then Bind enter the information I get this error message "res = ldap_bind_s(ld, NULL, &NtAuthIdentity, 1158); // v.3 {NtAuthIdentity: User='Administrator'; Pwd= <unavailable>; domain = ''.} Error <2>: ldap_bind_s() failed: Protocol Error. Server error: <empty>" Do you guys know what this could mean? Base DN is just a path where your Firewall wants to know which path in active directory it needs to search for your users. "OU=Users,OU=Chicago,dc=mydomain,dc=com" You're putting too much thought into it. BaseDN is a nothing more than a variable location in your AD structure, unique to each domain... Hopefully.... There is no "SET" baseDN. So if you have users in a specific directory tree that you want to allow, enter that OU path. The example above is the baseDN format for a mydomain.com domain... The Chicago OU and then the Users Child-OU in Chicago. Per say you want users from all sites to VPN to this server all together... Your baseDN just becomes "dc=mydomain,dc=com" If it doesn't like that.. you might be able to try a wildcard OU. "OU=*,dc=mydomain,dc=com" Hope that helps clarify what you need... You don't need ldp.exe to figure that out. It always seems to crash on me anyway... or I'm just too impatient to wait on that legacy app... Steve Kline Microsoft Certified IT Professional: Server Administrator Microsoft Certified Technology Specialist: Active Directory, Network Infrastructure, Application Platform, Windows 7 Microsoft Certified Product Specialist & Network Product Specialist Red Hat Certified System Administrator This posting is "as is" without warranties and confers no rights.

Your right I got it figured out, thanks for the help