The login policy needs to be explicit, not all (the manual I think is wrong there). LDAP takes over the explicit usage. If you login with SA, the LDAP TPS authentication still looks you up as if you were explicit, not via LDAP, so you need a 'proper' account to test with. The username you enter is the LANDesk explicit login and the password is the LDAP password that corresponds to the network connection entry. The network connection values are the LDAP distinguished name and in my experience need to be the first entries in the list of authentication strings. Any AD ones need to come after this. Values would be something like ...
Göran and I work on the same problem.
I have set up explicit login, but still get the same error message. I think I have a problem with the network login string or the ldap directory authentication string.
I'm not sure on what will be on both places.
Can you take a quick peek at http://community.landesk.com/support/message/67569#67569
and just see if the network login string or the directory string is completely messed up.
I would really appretiate it.
I think this issue was similar to the other issue detailed here - http://community.landesk.com/support/message/74988.
I resolved my issue by setting the <AuthenticationType> to 'Secure' in the DirectoryServiceAuthentificationConfiguration.xml file and copying some missing DLLs from the Framework folder to the WebAccess folder.