Recherche dans le site/ Search this Blog:

Login



Problem connecting to samba server (smbd) share after upgrading to samba 3.0.27 fixed Imprimer

We have an old SMB share server accessible only from our LAN mostly for testing purposes. We had tried to upgrade it to a recent secure version of samba before without success; we couldn't connect to the server anymore after the update forcing us to downgrade. Since we only connect internally to that test server, fixing this problem wasn't on our priority list but it had to be solved eventually, so here it is:

Our old server authenticated the users with credentials contained in the /etc/passwd file. It seems that newer version of samba keep the passwords required for authentication in its own passwd file now. We simply had to use the smbpasswd utility to set the passwords of the users accessing the shares.

Note : One needs to use the -a option to add users to the smbpasswd file.

We had to repeat the following steps for the few users we have :

Note: The user needs to exist already in your UNIX system by possessing an entry in the /etc/passwd file. We have a "dev" user defined in our /etc/passwd file so we could proceed with the creation of the "dev" user in the smbpasswd file.

root@dev:/var/log# smbpasswd -a dev

New SMB password:
Retype new SMB password:
Added user dev.
root@dev:/var/log#

Alternatively, One can also use the mksmbpasswd.sh to generate the smbpasswd file at once including all the users contained in your /etc/passwd file.

cat /etc/passwd | mksmbpasswd.sh > /etc/samba/smbpasswd

If you know or find out how to revert to the old behavior of samba where it tests directly against the UNIX /etc/passwd file, please post a comment at the bottom of this article.

 

 

 

Ajouter votre commentaire / Add your comment

Votre nom / Your name:
Sujet / Subject:
Commentaire:
SPAM: Ne pas inclure de lien ou utiliser le stratagème suivant: "yahoo.com slash mapage.html"     Nous utilisons un filtre qui bloque les commentaires suspects avec une erreur 403. De même, du code de programmation ou sql peut provoquer des erreurs 403. Veuillez utiliser un lien vers votre code tel que: "pastebin.com slash jVNqLieD"    Merci!
Comment:
SPAM: Do not include any links in your post or use the following construct: "yahoo.com slash mypage.html"    We are using a filter that denies suspicious posts with a 403 error. Programming language or SQL code may also cause a 403 error. Please provide a link to your code instead like: "pastebin.com slash jVNqLieD"    Thank you! :
  Lettres de vérification; lettres minuscules seulement, pas d
Retaper les lettres affichées / Word verification:
Mis à jour / Last updated ( samedi, 15 décembre 2007 19:03 )
 



Consultez TOUS nos fils d'actualité ici. / View ALL our newsfeed here.