Neon upgrade seems to have broken samba...
Page 1 of 1 (2 posts)
Tags:
None
Registered Member 
|
Hi.
I just updated this morning to the latest and greatest KDE Neon and found that I can no longer mount samba shares from our TrueNas system. No matter what I throw at it, it tells me the permission is denied. Nonsense. 1/2 an hour ago, I was able to get in just fine. It isn't a permissions issue, and it is working great for everyone else (windows and linux). The strange thing is that samba was not a package in the upgrade. Something else must be causing this... but I cannot mount any share from the TrueNas box from the command line or from a Dolphin window. I don't get any useful feedback... just "permission denied" -- even when looking in the logs on the server or client. So dmesg on the client tells me:
The same output is in /var/log/syslog There are no errors on the server for my user when attempting to connect. The packages that were upgraded:
I've seen some older posts where people were having similar issues and they used the sec=ntlmv2 or sc=ntlmssp options... In fact, I threw every sec= option in the man page, but that is not helping here. i can mount windows shares from windows servers just fine (with the same credentials). Thank you. OK... I was looking for a way to delete this post, but I guess too many days have passed. I have my solution, though it makes no sense to me. I rebooted the truenas server... and it works. I would have done this sooner... but it is a production system. The weird thing is that there were no changes whatsoever on the freenas server. Only my Neon system. Freenas was still working in all other respects -- and I found it would work in dolphin provided I used the UPN nomenclature (as opposed to the old netbios UNC format). It wouldn't work on the command line (including fstab), however, no matter what I threw at it. Restarting the smb service was not enough to fix this. Rebooting the truenas server, for whatever reason, fixed this issue.
Last edited by grooveman on Thu Jan 20, 2022 7:57 pm, edited 1 time in total.
|
|
Registered Member
|
This is an interesting issue... I think Linux is only obliquely involved.
What I've found is that this is also true in Debian buster now. I think what initiated this was the last patch Tuesday updates on the domain controllers. Winbindd on the truenas server stops being able to connect to the DC after a while. When I put the debug log to the maximum, you can see the rejections it is getting from the DC. The interesting thing here is that it only seems to affect the contemporary Linux systems -- and only when using the standard mount commands. It will still work with gvfs, and as noted, will work in Dolphin, provided I use the UPN... and of course, Windows clients work normally as well. I'm thinking now that this is, at heart, a Microsoft issue -- at least it was elicited by them. We have found that restarting winbindd will fix the problem for a period of time. It only seems to manifest ever few days, so doing this 3x a week in the wee hours of the a.m. would probably be enough to keep any users from noticing. I've also noted that if I mount the directory, and squat on it for some days, and the TN server windbindd starts squaking -- it will not affect my mount. The error seems to happen only at the time of authentication. If I unmount it and try to remount it while winbindd is unhappy, I cannot. The fix here is probably outside the bounds of debian/ubuntu/neon and in the court of Microsoft and the TN team. |
Page 1 of 1 (2 posts)
Bookmarks
Who is online
Registered users: Bing [Bot], Google [Bot], Sogou [Bot]
