samba - Aug 2015 - samba shares does not exist or permission denied when connecting

On 24/08/15 10:49, Sundeep Singh Nanuwa wrote:
> Hi,
>
> Is there any issues using spaces in directories paths?
>
> On 21/08/15 11:06, Sunny wrote:
>> Hi,
>>
>> We have the following shares listed in smb.conf
>>
>> users cannot access the samba share directly i.e.
>>
>> \\sambaserver\rixilr
>> or
>> \\sambaserver\bridges
>>
>> error messages
>>
>> '/ibe/dusty/RIXILE Share/Bridges' does not exist or permission
denied
>> when connecting to [bridges] Error was Permission denied
>> Aug 21 10:09:12 dish sambaserver[27859]: [2015/08/21 
>> 10:09:12.964101,  0] smbd/service.c:1092(make_connection_snum)
>>
>> however if the user browses to \\sambaserver\dusty - they're able
to
>> access the path to [rixile] and [bridges] within that share - 
>> permissions work.
>>
>>
>> [dusty]
>>        path = /ibe/dusty
>>        force create mode = 764
>>        guest ok = no
>>        writable = yes
>>        printable = no
>>        write list = @dusty
>>
>> [rixile]
>>         path = "/ibe/dusty/RIXILE Share/RIXILE"
>>         force create mode = 764
>>         guest ok = no
>>         writable = yes
>>         printable = no
>>         write list = @rixileadmin
>>
>> [bridges]
>>         path = "/ibe/dusty/RIXILE Share/Bridges"
>>         force create mode = 764
>>         guest ok = no
>>         writable = yes
>>         printable = no
>>         write list = @rixileadmin
>>
>> Any advise on what's going wrong?
>>
>> Regards
>>
>>
>
>
Well yes, you are storing the share on Unix and the space is treated as 
a delimiter.

If I start in my home dir and try and create a directory with a space in 
the name:

mkdir test dir

I end up with ./test and ./dir

mkdir "test dir"

however does create ./test dir

I can also do:

mkdir anothertest\ dir

this works as well

But if try to cd into the dir with a space in its name

cd test dir

then run:

pwd

I find I am in:

/home/rowland/test

OK, back to the start:

cd

Lets try again,

cd test\ dir

and now pwd tells me I am in:

/home/rowland/test dir

So you see, whilst windows doesn't mind spaces in dir & file names, Unix
does, you need to escape the spaces.

Rowland

In the smb.conf I have escaped the path to a samba share in quotes.

path = "/ibe/dusty/RIXILE Share/RIXILE"

all the users needs to do is go to

\\sambaserver\rixilr

but get's the following error message

does not exist or permission denied when connecting to [rixilr] Error 
was Permission denied

Is this correct syntax?

On 24/08/15 11:18, Rowland Penny wrote:
> On 24/08/15 10:49, Sundeep Singh Nanuwa wrote:
>> Hi,
>>
>> Is there any issues using spaces in directories paths?
>>
>> On 21/08/15 11:06, Sunny wrote:
>>> Hi,
>>>
>>> We have the following shares listed in smb.conf
>>>
>>> users cannot access the samba share directly i.e.
>>>
>>> \\sambaserver\rixilr
>>> or
>>> \\sambaserver\bridges
>>>
>>> error messages
>>>
>>> '/ibe/dusty/RIXILE Share/Bridges' does not exist or
permission
>>> denied when connecting to [bridges] Error was Permission denied
>>> Aug 21 10:09:12 dish sambaserver[27859]: [2015/08/21 
>>> 10:09:12.964101,  0] smbd/service.c:1092(make_connection_snum)
>>>
>>> however if the user browses to \\sambaserver\dusty - they're
able to
>>> access the path to [rixile] and [bridges] within that share - 
>>> permissions work.
>>>
>>>
>>> [dusty]
>>>        path = /ibe/dusty
>>>        force create mode = 764
>>>        guest ok = no
>>>        writable = yes
>>>        printable = no
>>>        write list = @dusty
>>>
>>> [rixile]
>>>         path = "/ibe/dusty/RIXILE Share/RIXILE"
>>>         force create mode = 764
>>>         guest ok = no
>>>         writable = yes
>>>         printable = no
>>>         write list = @rixileadmin
>>>
>>> [bridges]
>>>         path = "/ibe/dusty/RIXILE Share/Bridges"
>>>         force create mode = 764
>>>         guest ok = no
>>>         writable = yes
>>>         printable = no
>>>         write list = @rixileadmin
>>>
>>> Any advise on what's going wrong?
>>>
>>> Regards
>>>
>>>
>>
>>
>
> Well yes, you are storing the share on Unix and the space is treated 
> as a delimiter.
>
> If I start in my home dir and try and create a directory with a space 
> in the name:
>
> mkdir test dir
>
> I end up with ./test and ./dir
>
> mkdir "test dir"
>
> however does create ./test dir
>
> I can also do:
>
> mkdir anothertest\ dir
>
> this works as well
>
> But if try to cd into the dir with a space in its name
>
> cd test dir
>
> then run:
>
> pwd
>
> I find I am in:
>
> /home/rowland/test
>
> OK, back to the start:
>
> cd
>
> Lets try again,
>
> cd test\ dir
>
> and now pwd tells me I am in:
>
> /home/rowland/test dir
>
> So you see, whilst windows doesn't mind spaces in dir & file names,
> Unix does, you need to escape the spaces.
>
> Rowland
>

