Not quite sure what Format you are using but I have a server that is attached to the Domain but is not using any AD credentials at the moment for ePO or DLP.
When I get to enter the credentials I use below
Also something that may help you if I put the wrong username or password in I get the error cannot find forest: ' ' so not sure if that error is really worth chasing.
I've not had chance to check the connection information but I assume that it will be 389 or maybe 636 for Secure LDAP.
Thanks for your response Ian. I have done some wireshark testing and found that when I enter the credentials and click on OK, the ePO server makes a UDP port 139 request to find the forestname 1C name (netbios domain name).
So I worked out the lmhost file in my etc folder to make the IP address of one of my dns servers the 1C name. I then clicked Ok again and it failed really quick. In the wireshark packet it said that I failed authentication. It also listed the ROOT Forest, as my current domain is one of the many domains. I don't have an account in the root forest.
So I called someone who did have an account in the Root forest, he entered the root forest name into his own LMHOST file because he was having the exact same issue and his credentials in the root forest. It cranked away and found the root forest and listed the OU's within. He could not traverse back into his domain from there to grab his groups/accounts.
IMO, I really was hoping that this product would have grabbed users and groups the same way ePO did via LDAP.
Problem has been resolved by accessing the DLP console not from the server but from a client accessing the ePO server via a web console and internet explorer. Apparently there are software restrictions on the server that prevent these com's.