Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

3
  • The "API" in question is the Win32 API used by programs running on Windows -- it has nothing to do with SMB access from a Linux machine, where different path length limits apply. (SMB does not carry "raw" path strings, so both \\server\share\foo and \\?\UNC\server\share\foo still result in the same SMB request for share\foo being sent even from a Windows client.) Commented Jul 3, 2020 at 11:05
  • @user1686 Yes, that is taken from the MSDN and windows world. However, there is still limiation in the path at the server. I'll repharse that. Anyways, the server is Windows server and not a Samba one so the limitations from windows world still apply.
    – tukan
    Commented Jul 3, 2020 at 11:14
  • I added some information to the question. The path length is far below the limit you mentioned. Unfortunately I do not know which protocol version is used. There are no settings in smb.conf so it must be the default version (used in 4.5.16). I t does not seem probable but in theory smbclient and mount.cifs could have different default. Is there a way to find that out? The Windows admins had a look at the server and said that everything looks fine there. They see the connection (for mount, too) but do not get error messages for my failed access tries (like there wouldn't be under Linux). Commented Jul 3, 2020 at 19:51