Bug 11633 - NT_STATUS_BAD_NETWORK_PATH writing/deleting files to MAC 0S 10.9.5 server
NT_STATUS_BAD_NETWORK_PATH writing/deleting files to MAC 0S 10.9.5 server
Status: RESOLVED INVALID
Product: Samba 4.1 and newer
Classification: Unclassified
Component: libsmbclient
unspecified
All All
: P5 major
: ---
Assigned To: Samba QA Contact
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2015-12-04 11:35 UTC by Mike
Modified: 2015-12-07 13:02 UTC (History)
2 users (show)

See Also:


Attachments
Wireshark trace to Mac OS 10.10.3 (1.43 MB, application/vnd.tcpdump.pcap)
2015-12-04 11:39 UTC, Mike
no flags Details
Logs with debug level 10 from different run from Linux samba 4.1.17 (745.54 KB, text/plain)
2015-12-04 12:48 UTC, Mike
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Mike 2015-12-04 11:35:41 UTC
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.
Comment 1 Mike 2015-12-04 11:39:57 UTC
Created attachment 11665 [details]
Wireshark trace to Mac OS 10.10.3
Comment 2 Mike 2015-12-04 12:48:39 UTC
Created attachment 11666 [details]
Logs with debug level 10 from different run from Linux samba 4.1.17
Comment 3 Volker Lendecke 2015-12-04 14:02:29 UTC
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.
Comment 4 Jeremy Allison 2015-12-04 18:39:23 UTC
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.

Jeremy,
Comment 5 Volker Lendecke 2015-12-04 19:43:32 UTC
(In reply to Jeremy Allison from comment #4)

But what can we do in this case?
Comment 6 Jeremy Allison 2015-12-04 20:04:24 UTC
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.