I recently built a new storage tank using v 8.0.4
I have a large (10tb+) samba share configured for use by automated apps to save their database/configs.
The automated app uses the same user/pass and I have it configured as a local user.
If i make any sort of config change and restart samba the local user becomes "locked".
Now i use that because while the user seems fine it cannot login via cifs until i go on the command line and run smbpasswd -e <user>
and then it works fine.
In the app i get a bad credentials error until i run the smbpasswd -e command and then it works flawlessly until the next cifs restart
Now if i select a AD user for authenticating this share it works flawlessly. Restarting samba doesnt lock the account. Unfortunatly i cannot use AD auth with my app ui.
Any ideas on why this happens and how to fix?
I have a large (10tb+) samba share configured for use by automated apps to save their database/configs.
The automated app uses the same user/pass and I have it configured as a local user.
If i make any sort of config change and restart samba the local user becomes "locked".
Now i use that because while the user seems fine it cannot login via cifs until i go on the command line and run smbpasswd -e <user>
and then it works fine.
In the app i get a bad credentials error until i run the smbpasswd -e command and then it works flawlessly until the next cifs restart
Now if i select a AD user for authenticating this share it works flawlessly. Restarting samba doesnt lock the account. Unfortunatly i cannot use AD auth with my app ui.
Any ideas on why this happens and how to fix?
