javax.naming.ServiceUnavailableException when using JNDI to access LDAP

Using a InitialDirContext object, searching Active Directory fails. Specifically I'm using the .search method and the error occurs when executing the NamingEnumeration.hasMore method.

The error is that a javax.naming.PartialResultException is throw reporting that the root cause was a
javax.naming.ServiceUnavailableException: testdomain.net:389; socket closed.

I've verified that the environment I'm using to establish the InitialDirContext is correct (user,pass,url).  
Also verified that the LDAP query I'm passing the search method is valid and returns results (execute ldapsearch from command-line).

What could be causing my socket connection to close?

Thanks,
Ron
nub99Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Mayank SAssociate Director - Product EngineeringCommented:
>> What could be causing my socket connection to close?

Probably incorrect authentication credentials.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Java EE

From novice to tech pro — start learning today.