similar to: smb_raw_open_recv error on Windows 2012 R2 Preview

Walter H. wrote: > On 28.06.2018 16:30, mark wrote: > >> Just ran into a problem: someone with a new laptop, running Win 10, >> version 1709, tried to map their home directory (served from a CentOS 6.9 >> box, and it fails, with Windows complaining that it no longer supports >> SMBv1, and if you go to their site, you can install support >> for that manually....

On Thu, 28 Jun 2018, mark wrote: > Walter H. wrote: >> On 28.06.2018 16:30, mark wrote: >> >>> Just ran into a problem: someone with a new laptop, running Win 10, >>> version 1709, tried to map their home directory (served from a CentOS 6.9 >>> box, and it fails, with Windows complaining that it no longer supports >>> SMBv1, and if you go to

On 28.06.2018 16:30, mark wrote: > Hi, folks, > > Just ran into a problem: someone with a new laptop, running Win 10, > version 1709, tried to map their home directory (served from a CentOS > 6.9 box, and it fails, with Windows complaining that it no longer > supports SMBv1, and if you go to their site, you can install support > for that manually.... > > The

I will take your suggestion. Still, Samba 3.6 appears to support SMBv2 just fine. Windows 10 PC's and Windows 2019 Servers are able to connect as a client, with SMBv1 disabled. As long as there's a Windows 2012 R2 server doing the backend authentication. Pim On 10/29/2020 7:09 PM, Rowland penny via samba wrote: > I suggest you upgrade your Centos 6 server, it will go EOL in a month

The SMB3 POSIX extensions is different from the old Unix extensions. The Unix extensions can only support vers=1.0, but the new SMB3 POSIX extensions can support SMB3.1.1, vers=3.1.1. You can check this 2018 presentation slides: https://www.snia.org/sites/default/files/SDC/2018/presentations/SMB/Steve_French_SMB311.pdf Page 12 shows that POSIX extensions has been added. Page 22 shows that SMB3

On 05/10/2019 06:49, Chris Han via samba wrote: > Hi, I want to use the SMB3 POSIX extensions in the latest Samba (with > SMB3.1.1, vers=3.1.1). By following the user manual, I have added the > "posix" mount option when mounting, but it shows the following error > messages. > > Error messages: > [xxxxx] CIFS VFS: Server does not support mounting with posix SMB3.11

This might be a kernel thing. 4.13.5-1 .. ? Archlinux? There where recently e-mail about this on technical. So maybe its not implemented parts in samba or mount commands (yet) And i point to this : smb2_get_dfs_refer > > >> [13424.783242] CIFS VFS: ioctl error in smb2_get_dfs_refer rc=-2 > > >> [13424.789504] CIFS VFS: cifs_read_super: get root inode failed To give

Hi Nils, > one more information. > This behaviour also happens on a WIndows 2012 R2 Server System. if this behavior happens also on win2012r2, then the problem may be linked to the SMB version of the protocol. Win7 support SMB version up to SMBv2.x, as does win2k8r2. On the other hand, Win10, Samba4 and Win2k12 supports SMB up to SMBv3.x. And protocol version is negotiated during

On Thu, Oct 12, 2017 at 03:58:58PM +0200, Hadrien Grasland via samba wrote: > Hi, > > We're slowly deprecating SMBv1 support at work, so I'm trying to > mount our Samba network shares using SMBv2.0. This should in > principle be supported by the server, and seems works well enough > for the Windows clients. But it fails for me with some errors which > I do not

hai,   Please keep it mailing to the list, this way is shows up of others also. A workaround for disabling SMBv1, you can make your server less secure but thats not what i would do. Setting these to enable NTLM v1 again. lanman auth = yes ntlm auth = yes raw NTLMv2 auth = yes I think also this is more a question for the free raduis list, but i would to for a ldap(s) setup. just dont mixup

Hai, Can you check the following, a few things that where bit buggy lately. Disable nmbd ( systemctl stop nmbd ) And Try again. And what is in /etc/nsswitch.conf And is SeLinux or Apparmor installed/enabled? Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Rowland Penny via samba > Verzonden: vrijdag 2

Hi, We're slowly deprecating SMBv1 support at work, so I'm trying to mount our Samba network shares using SMBv2.0. This should in principle be supported by the server, and seems works well enough for the Windows clients. But it fails for me with some errors which I do not understand. Can you help me figure out what's going on? Here's my system configuration and a quick

On 11/2/18 5:43 AM, L.P.H. van Belle via samba wrote: > Its a headless server so in this case im unable to test from within kodi, atm. > But Michael count try to to adjust the maxprotocol from within kodi and see if that helps. Kodi is a GUI app. There is no "shell" or "exit to shell" feature. It calls library functions and does not call the "smbclient"

> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Arnab Roy via samba > Verzonden: donderdag 8 juni 2017 14:23 > Aan: samba at lists.samba.org > Onderwerp: [Samba] ntlm_auth and SMBv2/v3 > > Hi , > > I just need some clarification ; > > We currently use ntlm_auth + winbind for AD auth on > Freeradius, will

Hi Rowland, and thank you for quick feedback On Wed, Jun 17, 2020 at 6:45 PM Rowland penny via samba < samba at lists.samba.org> wrote: > On 17/06/2020 17:27, Anders ?stling via samba wrote: > > So my question is; does Win 7 behave differently than Win 10? The shares > > are the same as for the Win 10 clients, including the home directories. > Yes, unless you have changed

On Mon, 23 Oct 2023 12:02:20 +0200 Adam B?aszczykowski via samba <samba at lists.samba.org> wrote: > Ok thank you. > So, Is my file server with Samba 4.17.12 vulnerable to CVE-2016-2114 > if it is not a DC server? > > To be clear, I don't use any Active Directory domain controller in my > network. Lets see if I can paraphrase the documentation for CVE-2016-2014

On 16/05/2023 08:02, Ludovit Koren via samba wrote: > > > Hello, > > I am trying to connect and browse the Windows file server and get the > following error: > > > # smbclient //ente01.xxxx.local/data > Password for [xuser at xxxx.LOCAL]: > tree connect failed: NT_STATUS_SMB_BAD_CLUSTER_DIALECT > > OS: FreeBSD 13.1-STABLE > Samba 4.16.10_1 > >

> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Hadrien Grasland via samba > Verzonden: vrijdag 13 oktober 2017 15:34 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Share mounts in SMBv1 mode, but fails > weirdly in SMBv2 mode > > Hi Louis, > > Thanks for your reply! > > > This might be a

Il giorno lun 7 ott 2019, 10:05:27, Rowland penny via samba ha scritto: > On 07/10/2019 07:35, Andrea Zagli wrote: >> hi >> >> i'm very sorry for this private mail, instead of using the mailing >> list, but i cannot find anymore your reply on my mail client >> >> sorry again >> >> >> >> On 04/10/2019 13:59, Andrea Zagli via

Looks like you didn't really understand Marc's answer. This depends on settings on the Windows client. On the server side, this is not a question of changing behaviour, it's a question of Samba 4 supporting a new feature, SMBv2. I suppose that the only thing you can do on the server side is setting max protocol to SMBv1, which is really bad for performance and for security. People