Authentication

Hi Stuart James

Please disable AD SSO under Device Access and share the feedback 

Regards

Hi Stuart James  Thank you for reaching out to the Sophos community team. Please check nasm.log around this error message time to get reason on this one and based on those error message further course of action can be taken to fix it.

Hi Stuart James Thanks for sharing the snapshot for the nasm.log. From this log lines not getting clues on the cause side, so would suggest collecting nasm.log by putting nasm in the debug mode.

> To enable/disable debug for nasm service use the following commands - service nasm:debug -ds nosync
> To check the service status - service -S | grep nasm
Then change to the log directory using the command cd /log.
> To check the live logs - tail -f nasm.log
> To check the older logs - less nasm.log

Was it working fine previously or is it a new setup where you are observing this error? Also if it is a break-fix where all of a sudden it stopped working then I would suggest logging a support case to investigate it further if no changes on firewall or server end.

The document says to turn it on: https://docs.sophos.com/nsg/sophos-firewall/18.5/Help/en-us/webhelp/onlinehelp/AdministratorHelp/Authentication/HowToArticles/AuthenticationKerberosTurnOn/index.html#set-primary-authentication-method

This is a new setup.

I turned debug on and looked at the logs, but it just fly's past too quickly and I cant see anything

Hi Stuart James 

AD SSO can have problems if the DNS is incorrect.  In general, the AD server should be specified by FQDN and should be resolvable.  There are some special DNS records that computers need to have in order to join the domain. 

Regards