Date: Thu, 28 Sep 2017 17:11:56 +0200 From: Stefan Esser <se@freebsd.org> To: Mario Lobo <lobo@bsd.com.br> Cc: FreeBSD File-Systems <freebsd-fs@freebsd.org> Subject: Re: mount_smbfs question (re-post) Message-ID: <6a2b3bf8-b70b-a39e-be33-fa28967ebb88@freebsd.org> In-Reply-To: <CA%2ByoEx8kVpoHrZOv5fCSa6=YaaCQ3YWJUQtYiPVhqR6ZnjufCg@mail.gmail.com> References: <20170927100635.7b56f8fd@Papi.lobos> <CA%2B4G5KZP5TsGk53Wvf3SYCHwbTDry21qxa=0Sq%2BH5-voZWeumQ@mail.gmail.com> <CA%2ByoEx8kVpoHrZOv5fCSa6=YaaCQ3YWJUQtYiPVhqR6ZnjufCg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Am 28.09.17 um 16:16 schrieb Mario Lobo: > 2017-09-27 11:20 GMT-03:00 Erwan Legrand <freebsd@erwanlegrand.com>: > >> On Wed, Sep 27, 2017 at 3:06 PM, Mario Lobo <mlobo@digiart.art.br> wrote: >>> Since my environment is tottaly surrounded with shares that no longer >>> accept SMBv1 (Windows, Linux AND FreeBSD servers), so basically in the >>> end, what I'm really looking for is a confirmation that I'll just have >>> to dump all Freebsd samba clients because the OS can't deal with SMBv2 >>> or above. >> >> Perhaps have a look at implementations of SMB on top of FUSE? >> http://portsmon.freebsd.org/portoverview.py?category= >> sysutils&portname=fusefs-smbnetfs >> _______________________________________________ >> freebsd-questions@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-questions >> To unsubscribe, send any mail to "freebsd-questions- >> unsubscribe@freebsd.org" >> > > I did. Same problem. > smbnetfs only works with SMBv1 No, I've just tested it, it can see my SMB3-only samba server. I do not have any windows server to test against, but you can rise the debug level in smbnetfs.conf and start smbnetfs with the -d option to see what's going wrong on your system.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6a2b3bf8-b70b-a39e-be33-fa28967ebb88>