[Xymon] LDAP test will not use nonstandard port

[John Thurston]

On 9/17/2015 10:57 AM, Scot Kreienkamp wrote:
> Hi all,
>
>
> I’m running an LDAP test against an Oracle LDAP server from xymon using
> this configuration:
>
> ldap://oud1.example.com:1389/DC=example,DC=com "ldaplogin=cn=admin:password"
>
> That test is failing with the error that it cannot contact the server.


I have the following line in my hosts:
> 0.0.0.0  foo.bar.com   # ldap://foo.bar.com:399/uid=someone,ou=people,o=bar.com?mail?base ldap://foo.bar.com:389/uid=someone,ou=people,o=bar.com?mail?base ldaps://foo.bar.com:636/uid=someone,ou=people,o=bar.com?mail?base

Broken up for easier reading:
0.0.0.0  foo.bar.com   #
ldap://foo.bar.com:399/uid=someone,ou=people,o=bar.com?mail?base 
ldap://foo.bar.com:389/uid=someone,ou=people,o=bar.com?mail?base 
ldaps://foo.bar.com:636/uid=someone,ou=people,o=bar.com?mail?base

My server is listening on ports 389 and 636. I have added the 399 test 
for diagnostics. The result is: 399 fails, 389, and 636 continue to 
work. In this instance, I'd say my ldap test is able to test against 
non-standard ports.

(Solaris 10 with Xymon 4.3.21)

Does yours behave any differently if:
A) you attempt an anonymous bind?
B) you wrap your entire "ldap...=com" portion in double-quotes?
C) you replace your bind attempt with a simple port check?

-- 
    Do things because you should, not just because you can.

John Thurston    907-465-8591
John.Thurston at alaska.gov
Enterprise Technology Services
Department of Administration
State of Alaska