Ubuntu – Samba user login

sambaUbuntuuser-accounts

some help needed.

I have/manage a samba share at work. It works fine for everyone except one user. I've tried all I can think now, so now I hope for some new input.

$smbclient --list LOCALHOST

as my user works fine.

$smbclient --list LOCALHOST --user charlottepa

just gives me "session setup failed: NT_STATUS_LOGON_FAILURE".

any other user works just fine, but not this one. I've tried to set the password again with both "passwd" and "smbpasswd -a" and restarted the smbd after the change. No luck.

tail /var/log/samba/log.172.20.107.5 (the localhost)

[2015/09/15 17:14:09.756209,  0] ../source3/smbd/smbXsrv_session.c:1265(smbXsrv_session_update)
  smbXsrv_session_update: global_id (0xefcb8bb0) store failed - NT_STATUS_INVALID_PARAMETER
[2015/09/15 17:14:09.756269,  0] ../source3/smbd/sesssetup.c:374(reply_sesssetup_and_X_spnego)
  smb1: Failed to update session for vuid=62513 - NT_STATUS_INVALID_PARAMETER

How can I reset her access so that she can use or samba share again?

Server=[Samba 4.1.6-Ubuntu]
It's an Ubuntu 14.04 LTS server. (3.13.0-62-generic)

Best Answer

I finally manage to solve the problem. Using "pdbedit -L" I found that names containing Swedish characters didn't display properly. And after changing them with "pdbedit -r --fullname" it now works. I did write the same name again, but now they display correctly. So it looks like perhaps Samba changed the encoding for the user database.

Maybe this can help someone else.

Related Solutions

Linux – Problem connecting to a Samba server with share mode security

I think that you need to re-examine whether share-mode security is what you actually need for this problem. Share mode security means that a password is used to authenticate to a share, not a username/password combination.

If you want to allow multiple users (logging in as themselves) access to modify the files then you need to use user level security.

If you want to allow anybody that knows the magic password to see the share, then share mode security is right for you.

See the Samba Documentation for more information on share level security.

Samba – User in passdb, but getpwnam() fails!

SOLVED!!!!!!!!!!!

I have a script that was starting Samba (NMBD, SMBD) as well as OpenLDAP (SLAPD). It's an RC script that reads configuration data from a file to determine, among other things, which processes are already running or if a dependent process fails to start, etc... Here is a snippet of the relevant part in the script. The last line copies a version of the nsswitch.conf into place that specifies to use LDAP lookups.

while [ $i -lt $MAXPROCS ];
  do
   PID=${PROC[$i]}
   StartProc $PID

   if test $? != 0; then
    echo "!!! Aborting Any Remaining Start-up Processes !!!"
    exit 1
   fi

  i=$(($i+1))
done

 cp /etc/rc.d/pozix/nsswitch.conf.ldap /etc/nsswitch.conf

And upon shutdown I was doing the following; notice I copy a nsswitch.conf file that has "noldap" entries in it.

while [ $i -lt $MAXPROCS ];
do
  PID=${PROC[$i]}
  StopProc $PID
  i=$(($i+1))
done

cp /etc/rc.d/pozix/nsswitch.conf.noldap /etc/nsswitch.conf

It turns out that in the start-up scenario, samba wants the nsswtich.conf content to have the ldap entries there prior to invocation. Here is what I did to fix my issues:

cp /etc/rc.d/pozix/nsswitch.conf.ldap /etc/nsswitch.conf

while [ $i -lt $MAXPROCS ];
  do
   PID=${PROC[$i]}
   StartProc $PID

   if test $? != 0; then
    cp /etc/rc.d/pozix/nsswitch.conf.noldap /etc/nsswitch.conf
    echo "!!! Aborting Any Remaining Start-up Processes !!!"
    exit 1
   fi

  i=$(($i+1))
done

In summary, it appears that how you start SMBD is just as important as when you start it. If you start SMBD when nsswitch.conf has no LDAP entries, you get a version of smbd running linked to nss_ldap.so thinking it should only rely upon /etc/passwd (if that is all that is in the nsswitch.conf file) and changing the nsswitch.conf contents after SMBD is running has no effect.

Hope this helps other system builders....

Related Topic