search for: whatever_hostnam

...and a log entry with debug priority > if rDNS *mismatches*, but not when there's *no* rDNS. And this is > logged with level=1! > > Sigh.. > > /mjt > If this is a standalone server, then I suggest your turn on Avahi and use it, that way rdns will work, you will get 'whatever_hostname.local' If it is an AD domain member, why doesn't rdns work ? Rowland

10.01.2024 17:02, Rowland Penny via samba wrote: ... > If this is a standalone server, then I suggest your turn on Avahi and > use it, that way rdns will work, you will get 'whatever_hostname.local' Heck. I'm saying that a feature foo is broken. You're suggesting to use another feature instead. The purpose of my email is to fix the broken feature, instead of switching to another broken feature. (and no, avahi wont work in this context *at all*). > If it is an AD dom...

After fixing the abnormal logging with attempts to chmod smbpasswd file, a new threat is now happening: [2024/01/10 16:29:13.984400, 0, pid=2853904] ../../source3/lib/util_sock.c:711(matchname) matchname: host name/name mismatch: 10.2.111.26 != (NULL) [2024/01/10 16:29:13.984471, 0, pid=2853904] ../../source3/lib/util_sock.c:893(get_remote_hostname) matchname failed on 10.2.111.26 Yes,