similar to: Samba 4 Client Directory Contents Refresh

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

Thank you for the reply. I would prefer a RHEL 7 Samba 4 directive to address this. Like a global directive. We have a good amount of Windows workstations of different version involved, I do not want to have to change them all. We do not use AD (large workgroup). I have only tested with Windows 7 (my workstation). My concern is merely a difference in behavior between RHEL 5 (Samba 3), and

Hello Rick, Am 17.01.2018 um 20:20 schrieb rcone via samba: > Starting to use Samba 4 on RHEL 7. I noticed that new files do not > get refreshed automatically for display in a Windows directory listing > on Samba 4, and requires a manual refresh in Windows for them to> appear. This behavior appears to be different from RHEL 5 (Samba 3), > where new files appear automatically. Is

Hello, Starting to use Samba 4 on RHEL 7. I noticed that new files do not get refreshed automatically for display in a Windows directory listing on Samba 4, and requires a manual refresh in Windows for them to appear. This behavior appears to be different from RHEL 5 (Samba 3), where new files appear automatically. Is there a new global directive in Samba 4 for an automatic directory content

Hi, I was wondering if anyone knew why there would be so many Samba (smbd) processes running on my SCO OpenServer 5.0.5 system? I found an awful lot of them running, much more that what I would expect given the number of Windows PC's on the network. One of the users was having trouble accessing a file on the SCO system, and that is when I discovered this. I actually had to write a program

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

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 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

Hello, I am using Samba 4.0.8 on a Red Hat 5.2 x64 machine. I am getting the NT_STATUS_INVALID_PARAMETER error string when running smb_raw_open_recv for a Windows 2012 R2 Preview remote host. I was unable to reproduce the error on other Windows platforms (works fine for Windows 2012 and other older versions). The remote host has SMBv1, SMBv2 and SMBv3 enabled. If I disable SMBv1 I can't even

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

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

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"

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

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

> -----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

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 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

> -----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