05-30-2008 06:51 AM - edited 03-09-2019 08:48 PM
Hi, I am currently trying to seutp LDAP authentication for my Clean Access Agents but having some difficulty on the AD Side. Using an administrators credentials, I have added the Auth Server and using the same credentials I can do the Auth Test on this AD Server. If I try to do the Auth Test with a regular user however, it fails with a naming Error. The Userid I am testing with has an underscore as part of the name, has this ever been known to cause problems with AD? I have no experience with ldap so relying on our server guys to provide the information.
06-05-2008 07:26 AM
These problems usually come down to ports not being open on the clean access server that the workstation is attempting to use while loading the profile. So, make sure the following ports are open:
For each domain controller open the following ports:
TCP 88
TCP 135
TCP 389
TCP 445
TCP 1025
TCP 1026
UDP 88
UDP 389
UDP 636
Icmp to all domain controllers in the infrastructure NTP to all domain controllers
06-05-2008 07:38 AM
Hi Sam, Thanks for the reply. There is no firewall between the Manager and the Domain Controllers. Is there any specific level of access needed other than domain users, to be able to authenticate against ldap? I got our server guy to authenticate successfully with a domain admin ID and a slightly lower level of authorization ID, however my ID and my colleague's ID which are regular Domain Users only, cannot authenticate. I have done single finger typing of password also to make sure it is not Large Thumb Syndrome :)
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide