A Windows net use command works fine when there is a password but with no password set via 'smbpasswd -n <user>' I get:

System error 2148073478 has occurred.

Here's my smb.conf file:

[global]
workgroup = TESTIMAG
server string = Samba Server Version %v
log file = /var/log/samba/log.%m
max log size = 50
encrypt passwords = Yes
null passwords = Yes
debug uid = Yes
admin users = root
create mask = 0666
directory mask = 0777
security = user
passdb backend = tdbsam
# added after incorrect password error
ntlm auth = true

[IMAGES]
comment = Production Images
path = /images/base
write list = +imgrw, +img2, +img3
read only = No
hosts allow = 10.9.1. 10.101.10. 192.168.131.115

Which Windows version? Just wondering if the encrypted password policy may be at play here.

1 members found this post helpful.

Windows 10, but it works with the old server running Samba 3. By 'encrypted password policy' I assume you're referring to a Windows setting? I'll do a search on that and see if changing the setting has any effect.

Both 'encrypt passwords = Yes' and 'null passwords = Yes' in smb.conf get a warning that they are deprecated when I run testparm on the new Linux server. Any time I encountered 'deprecated' it meant it's going away but still works, so I assume that's the case here.

Another problem is it's an odd setup, user IDs but no passwords, so I haven't been able to find much searching google and this site. Most people are interested in setting up a share with no IDs or passwords, or if they use ID's they're using passwords as well.

I don't like the way it's set up, but there's a big rush to get off a very old version of Linux and Samba and I thought I'd get there first before revamping anything.

Thanks for the reply.

Encrypted passwords have been the default since samba 3.0.0 so there is no need to use 'encrypt passwords = yes' anyway. Since the users are not using passwords, you could consider implementing guest accessible shares perhaps?

https://wiki.samba.org/index.php/Set..._smb.conf_File

I'm not sure how 'null passwords' behaviour should be (never used it), but you could liaise with the samba team perhaps..
https://wiki.samba.org/index.php/Bug_Reporting

1 members found this post helpful.

Thanks. I figured out the easiest way to fix this is not to fix it at all. I'm just going give every account the same password. The Windows server admin just needs to add a password to their 'net use' command. It also adds a slight bit more security if someone unauthorized managed to get into their network. Right now the only security is the shares are restricted by subnet.

The proper way to do this would be to just use Windows domain credentials. The problem is this type of change could end up being a long drawn out process with this particular department (long story as to why).