Customer has received an XGS-FW, previously used a SG.AD SSO was set up at orientation of Sophos-Com contribution. (docs.sophos.com/.../index.html
The following problem:
NTLM-Auth works without problemsKERBEROS fails: "Cannot initalize...".
NASM log says the following.
[nasm] initialize_kerberos(): realm = XXXX.LOCALDec 02 10:06:58.761799Z [nasm] system configured hostname [XX-XGS01]Dec 02 10:06:58.762319Z [nasm] initialize_kerberos(): gss_acquire_cred HOST/XX-XGS01@XX.LOCAL: No key table entry found for HOST/XX-XGS01@XXX.LOCAL
Does anyone have an idea ?
Translated with www.DeepL.com/Translator (free version)
Hey schmiegi ,Thank you for reaching out to the community, may we know the SFOS version ?
Thanks & Regards,_______________________________________________________________
Vivek Jagad | Technical Account Manager 3 | Cyber Security Evolved
Sophos Community | Product Documentation | Sophos Techvids | SMSIf a post solves your question please use the 'Verify Answer' button.
Hi, sorry. Its SFOS 19.0.1 MR-1-Build365
Hello schmiegi ,On the CLI, select option 5. Device Management, then option 3. Advanced Shell.can you perform the following steps:1.) Stop the NASM service: #service nasm:stop -ds nosync 2.) Remove file /content/nasm: #rm -rf /content/nasm 3.) Start the NASM service: #service nasm:start -ds nosync
I already did this. Still the same errors. :(
I would request you please lock a support service request and let me know the service request number for internal tracking purpose !