search for: msmb3

...  Server (using get) > 10GB <-> 10GB      199MB/s > 10GB <-> 2x1GB    162MB/s  (??? ) >   1GB <-> 2x1GB     60MB/s > > > Cl             Server (using put) > 10GB <-> 2x1GB    ~100MB/s >   1GB <-> 2x1GB        50MB/s Try using SMB3 (smbclient -mSMB3). See if that makes a difference.

Setup:  Server 2x10GB NIC, client 1x1GB: Using smbclient with -mSMB3 I get an average of 52000 KiloBytes/sec (before 45000), using NFS (v3) from the same server I get  108000 KiloBytes/sec an more (mount ; cp; umount; ...) Bye, Peer On 03.11.2017 17:01, Jeremy Allison wrote: > On Fri, Nov 03, 2017 at 01:54:10PM +0100, Dr. Peer-Joachim Koch via samba wrote:...

On Mon, Nov 06, 2017 at 09:35:06AM +0100, Dr. Peer-Joachim Koch via samba wrote: > Setup:  Server 2x10GB NIC, client 1x1GB: > > Using smbclient with -mSMB3 I get an average of 52000 KiloBytes/sec (before > 45000), > > using NFS (v3) from the same server I get  108000 KiloBytes/sec an more > (mount ; cp; umount; ...) So I don't think it's the client. The smbclient code is very efficient, pipelining reads and writes. Is the server...

...fault SMB1/NT1?) >> - mount.cifs -o vers=1.0 is OK and slow >> - smbclient -m SMB2 (or -m SMB3) fails > The above is the interesting case, as this is much > easier to debug (in user space) than the kernel > client. > > Can you give more details on *exactly* HOW smbclient -mSMB3 > fails ? This is really strange: today I was not able to reproduce the problem. Neither with smbclient, nor with mount.cifs. Tried with 2 of the 3 Windows machines which showed the original problem, but today all copies with file sizes from 50 GB up to 150 GB went fine, using SMB 3.11. We...

We have a 10G network with a mix of Windows 10 and MacOS 10.12 machines, and a CentOS 7 machine. Copying large files "fast" from the CentOS machine to Windows, using SMB2 or SMB3 fails almost every time, at the end of the copy. - With SMB1, it seems to work, but is much slower. - Copying to a smb share on a Mac seems to work, but is also much slower. - Using a normal Gigabit network

...SMB3 connection can be selected in one of two ways. The easiest way to test the new protocol connection is to add the -mMAX_PROTOCOL command line switch to either smbclient or smbcacls. For example, to connect using SMB3 with smbclient a user would type: smbclient //server/share -Uuser%password -mSMB3 Another example of connecting using SMB2 using smbcacls would be: smbcacls //server/share -Uuser%password -mSMB2 filename Note that when connecting using SMB2 or SMB3 protocols the UNIX extensions are no longer available inside the smbclient command set. This is due to UNIX extensions not yet be...

...SMB3 connection can be selected in one of two ways. The easiest way to test the new protocol connection is to add the -mMAX_PROTOCOL command line switch to either smbclient or smbcacls. For example, to connect using SMB3 with smbclient a user would type: smbclient //server/share -Uuser%password -mSMB3 Another example of connecting using SMB2 using smbcacls would be: smbcacls //server/share -Uuser%password -mSMB2 filename Note that when connecting using SMB2 or SMB3 protocols the UNIX extensions are no longer available inside the smbclient command set. This is due to UNIX extensions not yet be...

...build process. > > Is there something I need to do when building from sRPMs to make > this stick? You could double check in ~/rpmbuild/BUILD/ if the patch was really applied. If it was, an smbclient open should result in DENY_ALL denymode in smbstatus -L, eg: $ ./bin/smbclient -Uslow%x -msmb3 //10.10.11.100/test Domain=[SLOWSERVER] OS=[] Server=[] smb: \> open test open file \test: for read/write fnum 1 $ sudo ./bin/smbstatus -L Locked files: Pid Uid DenyMode Access R/W Oplock SharePath Name Time -------------------------------------------...

I am having a problem with getting smbclient to interact with a Window 10 PRO/64 bit machine. The smbclient is being run from a FreeBSD-11.1/amd64 machine. smbclient - Version 4.6.11 Windows 10 Pro - version 1709 I have tried numerous methods, like the following: smbclient -I 192.168.0.102 -L HP-ENVY protocol negotiation failed: NT_STATUS_CONNECTION_RESET In every instance, it ends with the

