Problems with AD authentication for users

Hi,

Thank you for the feedback.

Are you using NTLM authentication and CAA both?

Regards,

Deepti

Both, some NTLM and some CAA. 

Hi,

Have you enabled NTLM and installed CAA on the same client?

Regards,

Deepti

Th client can use NTLM as well, but in the past there was no problem.

Since the update SFOS 17.5 this message appears. So far I see the following in the Auth-Log:

The problem mostly occours when I'am getting connected to a VPN.

Also I've seen that the hearbeat status is getting RED. 

Why is hearbeat getting RED and where is this behavior configured?? HELP :)

Hi,

Logs seems are from Heartbeat as client means ESG client.

What exactly are you using ?

With CAA as a Client, you will get CAA in "Auth client" column in Logviewer and same as for "NTLM".

Also share the live user snapshot and ESG client version.

Regards,

Deepti

Here is the endpoint version:

What kind of snapshot you mean?

We need logviewer screenshot.

You have snapshot, which is indicating logs from ESG client(Heartbeat). We need logs, where "Auth Type" is NTLM & CAA which you have mentioned.

Something like that?:

Hi,

From Logs looks, NTLM channel has never been established. Please check your config on AD side.

Was it working on Sf 17.1?

As you mentioned , the logs where "Logged out by administrator", which i could not find in snapshot.

Sending you PM.

Regards,

Deepti

The NTLM error must be something else, the primary authentication is done via CAA.

But since the update to 17.5beta I see these logs, no login via CAA, instead HB.

There is no line about the "Logged out by administrator". If I try to match the timestamps it's seems to be the "wrong credentials" line in log.

Hi Roboto,

               Thanks for details,I will send you PM for more details.

Hi Roboto,

               Thanks for details,I will send you PM for more details.