The Sophos Community will be offline for scheduled maintenance this Saturday, May 27th, at 13:00 UTC for approximately 1 hour. Apologies for any inconvenience caused.
"Wanna" ransomware outbreak. Please see this Sophos article sophos.com/kb/126733 for advice on how to protect your organization. Immediate action recommended.
We'd love to hear about it! Click here to go to the product suggestion community
Hi. My fallback log is constantly filling with messages like this:
2017:05:19-08:40:18 portal [daemon:err] winbindd: [2017/05/19 08:40:18.792234, 0] libsmb/cliconnect.c:1865(cli_session_setup_spnego)2017:05:19-08:40:18 portal [daemon:err] winbindd: Kinit failed: Client not found in Kerberos database
It's been going on since before this box was dropped in my lap. AD authentication is working as I can test authentication just fine. Any ideas what to do?
I googled site:community.sophos.com/products/unified-threat-management/f Kinit failed -succeeded
The thread that caught my eye indicated that this might be solved by un-joining and then re-joining the UTM to the domain. Un-join by using incorrect credentials and then join again using valid credentials. If that didn't work, you might need to rename your UTM using only lowercase letters before joining again - see The Zeroeth Rule in Rulz. Any luck with either approach?
Cheers - Bob