Skip to main content

Centos Samba failed to add user




Adding Samba users to Linux Centos box or other Linux distro fails. 

If a user account name, added to Samba does not have an account on the Linux box, then creation of the Samba user account will fail.

So before adding user accounts to Samba, create an account for the user on the Linux box.

Do these steps below:

Adduser account to Linux:
1. adduser  'user_name' --- create a user account

    adduser --system --no-create-home user_name

man adduser - for more info
adduser --help
adduser --info 
apropos adduser

You may need to add sudo before the command if you're running Ubuntu.

Or check the documentation of your Linux distro on how to add user account.

Now that a user account has been created, add the user account to Samba. 

2. smbpasswd -a user_name  (the user name that was created on Step 1)

man smbpasswd - for more info
smbpasswd --help
smbpasswd --info
apropos smbpasswd
If everything goes well, then creation of user account in Samba should be okay. 

If local user account is not present on the Linux box, then smbpasswd command will show this error " failed to add entry for the user".

So a local user account is needed before adding Samba user account.

If Samba "smb.conf" file is properly configured and all Samba ports has been forwarded or correctly set on the firewall. And still Samba does not work.

For CentOS/RedHat try: yum samba reinstall

Test and check whether Samba is working.


Hope this helps someone. Cheers! Till next time.

================================
Free Android Apps:

Click on links below to find out more:

Linux Android App cheat sheet:



Catholic Rosary Guide  for Android:


Divine Mercy Chaplet Guide (A Powerful prayer):

Labels

Labels:

Comments

Post a Comment

Popular posts from this blog

WMIC get computer name

WMIC get computer model, manufacturer, computer name and  username. WMIC is a command-line tool and that can generate information about computer model, its manufacturer, its username and other informations depending on the parameters provided. Why would you need a command line tool if there’s a GUI to check? If you have 20 or 100 computers, or even more. It’s quite a big task just checking the GUI to check the computer model and username. If you have remote computers, you need to delegate someone in the remote office or location to check. Or you can just write a batch file or script to automate the task. Here’s the code below on how get computer model, manufacturer and the username. Open an elevated command prompt and type:     wmic computersystem get "Model","Manufacturer", "Name", "UserName" Just copy and paste the code above, the word “computersystem” does not need to be change to a computer name. A...
Post a Comment
Read more

Print error 016-799 - Fuji Film Xerox

016-799 Fuji Xerox or Fuji Film print error code. That shows a description error as “Print instruction Fail detected in decomposer.” The error code and error description are alien languages for users and even system administrators who are not familiar with Fuji Xerox error code. The error code is quite simple and easy to fix, if the job print goes to the printer but print out doesn’t come out. So, basically the print job was received by the printer, but the printer just doesn’t know what type of paper or what size to use or which tray to utilize for the print out. In some instances, this is just a paper mismatch but the error description; if using Windows 10 to print does not exactly points to what is the issue. First thing to check, is the paper size selected by the user to print. Example, if the printer configuration is A3 and A4 sizes only. But then the person printing the file accidentally chooses “A4 Cover” then this error 016-799 will occur. ...
6 comments
Read more

How to check office version from command line

The are quite a few ways to check office version it can be done via registry, PowerShell or VBScript and of course, good old command line can also do it. Checking Windows office version whether it is Office 2010, Office, 2013, Office 2016 or other version is quite important to check compatibility of documents; or just a part of software inventory. For PowerShell this simple snippet can check the office version: $ol = New-Object -ComObject Excel.Application $ol . Version The command line option will tell you where’s the path located; the result will also tell whether office is 32-bit, 64-bit and of course the version of the office as well. Here’s the command that will check the office version and which program directory the file is located which will tell whether it’s 32-bit or 64-bit. Command to search for Excel.exe: DIR C:\ /s excel.exe | find   /i "Directory of"  Above command assumes that program files is on  C: drive. Sample O...
Post a Comment
Read more