Thanks for the reply. I came across your experiences while searching several times yesterday and tried some of the things suggested to you at the time.
> Are you able to connect using a LDAP client (JXplorer for example)? Yes, and I also have another web server which is using that AD for it's user accounts which also works fine. > I ask this because I saw multiple threads related to this error > (http://www.chicagotech.net/troubleshooting/evenyid13568.htm). > And if you are using 636 port (SSL/TLS connections) you need to import > Ldap server certificate in sipX, but I'm not sure if 4.2.1 version of sipX > permits this thing. Testing from sipx, the only connections going out to the AD are port 389. Based on the thread I found of your problem, I also checked to see if it might be because it was trying a TLS connect but it's not. I also tried that port to be safe and even installed a self signed cert on the MS AD which made no difference. I've yet to come across any information which helps much. Everything I've tried so far doesn't seem to change the error message I'm seeing which I'm starting to suspect is a java issue on sipx from what I'm reading. Issue only in that there may be a file which needs to be edited but I'm not a java guy so don't know. "2010-12-29T04:09:29.966000Z":233:JAVA:WARNING:sx.mydomain.com:P1-18:00000000:LdapContextSource:"Property 'userName' not set - anonymous context will be used for read-write operations" _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
