search for: status_no_such_fil

Launching workstation local applications creates SMB traffic and STATUS_NO_SUCH_FILE errors I am using Samba 2.2.12 as a domain controller without any use of roaming profiles. Everything is working fine, but I have noticed some strange behavior. I've been working on a problem for quite some time. No matter what local application I launch on a workstation, I will see the f...

I can't open a file (on our samba server) using Actis, When I troubleshoot the problem using Wireshark, see SMB protocol using FIND_FIRST2 and filename using obscure Windows metacharacters, e.g. USAARG03V>>A.SWK , which gives STATUS_NO_SUCH_FILE (Samba is interpreting the name literally) But if the files are copied to a local drive Actis can find them. Thanks for your help.

...lar exception. This exception occurs when a very antiquated piece of DOS based software attempts to write a zip backup file to the share. The attached tcpdump packet summary shows the error at around number 1069. It appears that samba responds to a request for information about the backup file with STATUS_NO_SUCH_FILE, which is, in fact, not true based on a directory listing via a shell prompt on the samba box. A check of perms on the file in question shows that they are correct for the operation being attempted. Ie. # file: MPLUSWIN.ZIP # owner: accounting_member # group: accounting user::rw- group::rw- group...

...017-July/209750.html > https://lists.samba.org/archive/samba/2017-July/209751.html > > Just citing key findings for your reference: > > In SMB1, the Windows client executes one FIND_FIRST2 Request for > each file to be copied (i.e. in my scenario, ~ 1000 requests) > returning STATUS_NO_SUCH_FILE every time before actually > creating/writing to the file. > > When looking at the same file in the SMB2 3.1.1, the Windows client > issues a different Find operation (SMB2_FIND_ID_BOTH_DIRECTORY_INFO > with Pattern "*") that does not look for the particular file name &gt...

...//lists.samba.org/archive/samba/2017-July/209750.html https://lists.samba.org/archive/samba/2017-July/209751.html Just citing key findings for your reference: In SMB1, the Windows client executes one FIND_FIRST2 Request for each file to be copied (i.e. in my scenario, ~ 1000 requests) returning STATUS_NO_SUCH_FILE every time before actually creating/writing to the file. When looking at the same file in the SMB2 3.1.1, the Windows client issues a different Find operation (SMB2_FIND_ID_BOTH_DIRECTORY_INFO with Pattern "*") that does not look for the particular file name that is about to be writt...

Hi again, Jeremy, and hi to all commercial customers of Samba supporting companies on this list, ;-) Am 18.08.2017 um 20:18 schrieb Jeremy Allison: > What I mean is what you're asking is interesting, and I might get time > to look at this, but I can't give any guarentees. Work priorities and > any security issues always have to come first. If people *need* a > guaranteed