On 24/08/15 12:41, Sunny wrote:
> In the smb.conf I have escaped the path to a samba share in quotes.
>
> path = "/ibe/dusty/RIXILE Share/RIXILE"
>
> all the users needs to do is go to
>
> \\sambaserver\rixilr
>
> but get's the following error message
>
> does not exist or permission denied when connecting to [rixilr] Error 
> was Permission denied
>
> Is this correct syntax?
>
> On 24/08/15 11:18, Rowland Penny wrote:
>> On 24/08/15 10:49, Sundeep Singh Nanuwa wrote:
>>> Hi,
>>>
>>> Is there any issues using spaces in directories paths?
>>>
>>> On 21/08/15 11:06, Sunny wrote:
>>>> Hi,
>>>>
>>>> We have the following shares listed in smb.conf
>>>>
>>>> users cannot access the samba share directly i.e.
>>>>
>>>> \\sambaserver\rixilr
>>>> or
>>>> \\sambaserver\bridges
>>>>
>>>> error messages
>>>>
>>>> '/ibe/dusty/RIXILE Share/Bridges' does not exist or
permission
>>>> denied when connecting to [bridges] Error was Permission denied
>>>> Aug 21 10:09:12 dish sambaserver[27859]: [2015/08/21 
>>>> 10:09:12.964101,  0] smbd/service.c:1092(make_connection_snum)
>>>>
>>>> however if the user browses to \\sambaserver\dusty -
they're able
>>>> to access the path to [rixile] and [bridges] within that share
-
>>>> permissions work.
>>>>
>>>>
>>>> [dusty]
>>>>        path = /ibe/dusty
>>>>        force create mode = 764
>>>>        guest ok = no
>>>>        writable = yes
>>>>        printable = no
>>>>        write list = @dusty
>>>>
>>>> [rixile]
>>>>         path = "/ibe/dusty/RIXILE Share/RIXILE"
>>>>         force create mode = 764
>>>>         guest ok = no
>>>>         writable = yes
>>>>         printable = no
>>>>         write list = @rixileadmin
>>>>
>>>> [bridges]
>>>>         path = "/ibe/dusty/RIXILE Share/Bridges"
>>>>         force create mode = 764
>>>>         guest ok = no
>>>>         writable = yes
>>>>         printable = no
>>>>         write list = @rixileadmin
>>>>
>>>> Any advise on what's going wrong?
>>>>
>>>> Regards
>>>>
>>>>
>>>
>>>
>>
>> Well yes, you are storing the share on Unix and the space is treated 
>> as a delimiter.
>>
>> If I start in my home dir and try and create a directory with a space 
>> in the name:
>>
>> mkdir test dir
>>
>> I end up with ./test and ./dir
>>
>> mkdir "test dir"
>>
>> however does create ./test dir
>>
>> I can also do:
>>
>> mkdir anothertest\ dir
>>
>> this works as well
>>
>> But if try to cd into the dir with a space in its name
>>
>> cd test dir
>>
>> then run:
>>
>> pwd
>>
>> I find I am in:
>>
>> /home/rowland/test
>>
>> OK, back to the start:
>>
>> cd
>>
>> Lets try again,
>>
>> cd test\ dir
>>
>> and now pwd tells me I am in:
>>
>> /home/rowland/test dir
>>
>> So you see, whilst windows doesn't mind spaces in dir & file
names,
>> Unix does, you need to escape the spaces.
>>
>> Rowland
>>
>
seeing as the share is stored on a Unix machine, you would probably 
better off doing this:

mv /ibe/dusty/RIXILE\ Share to /ibe/dusty/RIXILE_Share

and then update the share in smb.conf to reflect this, reload or restart 
samba

Rowland