[Samba] Samba 4 AD [homes] Share

[Rowland Penny]

On 16/01/14 17:42, Chan Min Wai wrote:
> I think this bugs is invalid.
> as home does work.
>
> Problem is it follow your linux home path definition.
>
> [homes]
>
> read only = No
>
> browseable = No
>
>
> smb.conf
>
>   winbind use default domain = Yes
>          template homedir = /home/%ACCOUNTNAME%
>          template shell = /bin/bash
>
>
>
>
> On Fri, Jan 17, 2014 at 1:23 AM, Márcio Merlone <marcio.merlone at a1.ind.br>wrote:
>
>> Opened a ticket on bugzilla:
>>
>> https://bugzilla.samba.org/show_bug.cgi?id=10385
>>
>> Best regards.
>>
>> Em 16-01-2014 09:18, Márcio Merlone escreveu:
>>
>>   Em 25-12-2013 15:25, Marc Muehlfeld escreveu:
>>>> Am 24.12.2013 13:06, schrieb Chan Min Wai:
>>>>
>>>>> Can help to advise what would be the [homes] share like for samba4 AD?
>>>>>
>>>> (...)
>>>> I wrote a HowTo some time ago:
>>>> http://wiki.samba.org/index.php/Setting_up_a_home_share
>>>>
>>>>> But On samba 4 I try the following but it don't work.
>>>> If you want to keep the old style homes, please give some more
>>>> information what doesn't work? Anything in the logs, etc.?
>>>>
>>> Hi,
>>>
>>> I am facing the same issue. On Samba 3.x a [homes] share (plural) would
>>> create a 'username' share for the user (\\server\username), but it no
>>> longer woks on Samba 4.1.4 (using Sernet's packages). When a user browser
>>> the server it sees an inaccessible share called - ta-da! - 'homes' and not
>>> its username.
>>>
>>> I am planning an upgrade of an old 3.x server using Ubuntu 12.04 LTS and
>>> Samba 4.14 Sernet's packages. Have already tested 4.0 using some ppa
>>> packages and self-compiled binaries with the same result.
>>>
>>> With this 2-line [homes] section:
>>> [homes]
>>> read only = no
>>>
>>> I get this log when browsing the server:
>>>
>>> [2014/01/15 15:55:09.588727,  2] ../source4/lib/socket/access.
>>> c:353(socket_check_access)
>>>    socket_check_access: Allowed connection to 'homes' from (192.168.0.153)
>>> [2014/01/15 15:55:09.589032,  0] ../source4/ntvfs/posix/vfs_
>>> posix.c:236(pvfs_connect)
>>>    pvfs_connect: '' is not a directory, when connecting to [HOMES]
>>>
>>> Using a path definition makes no difference. Should I fill a bug on Samba
>>> or on my brain? :)
>>>
>>> Thanks in advance, best regards.
>>>
>>>
>> --
>> *Marcio Merlone*
>> TI - Administrador de redes
>>
>> *A1 Engenharia - Unidade Corporativa*
>> Fone:   +55 41 3616-3797
>> Cel:    +55 41 9689-0036
>>
>> http://www.a1.ind.br/ <http://www.a1.ind.br>
>> --
>> To unsubscribe from this list go to the following URL and read the
>> instructions:  https://lists.samba.org/mailman/options/samba
>>
If you are using the winbind ad backend, it should pull the unix home 
directory from the very aptly named 'unixhomedirectory' attribute, 
provided that you have set it of course.

If you run  'getent passwd username' you should get something like this:

username:*:10000:100:username:/home/username:/bin/bash

With this, (and pam_mkhomedir in common-session) when a user logs into a 
linux machine, their home directory is created for them at /home/username.

Rowland