Skip site navigation (1)Skip section navigation (2)
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
--000000000000ff4e6f060036b241
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

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=E2=80=AFAM Paul Mather <paul@gromit.dlib.vt.ed=
u> 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 =3D 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 =3D 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) manua=
l
> 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 littl=
e
> bit of a pain to set up, but very reliable.  Its main advantage, for me, =
is
> supporting modern SMB standards.
>
> Cheers,
>
> Paul.
>


--=20
Paul Beard / www.paulbeard.org/

--000000000000ff4e6f060036b241
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I&#39;ll take a look but am reluctant (read: lazy) to inst=
all a whole new thing to do something=C2=A0that worked as recently as yeste=
rday.=C2=A0<div><br></div><div>Seeing this on the client side:=C2=A0</div><=
div>Jul 10 18:15:18 &lt;kern.crit&gt; www kernel: smb_smb_negotiate: Don&#3=
9;t know how to talk with server xxx (65535)<br></div><div>I assume this wa=
s during the testing of smb v1, v1=C2=A0+ v2 and pure v2.=C2=A0</div><div><=
br></div><div>I did install samba on the client so I could use smbclient, h=
oping for more debugging info.=C2=A0</div><div><br></div><div>smbclient -U =
www -I omphalos -N /tmp/mnt/storage =C2=A0//mnt/storage<br></div><div>sessi=
on setup failed: NT_STATUS_LOGON_FAILURE<br></div><div><br></div><div>and o=
f course, now smbutil doesn&#39;t work as it used to.=C2=A0</div><div><br><=
/div><div>The client on busybox allows some custom config to added: is ther=
e any logging I can toggle on there?=C2=A0</div></div><br><div class=3D"gma=
il_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jul 11, 2023 at 5:4=
7=E2=80=AFAM Paul Mather &lt;<a href=3D"mailto:paul@gromit.dlib.vt.edu">pau=
l@gromit.dlib.vt.edu</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-sty=
le: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=3D"=
cite" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:2px;border-left-s=
tyle:solid;border-left-color:rgb(114,159,207);padding-left:1ex"><div dir=3D=
"ltr">having some trouble mounting an smb volume hosted by a wireless base =
station running linux/busybox. <br><br>smbutil works, mount_smbfs doesn&#39=
;t. password is in .nsmbrc, seems to be readable by smbutil.=C2=A0<br><br><=
font face=3D"monospace">smbutil view //www@omphalos<br>Share =C2=A0 =C2=A0 =
=C2=A0 =C2=A0Type =C2=A0 =C2=A0 =C2=A0 Comment<br>-------------------------=
------<br>jffs =C2=A0 =C2=A0 =C2=A0 =C2=A0 disk =C2=A0 =C2=A0 =C2=A0 JFFS<b=
r>storage =C2=A0 =C2=A0 =C2=A0disk =C2=A0 =C2=A0 =C2=A0 STORAGE<br>EFI =C2=
=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0disk =C2=A0 =C2=A0 =C2=A0 EFI<br>IPC$ =C2=A0=
 =C2=A0 =C2=A0 =C2=A0 pipe =C2=A0 =C2=A0 =C2=A0 IPC Service (FreshTomato Sa=
mba Server)</font><br><br><font face=3D"monospace">mount_smbfs -I omphalos =
-N //tmp/mnt/storage /mnt/storage<br>mount_smbfs: unable to open connection=
: syserr =3D Authentication error</font><div><br></div><div>tail -1 /etc/fs=
tab <br>//omphalos/STORAGE =C2=A0 =C2=A0 =C2=A0/mnt/storage =C2=A0 =C2=A0sm=
bfs =C2=A0 rw,noauto, -N,-I192.168.0.1 00<br><br></div>This all used to wor=
k, but a couple of firmware upgrades have taken place. This was working yes=
terday after the latest update but now is failing and I am not seeing what&=
#39;s wrong with it.=C2=A0<div><br></div><div>The server offers Samba proto=
col version=C2=A0v1, v2 or mixed v1/v2. v1 doesn&#39;t work at all, returns=
=C2=A0</div><font face=3D"monospace">mount_smbfs: unable to open connection=
: syserr =3D RPC struct is bad<br></font><div><br></div><div>The others wil=
l allow smbutil to work but not mount_smbfs. Logging=C2=A0isn&#39;t telling=
 me much on the server side. I could mount the disk on macOS but that&#39;s=
 not working now either. smbutil still works there but not mount_smbfs.</di=
v></div></blockquote><div><br></div><div><br></div><div>When my OpenELEC se=
rver stopped supporting SMB1 by default I decided to bite the bullet and ab=
andon mount_smbfs, which does not support anything higher than SMB1. =C2=A0=
(See the STANDARDS section of the mount_smbfs(8) manual page.)</div><div><b=
r></div><div>In my case, I switched to the sysutils/fusefs-smbnetfs port.=
=C2=A0 It uses Samba4 under the hood, so supports both SMB2 and SMB3, makin=
g it more compatible with other OSes (like macOS).=C2=A0 I found fusefs-smb=
netfs a little bit of a pain to set up, but very reliable.=C2=A0 Its main a=
dvantage, for me, is supporting modern SMB standards.</div><div><br></div><=
div>Cheers,</div><div><br></div><div>Paul.</div><div><span></span></div></d=
iv>
</blockquote></div><br clear=3D"all"><div><br></div><span class=3D"gmail_si=
gnature_prefix">-- </span><br><div dir=3D"ltr" class=3D"gmail_signature">Pa=
ul Beard / <a href=3D"http://www.paulbeard.org/" target=3D"_blank">www.paul=
beard.org/</a><br></div>

--000000000000ff4e6f060036b241--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAMtcK2qGrxxMFCvYLJs062vmf5z=57jf67q-dMuHi3teENoMMw>