How can the risk of UID/GID inconsistencies be avoided across UNIX/Linux systems that are sharing information over protocols other than SMB/CIFS (eg: NFS)?
While attempting to create a user in the Samba database, the following message appeared:
# smbpasswd -a john
New SMB password:
Retype new SMB password:
...
Failed to initialise SAM_ACCOUNT for user john. Does this user exist in the UNIX password database?
Failed to modify password entry for user john
Select the correct explanation for why this error occurred.
The configuration below is contained in the Samba main configuration file:
[homes]
comment = Home folder
writable = yes
browseable = no
valid users = %S
However, an attempt at listing the share with smbclient didn't work. Which TWO options below could be
possible reasons for this?
A software vendor states that their SMB client software may perform better if the maximum packet size of SMB commands is limited to 32768 bytes. How would Samba be instructed to limit the size of requests it will accept?