Date: Tue, 11 Jul 2023 08:47:47 -0400 From: Paul Mather <paul@gromit.dlib.vt.edu> To: paul beard <paulbeard@gmail.com>, FreeBSD-questions <freebsd-questions@freebsd.org> Subject: Re: SMB =?UTF-8?Q?authentication=E2=80=A6flakiness=3F?= Message-ID: <e50a029b5cbc9e8bf9e6d2e92e5872940d233dd5.camel@gromit.dlib.vt.edu> In-Reply-To: <CAMtcK2q0kefQ8Koa%2BoCetqfLauZaRLTQn2r=VNgwBAdb0nrTNA@mail.gmail.com> References: <CAMtcK2q0kefQ8Koa%2BoCetqfLauZaRLTQn2r=VNgwBAdb0nrTNA@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Mon, 2023-07-10 at 18:30 -0700, paul beard wrote: > having some trouble mounting an smb volume hosted by a wireless base > station running linux/busybox. > > smbutil works, mount_smbfs doesn't. password is in .nsmbrc, seems to > be readable by smbutil. > > smbutil view //www@omphalos > Share Type Comment > ------------------------------- > jffs disk JFFS > storage disk STORAGE > EFI disk EFI > IPC$ pipe IPC Service (FreshTomato Samba Server) > > mount_smbfs -I omphalos -N //tmp/mnt/storage /mnt/storage > mount_smbfs: unable to open connection: syserr = Authentication error > > tail -1 /etc/fstab > //omphalos/STORAGE /mnt/storage smbfs rw,noauto, -N,- > I192.168.0.1 00 > > This all used to work, but a couple of firmware upgrades have taken > place. This was working yesterday after the latest update but now is > failing and I am not seeing what's wrong with it. > > The server offers Samba protocol version v1, v2 or mixed v1/v2. v1 > doesn't work at all, returns > mount_smbfs: unable to open connection: syserr = RPC struct is bad > > > The others will allow smbutil to work but not mount_smbfs. > Logging isn't telling me much on the server side. I could mount the > disk on macOS but that's not working now either. smbutil still works > there but not mount_smbfs. When my OpenELEC server stopped supporting SMB1 by default I decided to bite the bullet and abandon mount_smbfs, which does not support anything higher than SMB1. (See the STANDARDS section of the mount_smbfs(8) manual page.) In my case, I switched to the sysutils/fusefs-smbnetfs port. It uses Samba4 under the hood, so supports both SMB2 and SMB3, making it more compatible with other OSes (like macOS). I found fusefs-smbnetfs a little bit of a pain to set up, but very reliable. Its main advantage, for me, is supporting modern SMB standards. Cheers, Paul. [-- Attachment #2 --] <html><head></head><body><div>On Mon, 2023-07-10 at 18:30 -0700, paul beard wrote:</div><blockquote type="cite" style="margin:0 0 0 .8ex; border-left:2px #729fcf solid;padding-left:1ex"><div dir="ltr">having some trouble mounting an smb volume hosted by a wireless base station running linux/busybox. <br><br>smbutil works, mount_smbfs doesn't. password is in .nsmbrc, seems to be readable by smbutil. <br><br><font face="monospace">smbutil view //www@omphalos<br>Share Type Comment<br>-------------------------------<br>jffs disk JFFS<br>storage disk STORAGE<br>EFI disk EFI<br>IPC$ pipe IPC Service (FreshTomato Samba Server)</font><br><br><font face="monospace">mount_smbfs -I omphalos -N //tmp/mnt/storage /mnt/storage<br>mount_smbfs: unable to open connection: syserr = Authentication error</font><div><br></div><div>tail -1 /etc/fstab <br>//omphalos/STORAGE /mnt/storage smbfs rw,noauto, -N,-I192.168.0.1 00<br><br></div>This all used to work, but a couple of firmware upgrades have taken place. This was working yesterday after the latest update but now is failing and I am not seeing what's wrong with it. <div><br></div><div>The server offers Samba protocol version v1, v2 or mixed v1/v2. v1 doesn't work at all, returns </div><font face="monospace">mount_smbfs: unable to open connection: syserr = RPC struct is bad<br></font><div><br></div><div>The others will allow smbutil to work but not mount_smbfs. Logging isn't telling me much on the server side. I could mount the disk on macOS but that's not working now either. smbutil still works there but not mount_smbfs.</div></div></blockquote><div><br></div><div><br></div><div>When my OpenELEC server stopped supporting SMB1 by default I decided to bite the bullet and abandon mount_smbfs, which does not support anything higher than SMB1. (See the STANDARDS section of the mount_smbfs(8) manual page.)</div><div><br></div><div>In my case, I switched to the sysutils/fusefs-smbnetfs port. It uses Samba4 under the hood, so supports both SMB2 and SMB3, making it more compatible with other OSes (like macOS). I found fusefs-smbnetfs a little bit of a pain to set up, but very reliable. Its main advantage, for me, is supporting modern SMB standards.</div><div><br></div><div>Cheers,</div><div><br></div><div>Paul.</div><div><span></span></div></body></html>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e50a029b5cbc9e8bf9e6d2e92e5872940d233dd5.camel>