Guest User!

You are not Sophos Staff.

Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 28 subscribers
  • Views 13082 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Client authentication fails after MR2.

Slawski

I have noticed that Client Authentication Agent on a Mac fails to automatically authenticate me to the firewall after wake-up. It started to occur after upgrade to MR2.

Anyone else observing that behaviour? On a different platform?



Edited Tags
[edited by: Erick Jan at 11:52 PM (GMT -7) on 15 Sep 2022]
Parents
  • 0

    Hello,


    I'm experiencing the same issue on my both computers, as soon as I did the upgrade to MR2.

    As I'm using Sophos at home, I can't explain to my family how to force reconnection, and I did go back to MR1.1 to avoid this problem.


    Billy

  • 0 in reply to PhilippeGressier

    As a workaround make static DHCP leases and define Clientless users. This will fix policy assignments without client authentication agent. I think that it is sufficient in most home-use scenarios.

    I returned to MR2 and have used to those disconnects (my computer is the only not using clientless access because I'm testing different policies and switch them on will).

Reply
  • 0 in reply to PhilippeGressier

    As a workaround make static DHCP leases and define Clientless users. This will fix policy assignments without client authentication agent. I think that it is sufficient in most home-use scenarios.

    I returned to MR2 and have used to those disconnects (my computer is the only not using clientless access because I'm testing different policies and switch them on will).

Children
No Data