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.

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 PhilippeGressier over 9 years ago

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
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 PhilippeGressier over 9 years ago

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
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 Slawski over 9 years ago 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).
Cancel
Vote Up 0 Vote Down

Cancel