samba - Feb 2020 - Newbie question: Spaces in share names

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

Am 04.02.20 um 22:12 schrieb James Cartner-Young (Sandal Computers) via
samba:
> 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.
as admin just remove space and shift key from yor keyboard, it's that easy

spaces have all sort of side effects depending on the client application
and always hd - i would prefer smbd just exit with a fatal error

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
>

Hi,

Thank you for your replies.

I still feel non the wiser - one person requests I don't (because client 
problems) and another saying they experience no problems.

However, strangely, after I checked the 'Bookmark' on my desktop, it had
been changed to point to an actual file! (the displayed path and icon 
remained the same, though.)

After I removed and re-added the 'Bookmark', the SMB path now opens fine
in Libr? Office...

No idea what changed the bookmark's location (or could), but it was 
pointing to an '.ods' file, which seems strange - Maybe it was Libr? 
Office which changed the bookmark? idk

However, thank you both, again, for responding my questions so quickly 
and apologies for wasting your time.

I feel this is yet another Linux quirk I'll have to live with.

James

On 04/02/2020 21:41, Luke Barone wrote:
> 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 <mailto: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
>