>Not a network problem and nothing else has changed. I just downgraded >to >Samba 4.16.4 from the Rocky Linux 8.7 repos, but left everything else as >Rocky 8.8, and everything is working fine.>Thanks, >DaleI?m running Rocky OS 9 with Samba 4.17.5. I have successfully set up Samba on other OSes with other (prior) versions but I?m encountering the exact same issue you are with nearly the exact same setup/configuration. Is this something to do with the 4.17.5 version, or did you determine it is unique to your setup? I?m wondering if downgrading the Samba package is an effective way to work around this. BPB
On 01/06/2023 12:55, Brian Brock via samba wrote:>> Not a network problem and nothing else has changed. I just downgraded >to >> Samba 4.16.4 from the Rocky Linux 8.7 repos, but left everything else as >> Rocky 8.8, and everything is working fine. > >> Thanks, >> Dale > > I?m running Rocky OS 9 with Samba 4.17.5. I have successfully set up Samba on other OSes with other (prior) versions but I?m encountering the exact same issue you are with nearly the exact same setup/configuration. Is this something to do with the 4.17.5 version, or did you determine it is unique to your setup? I?m wondering if downgrading the Samba package is an effective way to work around this. > BPBJust another couple of thoughts, what is the uidNumber set on the user getting this message in the logs, is it outside the DOMAIN range set in smb.conf ? Can you raise the log level and see if anything helpful pops out ? Rowland
On Thu, Jun 1, 2023 at 8:56?AM Brian Brock via samba <samba at lists.samba.org> wrote:> Is this something to do with the 4.17.5 version, or did you determine itis unique to your setup? I think it is unique to my setup since it works for Christian.> I?m wondering if downgrading the Samba package is an effective way towork around this. downgrading to the 4.16 Rocky 8.7 rpms works for me