Troubleshooting of samba error in Linux configuration startup
- systemctl start SMB indicates an error and the firewall needs to be closed. Set SELinux to disabled through sudo VI/etc/SELinux/config, and systemctl start SMB succeeds again. Windows connects to Linux through samba and prompts an error. You need to turn off the firewall through sudo systemctl stop firewalld. Then, connect again and succeed ol>
Configuring Samba login users
Sudo smbpasswd – a username
sudo smbpasswd – A to add a user, the user to be added must already be a system user
sudo smbpasswd – D to freeze the user so that the user can no longer log in
sudo smbpasswd – e to restore the user, so that the frozen user can use
sudo smbpasswd – n to set the user’s password to null again
Read More:
- “Failed to find entry for user…” appears when Linux uses samba
- Modify samba configuration, restart service failed
- Troubleshooting of “disk I / O error” after startup
- Samba error: session setup failed: NT_ STATUS_ LOGON_ FAILURE
- Troubleshooting of errors in installing elasticsearch
- Linux configuration SFTP server
- Error in startup after the supervisor modifies the configuration file: error: cannot open an HTTP server: socket.error reported errno.eaddnotavail
- Configuration: error: no acceptable C compiler found in $path error in Linux installation file
- Troubleshooting of errors in the installation and use of scienceplots
- Add Samba user prompt failed to add entry for user
- Prompt when executing sh file in Linux: nohup: unable to run command “. / startup. Sh”: insufficient permissions
- “Failed to find entry for user…” appears when Samba is used
- Samba mount error (115): operation now in progress refer to the mount.cifs (8) manual page (e.g. ma
- Error report of mongodb startup under Linux
- Ubuntu 16.04 Samba shared folder
- Methods of exporting configuration and importing configuration in IntelliJ idea
- Add samba user prompt Failed to add entry for user.
- Linux7 hardware time occasionally encounter nonsense Powerpath startup error
- SteamVR error code 108/203/208/301/306/308/400/405 troubleshooting method
- Configuration error in mybatis configuration file