similar to: client max protocol = SMB3 ?

I have to add noise: Provisioning a DC with sernet 4.1.x called NT1 as max default with me. Am 6. M?rz 2015 18:28:55 MEZ, schrieb James <lingpanda101 at gmail.com>: >OK. Now I'm really confused. I was not aware of two 'testparm' >commands. >Running 'testparm -v' shows correct default values. So whats the >difference? > > >On 3/6/2015 12:20 PM,

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

Hi Marc, I'm a little confused. The values I provided for client and server max protocol are default values. At least according to the command 'samba-tool testparm -v'. I have not explicitly set them in my smb.conf file. I assume SMB3 became the default at some point with a release? I'm worried now that I must make explicit changes to my smb.conf file when default values are

On 06/03/15 17:05, Marc Muehlfeld wrote: > Am 06.03.2015 um 14:56 schrieb Rowland Penny: >>> From 'samba-tool testparm -v' : >>> >>> server max protocol = NT1 >>> >>> BUT 'man smb.conf' says this : >>> >>> Default: server max protocol = SMB3 >>> >>> OK, one of these is wrong, but which ??? > If

Using Wireshark I see the protocol used as SMB2. Using a Windows workstation I tested by navigating to files and folders on my member server or to my sysvol folder on a DC. On 3/6/2015 8:56 AM, Rowland Penny wrote: > On 06/03/15 13:36, James wrote: >> Hi Marc, >> >> I'm a little confused. The values I provided for client and server >> max protocol are default

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

> Which smb version are you using (mount option)? Support for DFS on smb2+ > was only added in linux 4.11. smbstatus shows the connection as NT1. DFS links do work like this: serverA_msdfsrootYES => serverB_msdfsrootNO But not like this: serverA_msdfsrootYES => serverB_msdfsrootYES Somehow the destination having 'msdfsroot yes' prevents the cifs kernel module from

Hello, >> Can more than one server have a share with 'msdfs root = yes'? Or >> can there be only one root? (Setting 'msdfs root = yes' on shares on > > yes Thanks! It works great for all clients* except the linux kernel (v4.9) mount, which was what led me astray. Any idea if this works in more recent kernels? If not where do I wish list this. :)

Re-sending with right email... msdfs root is set to "no" by default and is per-share. [myshare] msdfs root = no path = ... Should do the trick. Otherwise if mounting on linux you can also use the 'nodfs' mount option (mount.cifs //host/share/... /mnt/ -o ...,nodfs) to disable DFS resolving and automatic sub-mounting. Chad W Seys <cwseys at

Hi Rowland, > Are you using sssd or nslcd ? I am using sssd. I can ssh into the server using credentials from either kerberos realm. E.g. ssh cwseys at PHYSICS.WISC.EDU@smb01.physics.wisc.edu (works) ssh seys at AD.WISC.EDU@smb01.physics.wisc.edu (works) PHYSICS.WISC.EDU is an MIT kerberos KDC. AD.WISC.EDU is a active directory KDC (etc). The reason I thought sssd would be best is because

(Let's keep this on the list) Aurélien Aptel via samba <samba at lists.samba.org> writes: > Chad William Seys <cwseys at physics.wisc.edu> writes: >> Somehow the destination having 'msdfsroot yes' prevents the cifs kernel >> module from following the link. I've taken a look at your traces and right off the bat I see things like this: [...]

Hi Rowland et al, > > The reason I thought sssd would be best is because I want to use the > > /etc/passwd file for user existence and was easy to set up. > > You cannot have the same user in /etc/passwd and AD i.e. user 'foo' in > /etc/passwd could, and probably would, be seen as the the AD user 'foo'. The way the system is set up, username existance and

Hello.. My server have this settings in [global] section: max protocol = smb3 min protocol = smb2 When I try connect to server using my clients (Centos 7.3/Ubuntu 16.04) I can't because clients still trying NT1. I must explicity add in smb.conf on clients the option ' client max protocol = smb3' and the connections works again. The question is: If I have defined the min and max

Hello, I currently run samba with server min protocol = NT1 but I need to move towards server min protocol = SMB2 is there any way I can detect which clients still use the older protocol versions? I would like to estimate the impact of the change before i do close NT1/SMB1. Thank and kind regards, Heiner Billich

I did not set max protocol to SMB2 in smb.cnf, I don't want to force SMB2 selection if SMB3 can be used by a client. The machine is a Windows 7, so is SMB2 compliant. Le 22/07/2019 ? 11:44, Gaiseric Vandal via samba a ?crit?: > I would guess that changing the min protocol does not affect existing > connections unless you were to restart samba. > > Is the max protocol set to at

I have a classic NT4 domain with the PDC also the wins server. With the recent ransomware problem, we're trying to remove SMB1 and below protocols. However when I do this, the browse list is gone. Hosts can access properly the shares, but they have to know exactly \\machine\share in order to to connect. The same thing from a linux client: smbclient -L {PDC} -m SMB2 Domain=[{MYDOMAIN}]

Hi Rowland, Below is output of testparm. Samba is set up as standalone server. # testparm Load smb config files from /etc/samba/smb.conf Processing section "[generic]" Loaded services file OK. Server role: ROLE_DOMAIN_MEMBER Press enter to see a dump of your service definitions [global] realm = PHYSICS.WISC.EDU server string = %h server server role =

On Wed, 25 Sep 2024 11:08:24 +0200 Anders ?stling via samba <samba at lists.samba.org> wrote: > Is it possible to have the "min client protocol" statements per share, > or must they be global? I take you meant 'client min protocol', that is a global setting and cannot be per share. > > I am asking since I have the NT1 limit on a specific Samba server with

Hello, I am using Samba version 4.2.0rc4-GIT-4701d74. When using a connection in protocol smb2 or smb3, the unix client says symlinks are not supported, for example: # mount //ip.addr/Programs ./tmp -o vers=3.0 # cd tmp # ln -s bla blub ln: failed to create symbolic link ?blub?: Operation not supported # mount //ip.addr/Programs on /mnt/tmp type cifs

Agreed, I will keep the NT1 share on a separate VM and create a new one for the other services. Air-gapping will be difficult though, but I will check what can be done. Thanks On Wed, Sep 25, 2024 at 11:20?AM Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Wed, 25 Sep 2024 11:08:24 +0200 > Anders ?stling via samba <samba at lists.samba.org> wrote: > >