G
Guest
Hi,
we have already an performanceproblem within our application.
If we start some tasks with our DB2-Client we couldn't act within our
application for an duration from 10 to 15 seconds.
Our sniffer on the network shows that lsass.exe use the lsarpc interface to
start the operation LsarLookupNames4 with the operation # 0x4d within this
time intervall against our Active Directory Controller.
It seems that the LsarLookupNames4 operation try to solve the SID.
Now my questions:
- Could someone explain me which process or something else triggers the
lsass.exe in order to produce this operation?
- When will these calls are generated? Is this regularly?
- Use an DB2 Connect this operation automatically?
- Could I manipulate this operation? If yes, how.
Thanx
we have already an performanceproblem within our application.
If we start some tasks with our DB2-Client we couldn't act within our
application for an duration from 10 to 15 seconds.
Our sniffer on the network shows that lsass.exe use the lsarpc interface to
start the operation LsarLookupNames4 with the operation # 0x4d within this
time intervall against our Active Directory Controller.
It seems that the LsarLookupNames4 operation try to solve the SID.
Now my questions:
- Could someone explain me which process or something else triggers the
lsass.exe in order to produce this operation?
- When will these calls are generated? Is this regularly?
- Use an DB2 Connect this operation automatically?
- Could I manipulate this operation? If yes, how.
Thanx