[Samba] Samba 4 AD [homes] Share

[Chan Min Wai]

Dear All,

I've try a few week and found that. 
This basic config work...

[homes] valid users = %S 
read only = No 
browseable = No

But problem might try the following in your shell 
getent password
If you don't see your user and home dir there. Than you have a problem on the Linux part. 

They need to know the home dir
You might follow the guide below to configure winbind and etc. 

I've a guide on the link below 
http://wiki.gentoo.org/wiki/Samba4_Migrating/HOWTO
Look at the FAQ Q2

Thank you. 

Regards, 
Chan Min Wai 

> Rene van Schijndel <rvs at prisma-spo.nl> 於 16/01/2014 7:41 PTG 寫道：
> 
> I am using sernet samba 4.1.4 on centos 6.5.
> If i make the homes share with following entries that works fine.
> [homes]
> read only = no
> 
> Make sure the unixHomeDirectory entry exist in ldap.
> 
> I can acces the home share with \\server\user
> Dont use substitutions %H in the path name that does not work on samba 4.
> 
> 
> 
> 
> 
> 
>> Op 16 januari 2014 om 12:18 schreef Márcio Merlone <marcio.merlone at a1.ind.br>:
>> 
>> 
>> 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
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  https://lists.samba.org/mailman/options/samba