We have a workflow using smbclient that writes a lock directory and lock file in that directory, creates another directory, writes some files, and then deletes the lock file and directory. If we do this one right after another, it eventually (after 5 to 10 tries) gives us back a NT_STATUS_BAD_NETWORK_PATH error. We have created scripts and sent the same workflow to our MAC server and another to a Windows 2012 server, and the windows server has no problems with it. It appears to be a Mac issue since it happens using 3.6.5, 4.0.7, 4.1.17 and 4.1.19. I've scoured the web and can't find an answer.
Created attachment 11665 [details]
Wireshark trace to Mac OS 10.10.3
Created attachment 11666 [details]
Logs with debug level 10 from different run from Linux samba 4.1.17
I'm assuming from the comments that the server is an OS/X SMB server.
Please contact Apple about this issue, it looks like smbclient is doing things exactly the same way every time, but sometimes the Apple SMB server does not like it. Apple should be able to tell you what's wrong here.
Volker, this is my fault. I asked Mike to log a bug with us here, so at least we have a record of something going wrong with the MacOSX server we can point to if others have the same issue.
(In reply to Jeremy Allison from comment #4)
But what can we do in this case?
Not a lot. I just wanted this as a placeholder so if Apple fix it or give us a workaround we can track it here.