samba - Jun 2019 - error when trying to copy file from samba share to old Windows CE share

Resending this to whole list, sorry for the duplicate email Rowland, I
rarely use mailing lists and didn't notice the Reply-To was to you
instead of the list.

On Tue, Jun 18, 2019 at 10:18 AM Rowland penny via samba
<samba at lists.samba.org> wrote:
>
> Try adding 'client max protocol = NT1' to [global] in your smb.conf
>
> Rowland
>
Tried this, but it did not help. I am kind of confused though, maybe
there is a misunderstanding... The "client max protocol" setting would
only effect smbclient run on the server itself, right? I am not
accessing or mounting any shares on the server itself, just hosting
the share. It is a Windows 7 PC that is accessing the share as the
client and giving me the error.

I also tried setting "server max protocol = NT1" and it did not help
either.

Tried testing on Windows 10 and it gives a slightly different error,
"Could not find this item
This is no longer located in C:\Path\To\File. Verify the item's
location and try again."

but of course the file is still there...

Thanks,
Dan

On Tue, Jun 18, 2019 at 10:18 AM Rowland penny via samba
<samba at lists.samba.org> wrote:
>
> On 18/06/2019 14:55, Dan Arena via samba wrote:
> > Hello,
> >
> > This error started after upgrading my distro(did a fresh install of
> > fedora 30 server edition), which upgraded samba from 4.1.20 to 4.10.4.
> > If I try to copy a file using a Windows 7 PC from the samba share to
> > an old Windows CE share (on a CNC router table, so can't upgrade
it)
> > it tells me:
> >
> > An unexpected error is keeping you from copying the file. If you
> > continue to receive this error, you can use the error code to search
> > for help with this problem.
> >
> > Error 0x8007007C: The system call level is not correct.
> >
> > It shows this every time and refuses to copy the file. I am able to
> > copy the file from the samba share to the Windows PC just fine, and I
> > can read the file contents. I also tried then copying the file from
> > the Windows 7 PC to the Windows CE share and it still gives the error.
> > I am able to copy any other file from the Windows 7 PC to the Windows
> > CE share as long as it didn't originate from the samba share. The
> > smb.conf is almost exactly the same on the new server as my old server
> > that didn't have this issue. The only thing I had to add to get it
> > working with some of the windows PCs was "ntlm auth > >
ntlmv1-permitted". This is a simple file share, no DC/AD setup.
> >
> > Searching online for information about this error code did not turn up
> > much. Only interesting thing I found was at
> >
https://docs.microsoft.com/en-us/windows/desktop/adsi/win32-error-codes-for-adsi-2-0
> > where it mentions 0x8007007C could also be
"LDAP_PROTOCOL_ERROR".
> >
> > Here is my smb.conf:
> >
> > [global]
> >          workgroup = MYGROUP
> >          server string = Main File Server
> >          security = user
> >          passdb backend = tdbsam
> >          ntlm auth = ntlmv1-permitted
> >          local master = yes
> >          os level = 66
> >          preferred master = yes
> >          wins support = yes
> >
> >          load printers = no
> >
> >          log file = /var/log/samba/log.%m
> >          # maximum size of 10MB per log file, then rotate:
> >          max log size = 10000
> >
> > [homes]
> >          comment = Home Directories
> >          valid users = %S, %D%w%S
> >          browseable = No
> >          read only = No
> >          inherit acls = Yes
> >
> > [fileshare]
> >     comment = Public Share
> >     path = /share/fileshare
> >     public = no
> >     writable = yes
> >     valid users= @fileshare
> >     printable = no
> >     force create mode = 0660
> >     force directory mode = 0770
> >     force group = fileshare
> >
> >
> > Thanks,
> > Dan
> >
> Try adding 'client max protocol = NT1' to [global] in your smb.conf
>
> Rowland
>
>
> --
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba

On Wed, Jun 19, 2019 at 10:00:23AM -0400, Dan Arena via samba
wrote:
> Resending this to whole list, sorry for the duplicate email Rowland, I
> rarely use mailing lists and didn't notice the Reply-To was to you
> instead of the list.
> 
> On Tue, Jun 18, 2019 at 10:18 AM Rowland penny via samba
> <samba at lists.samba.org> wrote:
> >
> > Try adding 'client max protocol = NT1' to [global] in your
smb.conf
> >
> > Rowland
> >
> 
> Tried this, but it did not help. I am kind of confused though, maybe
> there is a misunderstanding... The "client max protocol" setting
would
> only effect smbclient run on the server itself, right? I am not
> accessing or mounting any shares on the server itself, just hosting
> the share. It is a Windows 7 PC that is accessing the share as the
> client and giving me the error.
> 
> I also tried setting "server max protocol = NT1" and it did not
help either.
> 
> Tried testing on Windows 10 and it gives a slightly different error,
> "Could not find this item
> This is no longer located in C:\Path\To\File. Verify the item's
> location and try again."
> 
> but of course the file is still there...
Only wireshark traces and debug level 10 logs are
going to help here I'm afraid.

On Wed, Jun 19, 2019 at 2:57 PM Jeremy Allison <jra at samba.org>
wrote:
> Only wireshark traces and debug level 10 logs are
> going to help here I'm afraid.
I have the tcpdumps open in wireshark right now, and also have debug
10 logs. Do you want me to just email these directly to you or
something? I have been staring at wireshark for like 20 minutes now,
but don't really know what I am looking for. I have a dump of the same
file being transferred with the old samba vs new samba, but it looks
like they are currently using different protocol versions. I found the
packet where the data is being transferred and I can see a lot of
permission bits, etc.

Thanks,
Dan