Your walking a thin line here.. https://docs.microsoft.com/en-us/rest/api/storageservices/naming-and-referencing-shares--directories--files--and-metadata Quote : Share names must start with a letter or number, and can contain only letters, numbers, and the dash (-) character. https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file?redirectedfrom=MSDN Not saying its wrong, but your prone to errors.. I would not recommend it. Greetz, Louis> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Luke > Barone via samba > Verzonden: dinsdag 4 februari 2020 22:42 > Aan: James Cartner-Young (Sandal Computers) > CC: samba > Onderwerp: Re: [Samba] Newbie question: Spaces in share names > > I use spaces in share names, and I don't have problems. > > On Tue, Feb 4, 2020 at 1:28 PM James Cartner-Young (Sandal > Computers) via > samba <samba at lists.samba.org> wrote: > > > Hello. > > > > I hope you are all well. > > > > A quick question as I am trying to fix some bugs and just wondering > > where the fault lies - Does the Samba daemon/client specification > > (Windows version or otherwise) support spaces within share > names (not at > > the start, but after the first alphanumeric character and > before the last)? > > > > For example is "My Document Share" a valid share name, which > > "\\Servername\My Document Share" would then point to? > > > > I have searched various guides and the Samba wiki, but, > strangely, found > > nothing relating to my searches. > > > > I ask as I have a share with a space in it which shared > fine from the > > BSD server and worked fine on my Linux Mint desktop client. However, > > recently, a core component (possibly after an update? I'm > not 100% sure) > > has been misbehaving with this particular share... The > share happens to > > be where all my business data is kept, so it's quite > important that I > > have consistent access to it. > > > > I understand some folk shudder at the thought, but I was > assuming that > > it was being handled fine, until now. > > > > Many thanks for your help. > > > > James > > > > -- > > To unsubscribe from this list go to the following URL and read the > > instructions: https://lists.samba.org/mailman/options/samba > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba > >
On Wed, 2020-02-05 at 08:59 +0100, L.P.H. van Belle via samba wrote:> Your walking a thin line here.. > > https://docs.microsoft.com/en-us/rest/api/storageservices/naming-and-referencing-shares--directories--files--and-metadata > Quote : Share names must start with a letter or number, and can contain only letters, numbers, and the dash (-) character.Louis, I think it should be clarified that this is about a totally different service, not SMB.> https://docs.microsoft.com/en-us/windows/win32/fileio/naming-a-file?redirectedfrom=MSDN > > Not saying its wrong, but your prone to errors.. > I would not recommend it.Unlike on unix, spaces are a very regular part of windows and so SMB files, folders and share names. Samba certainly doesn't care, everything is a string to us, where the special characters are just those listed above as actually special (space isn't). The rules on share names there are (only): "Control characters in range 0x00 through 0x1F, inclusive, are illegal in a share name." Andrew Bartlett -- Andrew Bartlett http://samba.org/~abartlet/ Authentication Developer, Samba Team http://samba.org Samba Developer, Catalyst IT http://catalyst.net.nz/services/samba
Hai Andrew, Yes, its a total different service i showed. I use it because of the clear text there, and if everything is kept within these guidelines. You never see errors, thats all im saying, why i also said.. "its not wrong".. Its all about "haveing a trouble free" network, thats why i `adviced` not to use spaces.> > Samba certainly doesn't care, everything is a string to us, where the > special characters are just those listed above as actually special (space isn't).Sure, Samba not, and yes, i know about https://tools.ietf.org/html/draft-crhertel-smb-url-12#section-10 But that is not complete if you setup a network and I also take account off possible other software. And thats to hard to read for most people.. Per example, same thing, to prevent problems.. Its the same with DNS and AD design. https://support.microsoft.com/en-us/help/909264/naming-conventions-in-active-directory-for-computers-domains-sites-and And looking at table 6.2 here: https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-2000-server/cc959336(v=technet.10) So if you want to setup so its most compatible - hostname , min 1, max 15 characters, a-Z,0-9, - - DNS domain name, max total FQDN 254 characters, include the dot's. And 254-15, results in 239 characters left for the domain.tld part. So in this example, any 254 character long unc path is ok, right, no.. The FQDN for an Active Directory domain name is limited to 64 bytes. There is more to above in combination with the DNS RFC's. but that even more out of scope here. This is why i show these things. Im telling people this because, i run samba 4 now about 5 years, and im using samba over 18 year now. i upgraded as of 4.1.x All the way up, i have never/hardly problems, if i had one, its was a (samba) bug. I may not be a coder, but i do know my stuff of setting up stable networks, its only based on 30years being a sysadmin.. Please remember that. I dont want argue this but, please know, even then info i show a link that might not be 100% correct. The result will be a happy sysadmin with no problems with any software. But, i'll respect your comments, i'll post the correct link next time. I'll be more precise to the question asked, because even with 30y experiance, i still learn every day. Greetz, Louis