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

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

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

What i see with google and that error code is. 

Windows activation problems due to bad disk/bad sectors. 
File copy problems due to wrong rights. 
Virus/mailware activity. 

And what happens if you change your share to : 
 [fileshare]
    comment = Public Share
    path = /share/fileshare
    public = no
    writable = yes
    printable = no

A few thing you can check/try. 

Greetz, 

Louis
 
> -----Oorspronkelijk bericht-----
> Van: samba [mailto:samba-bounces at lists.samba.org] Namens Dan 
> Arena via samba
> Verzonden: dinsdag 18 juni 2019 15:56
> Aan: samba at lists.samba.org
> Onderwerp: [Samba] error when trying to copy file from samba 
> share to old Windows CE share
> 
> 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-er
> ror-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
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba
> 
>

On Tue, Jun 18, 2019 at 09:55:39AM -0400, 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.
That usually means the client is sending an info level
we don't support. Can you get a wireshark trace/debug level 10
log ?

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 Tue, Jun 18, 2019 at 9:56 AM Dan Arena via samba
<samba at lists.samba.org> wrote:
> ... I also tried then copying the file from
> the Windows 7 PC to the Windows CE share and it still gives the error.
So it's a problem with the file at this point.
> 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.
Would it be accurate to say that all files not originating (at some
point) from the Samba system can be successfully copied to the CE
device and that all files once copied from the Samba system to the
Windows PC give rise to that error when you attempt to copy them to
the CE device?

If so, I would wonder about the source of the files on the Samba
system. As a test; if you copy a working file from the PC (one that
you can copy successfully from the PC to the CE) to the Samba system
can that file then be copied directly to the CE device? If you copy
the same file back from the Samba system to the PC does it then fail
the copy from the PC to the CE device?

Chris

On Tue, Jun 18, 2019 at 10:48 AM L.P.H. van Belle via samba
<samba at lists.samba.org> wrote:
>
> And what happens if you change your share to :
>  [fileshare]
>     comment = Public Share
>     path = /share/fileshare
>     public = no
>     writable = yes
>     printable = no
>
Louis, thanks for the suggestion, but unfortunately this did not fix it either.

On Wed, Jun 19, 2019 at 10:23 AM Sonic <sonicsmith at gmail.com>
wrote:
>
> Would it be accurate to say that all files not originating (at some
> point) from the Samba system can be successfully copied to the CE
> device and that all files once copied from the Samba system to the
> Windows PC give rise to that error when you attempt to copy them to
> the CE device?
>
> If so, I would wonder about the source of the files on the Samba
> system. As a test; if you copy a working file from the PC (one that
> you can copy successfully from the PC to the CE) to the Samba system
> can that file then be copied directly to the CE device? If you copy
> the same file back from the Samba system to the PC does it then fail
> the copy from the PC to the CE device?
>
> Chris
Yes, that is exactly the case. Just tested what you asked; copied a
file from PC desktop to samba share, then back to desktop, and now the
copy of the file will not copy from the PC desktop to the CE share,
but the original file still copies successfully. This is pretty odd...

I am going to try tcpdump'ing the transfers with old samba vs new
samba to see what the difference is. The same files with same smb.conf
on older samba version is not having this issue.

Thanks,
Dan