similar to: Disable SMB v1

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

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

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

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

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

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

Hi, Trying the latest version again tonight 4.6.7 it has the same problem I've seen with the prior newer versions as well. The one I went back to was 4.4.15 which works. What is happening right now is there is a Win2K3 box that is the domain server, with thecompanydomain.com (NetBIOS domain name: COMPANY). That has the __MSBROWSE__ on it. I have a Linux Wheezy system on that is part of

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 max protocol = SMB3? in the config file; however, I am not sure if it is being used. Thanks! -- Gerard -------------- next part -------------- A non-text attachment was

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

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

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

> -----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 Mon, Jul 13, 2020 at 2:03 AM Rowland penny via samba < samba at lists.samba.org> wrote: > On 13/07/2020 04:29, Michael Jones via samba wrote: > > I'm trying to diagnose why my windows 10 clients can't do network > browsing. > > The network neighborhood doesn't show any of my machines running samba. > > > > Any advice? > > > Sorry, but it

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

Hi, all, we run smbcacls tool from linux machine to set file permissions on windows server. here is our environment: Linux machine: Ubuntu 14.04 LTS, kernel version 3.13.0-112-generic Samba version: 4.3.11 Windows machine: Windows server 2012 the cmd we run is something like following: /usr/bin/smbcacls -U 'Domain\Administrator'%'pwd' '//win_server/testshare'

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

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

## QUESTION I am sharing a 120GB folder with lots of files via Samba on a LAN (1Gbps connection). 1) Doing an `ls -lR` on the server (on this folder) takes ~32 seconds, compared with **72 minutes** on the client. Is this difference in performance expected (due to network and protocol overhead)? 2) While the client is executing an `ls -lR`, one smbd process on the server uses about 30-40% of a