Users created in AD with a first name and last name have a "cn=first<space>last" and the actual logon credentials are stored in "sAMAccountName=loginID". This presents a problem when a LDAP querry is passed from CiscoWorks LMS. When attempting to authenticate CiscoWorks LMS users against Microsoft Active Directory / LDAP, login credentials must be "first<space>last" rather than actual loginID. Desired configuration would be to reference SAMAccountName (loginID) rather than CN. I see CCO references to SAMAccountName under Unified Messaging and NAC documentation. But nothing under CiscoWorks documentation. Is this possible?
Nope, anonymous bind is not enabled. That's the source of my problem. Unfortunately, policy won't permit me to enable it either. I guess ACS appliance is the longer-term fix. In the meantime, I can change the user requiring this access. Thanks for your assistance.
Hi everyone, I would like to thank you in advance for any help you can provide a newcomer like myself!
Im studying the 100-105 book by Odom and am currently on the topic of Port security. I purchased a used 2960 and I'm trying to follow a...
While deploying a number of 18xx/2802/3802 model access points (APs), which run AP-COS as their operating platform. It can be observed on some occasions that while many of their access points were able to join the fabric WLC withou...
I am going to design and build an LAN network under a tunnel underground with long distance between the switches.
I will have 2 Catalyst switches and 8 Industrial IE3000, and they will be connected with fiber.
For now I am planning on use Layer-2 s...