[Samba] Smbclient cant transer large files

Tue Aug 8 11:29:11 UTC 2017

(forwarding this, din not reply-all)

-----Original Message-----
From: Lange Norbert 
Sent: Dienstag, 08. August 2017 12:00
To: 'L.P.H. van Belle'
Subject: RE: [Samba] Smbclient cant transer large files

Hello,

the mount was done from within GNOME, I don`t know where those parameters come from.

Some corrections are necessary:
The problematic server is a Stretch server, and my desktop is Buster/Testing,
apart from that I have a own repo with backports and various fixes (like now samba with the referred patch).

... and replace the occurrence of "NFS Server" with "Windows Server", sorry for the confusion

I added the output of the various SMB Modes, only SMB2 works (seems like a better fix than having to maintain a patched samba)

Thanks,
Norbert

 >-----Original Message-----
 >From: samba [mailto:samba-bounces at lists.samba.org] On Behalf Of L.P.H. van
 >Belle via samba
 >Sent: Dienstag, 08. August 2017 11:28
 >To: samba at lists.samba.org
 >Subject: Re: [Samba] Smbclient cant transer large files
 >
 >EMAIL from a NON-ANDRITZ SOURCE: as a security measure, please exercise
 >caution with email content and any links or attachments.
 >
 >
 >Hi,
 >
 >>>The same drive can be mounted and accessed easily with
 >cifs://vienas01.andritz.com/HIPASE on /media/HIPASE_Q type cifs
 >>>(rw,nosuid,nodev,relatime,vers=1.0,cache=strict,username=<snip>,domain=<
 >snip>,uid=1000,forceuid,gid=1000,forcegid,addr=172.24.180.161,\
 >>>
 >file_mode=0755,dir_mode=0755,nounix,mapposix,rsize=61440,wsize=65536,ec
 >ho_interval=60,actimeo=1,user=<snip>)
 >
 >What i noticed here also, and if someone can explain this for me why this is.
 >rsize=61440
 >wsize=65536
 >
 >Normaly i see rsize and wsize 65536
 >By default block size = 1024 but above shows a difference of exact 4096
 >Is this related? Should block size not be 4096?
 >
 >From the above cifs mount line, i see a vers=1.0
 >1.0 - The classic CIFS/SMBv1 protocol, and smbv1 is getting disabled
 >everywhere.
 >This is due to you samba 4.2 also.
 >
 >So what happens if use try smbclient like this.
 >smbclient -m SMB2 or  smbclient -m SMB3
 >
 >If you want, or if your able to, i really suggest upgrade you Jessie server to
 >Stretch.
 >And run al least samba 4.5.8, but preffered even higher.
 >
 >If you dont want to move to stretch yet, you can use my packages, found here :
 >http://apt.van-belle.nl
 >For jessie i have : 4.5.8 backported from stretch, 4.5.12 created from
 >samba.org source, 4.6.6 created from samba.org source.
 >For stretch : 4.6.5 and 4.6.6 are available.
 >The apt site explains howto use them.
 >
 >Now very last Norbert, you have the same problem with NFS? I dont understand
 >this part.
 >>  >A very old smbclient (Ubuntu 12.04) was successfully tested, so I believe this
 >was not a change on the NFS Server
 >Can you explain more here, if you problem cifs of nfs or both?
 >
 >
 >Greetz,
 >
 >Louis
 >
 >
 >> -----Oorspronkelijk bericht-----
 >> Van: samba [mailto:samba-bounces at lists.samba.org] Namens
 >> Lange Norbert via samba
 >> Verzonden: dinsdag 8 augustus 2017 10:55
 >> Aan: samba at lists.samba.org
 >> Onderwerp: Re: [Samba] Smbclient cant transer large files
 >>
 >>
 >> Well, apparently there WAS a change on the Windows Server,
 >> which only affected new samba versions I was able to fix my
 >> issue by using this patch:
 >> https://bugzilla.samba.org/show_bug.cgi?id=12776
 >>
 >> Can this be officially fixed please?
 >>
 >>  >-----Original Message-----
 >>  >From: Lange Norbert
 >>  >Sent: Dienstag, 08. August 2017 10:04
 >>  >To: samba at lists.samba.org
 >>  >Subject: Smbclient cant transer large files  >  >  >Hello
 >> >  >I have a problem transferring files >64KB to a Windows
 >> share, it worked fine  >until a few weeks ago (see bottom for
 >> information).
 >>  >The issue seems identical to
 >> https://lists.samba.org/archive/samba/2016-
 >>  >November/204558.html, and I added a Wireshark-Dump which
 >> begins directly  >after  >NTLMSSP_AUTH authentication (don't
 >> want to add login information).
 >>  >
 >>  >The error is always "Write AndX Response fails with
 >> >STATUS_INVALID_PARAMETER"
 >>  >
 >>  >The same drive can be mounted and accessed easily with cifs:
 >>  >//vienas01.andritz.com/HIPASE on /media/HIPASE_Q type cifs
 >> >(rw,nosuid,nodev,relatime,vers=1.0,cache=strict,username=<sni
 >> p>,domain=<sni
 >>
 >> >p>,uid=1000,forceuid,gid=1000,forcegid,addr=172.24.180.161,fi
 >> le_mode=0755,
 >>
 >> >dir_mode=0755,nounix,mapposix,rsize=61440,wsize=65536,echo_in
 >> terval=60,a
 >>  >ctimeo=1,user=<snip>)
 >>  >
 >>  >The problem seems to have appeared with 2:4.2.14+dfsg-0+deb8u7:
 >>  >http://metadata.ftp-
 >>  >master.debian.org/changelogs/main/s/samba/samba_4.2.14+dfsg-
 >>  >0+deb8u7_changelog
 >>  >
 >>  >A very old smbclient (Ubuntu 12.04) was successfully
 >> tested, so I believe this  >was not a change on the NFS
 >> Server  >  >Kind regards  >  >Norbert Lange
 >>
 >>
 >>
 >> ##############################################################
 >> #######################
 >>
 >> This message and any attachments are solely for the use of
 >> the intended recipients. They may contain privileged and/or
 >> confidential information or other information protected from
 >> disclosure. If you are not an intended recipient, you are
 >> hereby notified that you received this email in error and
 >> that any review, dissemination, distribution or copying of
 >> this email and any attachment is strictly prohibited. If you
 >> have received this email in error, please contact the sender
 >> and delete the message and any attachment from your system.
 >>
 >> Thank You.
 >>
 >> ##############################################################
 >> #######################
 >>
 >>
 >> --
 >> To unsubscribe from this list go to the following URL and read the
 >> instructions:  https://lists.samba.org/mailman/options/samba
 >>
 >
 >
 >--
 >To unsubscribe from this list go to the following URL and read the
 >instructions:  https://lists.samba.org/mailman/options/samba