samba - Jun 2019 - AD home drive

Hi Rowland,

Initially I deposited the line towards the bottom but then it didn't work.
The line wasn't getting enough attention so it decided to creep up a bit :)
As suggested in the initial email, the box was a NT4 PDC which had the all the
shares. The home drive pointed to /home/%U/samba.

Looking at the logs, to me it looks like the default smb.conf template (as
suggested by Louis) doesn't match the homes definition

Regards,

Praveen


-----Original Message-----
From: samba [mailto:samba-bounces at lists.samba.org] On Behalf Of Rowland penny
via samba
Sent: Friday, 14 June 2019 6:19 PM
To: sambalist
Subject: Re: [Samba] AD home drive

On 14/06/2019 07:40, Praveen Ghimire wrote:
> Hi Rowland,
>
> I've added the bit to the pam.d and rebooted the server but still no 
> go
>
> The following is from the log file for the machine (user is testhome2)
>
> adding home's share [VM-WIN7-01$] for user 'LIN\VM-WIN7-01$' at
'/home/%U/samba'
>
> get_auth_event_server: Failed to find 'auth_event' registered on
the
> message bus to send JSON authentication events to: 
> NT_STATUS_OBJECT_NAME_NOT_FOUND
>
> Adding homes service for user 'LIN\testhome2' using home directory:
'/home/LIN/testhome2'
>
> canonicalize_connect_path failed for service testhome2, path 
> /home/testhome2/samba
>
>
> pam.d/common-session
>
> # here are the per-package modules (the "Primary" block)
> session [default=1]                     pam_permit.so
> # here's the fallback if no module succeeds
> session requisite                       pam_deny.so
> # prime the stack with a positive return value if there isn't one 
> already; # this avoids us returning an error just because nothing sets 
> a success code # since the modules above will each just jump around
> session required                        pam_permit.so
> session    required   pam_mkhomedir.so skel=/etc/skel/ umask=0022
> # The pam_umask module will set the umask according to the system 
> default in # /etc/login.defs and user settings, solving the problem of 
> different # umask settings with different shells, display managers, remote
sessions etc.
> # See "man pam_umask".
> session optional                        pam_umask.so
> # and here are more per-package modules (the "Additional" block)
> session required        pam_unix.so
> session optional                        pam_winbind.so
> session optional        pam_systemd.so
> # end of pam-auth-update config
I said 'add' it, not plonk it into the middle of the file ;-)

Also your path is a bit suspect, I would expect '/home/samba/%U' and
'/home/samba' would have to exist.

Rowland


--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/options/samba

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________

On 14/06/2019 11:30, Praveen Ghimire wrote:
> Hi Rowland,
>
> Initially I deposited the line towards the bottom but then it didn't
work. The line wasn't getting enough attention so it decided to creep up a
bit :)
> As suggested in the initial email, the box was a NT4 PDC which had the all
the shares. The home drive pointed to /home/%U/samba.
>
> Looking at the logs, to me it looks like the default smb.conf template (as
suggested by Louis) doesn't match the homes definition
>
> Regards,
>
> Praveen
>
>
My mistake, you want the users home directory created when the user 
connects via Samba, this doesn't work via PAM. You need to investigate 
the 'root preexec' parameter in 'man smb.conf'

Rowland

On 6/14/19 5:30 AM, Praveen Ghimire via samba wrote:
> Initially I deposited the line towards the bottom but then it didn't
work. The line wasn't getting enough attention so it decided to creep up a
bit :)
PAM configuration is very, very temperamental.  Unless you know exactly 
what you're doing you'll probably lock yourself out of your system.

I suggest either taking some time to learn how PAM works or enlisting 
the help of a friend who does.  Just randomly placing lines in a PAM 
file is almost guaranteed not to work.

On 14/06/2019 16:57, Goetz, Patrick G via samba wrote:
> On 6/14/19 5:30 AM, Praveen Ghimire via samba wrote:
>> Initially I deposited the line towards the bottom but then it
didn't work. The line wasn't getting enough attention so it decided to
creep up a bit :)
> PAM configuration is very, very temperamental.  Unless you know exactly
> what you're doing you'll probably lock yourself out of your system.
>
> I suggest either taking some time to learn how PAM works or enlisting
> the help of a friend who does.  Just randomly placing lines in a PAM
> file is almost guaranteed not to work.
>
>
If he had logged in via SSH, it would have worked with the line at the 
bottom, but it seems that isn't the way the OP was trying to connect, he 
was trying to connect via Samba and Samba doesn't use PAM. He needs to 
use 'root preexec' in smb.conf with a script to create the users 
directory if it doesn't exist.

Rowland