Date: Tue, 11 Jul 2023 07:12:59 -0700 From: paul beard <paulbeard@gmail.com> To: Paul Mather <paul@gromit.dlib.vt.edu> Cc: FreeBSD-questions <freebsd-questions@freebsd.org> Subject: =?UTF-8?Q?Re=3A_SMB_authentication=E2=80=A6flakiness=3F?= Message-ID: <CAMtcK2qGrxxMFCvYLJs062vmf5z=57jf67q-dMuHi3teENoMMw@mail.gmail.com> In-Reply-To: <e50a029b5cbc9e8bf9e6d2e92e5872940d233dd5.camel@gromit.dlib.vt.edu> References: <CAMtcK2q0kefQ8Koa%2BoCetqfLauZaRLTQn2r=VNgwBAdb0nrTNA@mail.gmail.com> <e50a029b5cbc9e8bf9e6d2e92e5872940d233dd5.camel@gromit.dlib.vt.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] I'll take a look but am reluctant (read: lazy) to install a whole new thing to do something that worked as recently as yesterday. Seeing this on the client side: Jul 10 18:15:18 <kern.crit> www kernel: smb_smb_negotiate: Don't know how to talk with server xxx (65535) I assume this was during the testing of smb v1, v1 + v2 and pure v2. I did install samba on the client so I could use smbclient, hoping for more debugging info. smbclient -U www -I omphalos -N /tmp/mnt/storage //mnt/storage session setup failed: NT_STATUS_LOGON_FAILURE and of course, now smbutil doesn't work as it used to. The client on busybox allows some custom config to added: is there any logging I can toggle on there? On Tue, Jul 11, 2023 at 5:47 AM Paul Mather <paul@gromit.dlib.vt.edu> wrote: > 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. > -- Paul Beard / www.paulbeard.org/ [-- Attachment #2 --] <div dir="ltr">I'll take a look but am reluctant (read: lazy) to install a whole new thing to do something that worked as recently as yesterday. <div><br></div><div>Seeing this on the client side: </div><div>Jul 10 18:15:18 <kern.crit> www kernel: smb_smb_negotiate: Don't know how to talk with server xxx (65535)<br></div><div>I assume this was during the testing of smb v1, v1 + v2 and pure v2. </div><div><br></div><div>I did install samba on the client so I could use smbclient, hoping for more debugging info. </div><div><br></div><div>smbclient -U www -I omphalos -N /tmp/mnt/storage //mnt/storage<br></div><div>session setup failed: NT_STATUS_LOGON_FAILURE<br></div><div><br></div><div>and of course, now smbutil doesn't work as it used to. </div><div><br></div><div>The client on busybox allows some custom config to added: is there any logging I can toggle on there? </div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Jul 11, 2023 at 5:47 AM Paul Mather <<a href="mailto:paul@gromit.dlib.vt.edu">paul@gromit.dlib.vt.edu</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div><div>On Mon, 2023-07-10 at 18:30 -0700, paul beard wrote:</div><blockquote type="cite" style="margin:0px 0px 0px 0.8ex;border-left-width:2px;border-left-style:solid;border-left-color:rgb(114,159,207);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></div> </blockquote></div><br clear="all"><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature">Paul Beard / <a href="http://www.paulbeard.org/" target="_blank">www.paulbeard.org/</a><br></div>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMtcK2qGrxxMFCvYLJs062vmf5z=57jf67q-dMuHi3teENoMMw>