Anonymous_User Absent Member.
Absent Member.
1245 views

LDAP tracing

How do I trace where an LDAP authentication call is coming from? The
connection address on the dstrace screen doesn't seem to correspond to any
IP address I'd be using.

Failed to authenticate local on connection 0x622930e0, err = failed
authentication (-669).



Labels (2)
0 Likes
4 Replies
Anonymous_User Absent Member.
Absent Member.

Re: LDAP tracing

What dstrace settings are you using?

Don

Kurt Ristow wrote:
> How do I trace where an LDAP authentication call is coming from? The
> connection address on the dstrace screen doesn't seem to correspond to any
> IP address I'd be using.
>
> Failed to authenticate local on connection 0x622930e0, err = failed
> authentication (-669).
>
>
>


--
D.Lohr
Technical Services
James Madison University

++ Bad command or file name ++
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: LDAP tracing

I was only using +Ldap. Edir 8.7.3. 10553.73.

Here's the scenario: We use ldap to authenticate several systems. I had one
user who kept getting her account locked by Intruder lockout. The intruder
address was the server we use for querying ldap, so I'm pretty sure that's
where it was coming from. I'd like to identify which system is causing the
problem, I figured the easiest way was determining the ip address of the
source.

Should I be using more / different switches, or a different tool?



0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: LDAP tracing

Kurt Ristow wrote:


> Should I be using more / different switches, or a different tool?


ConsoleOne | LDAP Server object | Screen options | check connection
information


--
Cheers,
Edward
0 Likes
Anonymous_User Absent Member.
Absent Member.

Re: LDAP tracing

> ConsoleOne | LDAP Server object | Screen options | check connection
> information

That's what I'm looking for.
Thanks.


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.