similar to: Disable SMB v1

Hi, I am running samba-4.1.4 on my Fedora OS. I have provided the "client max protocol = SMB3" and "server max protocol = SMB3" parameters in smb.conf file I'm able to get only SMB2.1 packets using wireshark after fileshare access from my windows 7 machine. And not SMB3 packets. SMB2->NegotiateProtocol Response 0x0202 0x0210 Samba-4.1.4 is supporting SMB3 also. So

Hi all, Behavior described in this email is identical whether I try to mount at 192.168.100.2, my desktop and location of my Samba server, or 192.168.100.239, my laptop that is remote from my desktop with Samba server... I want to mount a share defined on my Linux desktop, on my Linux laptop, as a better alternative than sshfs or NFS. I want this mount to happen as version 2.x or 3.x, not as

Sorry for a rather 'unifornative' subject, but i've little o no clue on this. I'm using at work 'pam_mount' with a rather standard configuration to mount via CIFS/SMB user's home directory, from a samba AD member server. This configuration is a bit 'old' (mint sonya, AKA Ubuntu 16.04 as a client, so samba 4.3; debian and samba 4.8 as a server), but work

Samba Team Releases Samba 4.0 ============================= December 11th 2012. The Samba Team is proud to announce the release of Samba 4.0, a major new release of the award-winning Free Software file, print and authentication server suite for Microsoft Windows clients. The First Free Software Active Directory Compatible Server

Samba Team Releases Samba 4.0 ============================= December 11th 2012. The Samba Team is proud to announce the release of Samba 4.0, a major new release of the award-winning Free Software file, print and authentication server suite for Microsoft Windows clients. The First Free Software Active Directory Compatible Server

Is that with an active directory domain controller? On Apr 3, 2016 11:21 PM, "barış tombul" <bbtombul at gmail.com> wrote: > my conf win10 no problem: > client NTLMv2 auth = Yes > client lanman auth = No > server max protocol = SMB3_11 > server min protocol = LANMAN1 > client max protocol = SMB3_11 > client min protocol = CORE > >

Hi, I am trying to figure out what features in terms of protocols (SMB/CIFS, SMB2, SMB2.1, SMB3) a client uses when being connected to a Samba server (v4.1.17). Is there any tool like smbstatus that shows which protocol version (and possibly which features) a client is using in a connection? (Feature in the sense of 'using encryption' for example). Thanks, Adi

On 13/05/2019 17:05, Steve Litt via samba wrote: > Hi all, > > Behavior described in this email is identical whether I try to mount at > 192.168.100.2, my desktop and location of my Samba server, or > 192.168.100.239, my laptop that is remote from my desktop with Samba > server... > > I want to mount a share defined on my Linux desktop, on my Linux > laptop, as a better

Hallo, Luke, Du meintest am 02.04.16: > Also, when I run testparm -svv | less I can find these four lines on > both the working and non-working servers: > server max protocol = SMB3 > server min protocol = LANMAN1 > client max protocol = NT1 > client min protocol = CORE Perhaps a max protocol = NT1 in the global section helps. And

On Mon, 14 Oct 2019 13:47:34 +0100, Rowland penny via samba stated: >On 14/10/2019 13:27, Gerard Seibert via samba wrote: >> FreeBSD 12 >> Samba 4.8.12 >> >> Samba is not showing up on my Win 10 PRO machine. I can access the >> shares if I use the machines hostname or IP, though. How can I >> determine what version of ?smb? is being used? I have set ?client

> -----Original Message----- > From: samba [mailto:samba-bounces at lists.samba.org] On Behalf Of Gerard Seibert via samba > Sent: 14 October 2019 17:09 > To: samba at lists.samba.org > Cc: Gerard Seibert > Subject: Re: [Samba] Detect version of smb being employed > > On Mon, 14 Oct 2019 13:47:34 +0100, Rowland penny via samba stated: > >On 14/10/2019 13:27, Gerard

On 10/14/19 12:00 PM, Roy Eastwood via samba wrote: >> -----Original Message----- >> From: samba [mailto:samba-bounces at lists.samba.org] On Behalf Of Gerard Seibert via samba >> Sent: 14 October 2019 17:09 >> To: samba at lists.samba.org >> Cc: Gerard Seibert >> Subject: Re: [Samba] Detect version of smb being employed >> >> On Mon, 14 Oct 2019

There may be various "signing" parameters that you may need to set to "no"  on the samba PDC. I would also disable SMB3.   Windows 10 does support SMB3 but (in my experience) Samba does not properly implement it, so you will get problems.  Windows 7 does not support SMB3 so will fall back to SMB2 anyway. I suspect at this point making Windows 7 and Windows 3.11 interact

Hi Gaiseric, Do you happen to run into any oplock(opportunistic locking) issues? On my DC I have these issues with my group policy files. I'm hopeful using smb 2.0 will fix this problem. Thanks. On 3/4/2015 3:55 PM, Gaiseric Vandal wrote: > I have several Samba 3.6.24 domain controllers/file servers . > > > Server1 - Solaris 10, Samba 3.6.24, max protocol NT1. This is

Hello, My DC smb.conf currently has the following set server max protocol = NT1 server min protocol = CORE client max protocol = NT1 client min protocol = CORE Is it safe to change both the client and server max to = SMB3? What about on member servers? Should I be concerned with anything breaking? I'm using Windows 7 clients to authenticate against Ubuntu

> > Unless you upload a network capture of you mounting and doing the ls -lR > on the client it's hard to say what really goes on. I understand you > might not want to make it public.. but if you do > This is the last thing I'll try after I've exhausted all the other options. How are you mounting your share (which mount options)? > Something weird is going on with

I have several Samba 3.6.24 domain controllers/file servers . Server1 - Solaris 10, Samba 3.6.24, max protocol NT1. This is the main file server. Server2 - Solaris 10, Samba 3.6.24, max protocol SMB2. 2ndary file server, not as heavily used as as server1. Server3 - Solaris 11, Samba 3.6.24, max protocol SMB2 . This was set up to replace Server 1. I also have a a Citrix XenApp

Hello Experts, I am trying to migrate a Samba 3.6 server to Samba 4.19. The OS of the old server is FreeBSD 10.3 and the new one is FreeBSD 14.1. The client computers are Win 10 Pro. Simple Samba configuration, no need for Active Directory, just a file server with user authentication. On the Windows computer I try to mount the shares from the new server as \\[new server IP address]. The log

On Mon, 8 Aug 2016 14:33:37 -0400 Steve Ankeny <steve_a at cinergymetro.net> wrote: > Looking at a "System 58 error" with Windows 7 -- > > https://serverfault.com/questions/69049/system-error-58-while-accessing-shares-on-windows-7-from-windows-xp > > I'm wondering if the problem lies in the "server max level = NT1" > issue we've seen before

On Tue, 8 Oct 2024 00:20:44 -0400 samba3to4 via samba <samba at lists.samba.org> wrote: > Hello Experts, > > I am trying to migrate a Samba 3.6 server to Samba 4.19. > > [...] > > The log file shows that the user can authenticate: > > [2024/10/07 23:27:24.974539, 2] ../../source3/auth/auth.c: > 338(auth_check_ntlm_password) check_ntlm_password: