Univention Bugzilla – Bug 53880
Samba shares with consecutive whitespaces not working as expected
Last modified: 2021-10-06 14:46:51 CEST
Samba shares with consecutive whitespaces not working as expected While Bug 38688 and Bug 53799 fixed a problem with loading the samba config then it contains shares with consecutive whitespaces, actual accessing such a share is still problematic or even doesn't work at all. First samba seems to reduce consecutive whitespaces in share names to a single whitespace. E.g. if the share is called "two space", it is listed in samba (smbclient -L ...) as "two space" and can only be accessed as "two space". Accessing it using "two space" results in the following error: "tree connect failed: NT_STATUS_BAD_NETWORK_NAME" (using smbclient) I could not find any documentation about this behavior. Secondly if the directory which should be shared contains consecutive whitespaces, it seems impossible to access that share at all. Even if the share name has no spaces. Trying to access such a share results in the following error: "tree connect failed: NT_STATUS_NO_SUCH_GROUP" (using smbclient)