- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
07-24-2011 02:20 AM
Hi
has anyone encountered the following error.
When i type the following command
enayat@fw-tec1-pa2050>show user ldap-server state
07-24-2011 07:59 PM
My guess is that the BIND DN isn't working because you didn't specify the complete path to where the service account is located. Since it can't find the account, it triggers an invalid credential error.
When you entered the BIND DN, did you include the complete path where the service account is located?
For example, in our environment the service accounts are located under the Accounts OU in AD.
So the bind DN would be cn=serviceaccountname,ou=Accounts,dc=xyz,dc=com.
08-25-2011 12:05 AM
yes it is because of either the ldap service act password or the path,
BIJILESH.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!