...option] is OK and slow (uses default SMB1/NT1?) > - mount.cifs -o vers=1.0 is OK and slow > - smbclient -m SMB2 (or -m SMB3) fails The above is the interesting case, as this is much easier to debug (in user space) than the kernel client. Can you give more details on *exactly* HOW smbclient -mSMB3 fails ?

...SMB3 connection can be selected in one of two ways. The easiest way to test the new protocol connection is to add the -mMAX_PROTOCOL command line switch to either smbclient or smbcacls. For example, to connect using SMB3 with smbclient a user would type: smbclient //server/share -Uuser%password -mSMB3 Another example of connecting using SMB2 using smbcacls would be: smbcacls //server/share -Uuser%password -mSMB2 filename Note that when connecting using SMB2 or SMB3 protocols the UNIX extensions are no longer available inside the smbclient command set. This is due to UNIX extensions not yet be...

...SMB3 connection can be selected in one of two ways. The easiest way to test the new protocol connection is to add the -mMAX_PROTOCOL command line switch to either smbclient or smbcacls. For example, to connect using SMB3 with smbclient a user would type: smbclient //server/share -Uuser%password -mSMB3 Another example of connecting using SMB2 using smbcacls would be: smbcacls //server/share -Uuser%password -mSMB2 filename Note that when connecting using SMB2 or SMB3 protocols the UNIX extensions are no longer available inside the smbclient command set. This is due to UNIX extensions not yet be...

...SMB3 connection can be selected in one of two ways. The easiest way to test the new protocol connection is to add the -mMAX_PROTOCOL command line switch to either smbclient or smbcacls. For example, to connect using SMB3 with smbclient a user would type: smbclient //server/share -Uuser%password -mSMB3 Another example of connecting using SMB2 using smbcacls would be: smbcacls //server/share -Uuser%password -mSMB2 filename Note that when connecting using SMB2 or SMB3 protocols the UNIX extensions are no longer available inside the smbclient command set. This is due to UNIX extensions not yet be...

...SMB3 connection can be selected in one of two ways. The easiest way to test the new protocol connection is to add the -mMAX_PROTOCOL command line switch to either smbclient or smbcacls. For example, to connect using SMB3 with smbclient a user would type: smbclient //server/share -Uuser%password -mSMB3 Another example of connecting using SMB2 using smbcacls would be: smbcacls //server/share -Uuser%password -mSMB2 filename Note that when connecting using SMB2 or SMB3 protocols the UNIX extensions are no longer available inside the smbclient command set. This is due to UNIX extensions not yet be...

...SMB3 connection can be selected in one of two ways. The easiest way to test the new protocol connection is to add the -mMAX_PROTOCOL command line switch to either smbclient or smbcacls. For example, to connect using SMB3 with smbclient a user would type: smbclient //server/share -Uuser%password -mSMB3 Another example of connecting using SMB2 using smbcacls would be: smbcacls //server/share -Uuser%password -mSMB2 filename Note that when connecting using SMB2 or SMB3 protocols the UNIX extensions are no longer available inside the smbclient command set. This is due to UNIX extensions not yet be...

Hi Ralph, I applied the patch to a new build of Sernet 4.4.6 SRPM. I could still open the file from both hosts, and in fact this time I could actually open it on the same host without any problems: host 1: smbclient -U ajc //172.31.0.120/ifa_v ... smb: \jmi\Corporate Accounting\ISL Ltd Accounts\2016\1609\> open "201609 213_ ISL Balance sheet variance analysis.xls" open file

...s there something I need to do when building from sRPMs to make >> this stick? > You could double check in ~/rpmbuild/BUILD/ if the patch was really > applied. If it was, an smbclient open should result in DENY_ALL > denymode in smbstatus -L, eg: > > $ ./bin/smbclient -Uslow%x -msmb3 //10.10.11.100/test > Domain=[SLOWSERVER] OS=[] Server=[] > smb: \> open test > open file \test: for read/write fnum 1 > > $ sudo ./bin/smbstatus -L > Locked files: > Pid Uid DenyMode Access R/W Oplock SharePath Name Time > ----...

just to verify basic facts: Did you cross check vie network sniff, on which SMB protocol versions Server + Win 7 clients agree ? Or did you pin down via registry ? AFAIK only starting with win 8 or win 10 clients you could ask with powershell, which protocol version is in use. Did you also cross check samba logs for a name resolution issue ( windows names, not DNS) if one of your boxes is an