Samba authentication issue
by dravur from LinuxQuestions.org on (#5DK9H)
Good morning,
I am having a bear of a time with a Samba issue.
Only 1 Windows server needs to attach to this Linux server. It is a legacy Windows 2008 Server. The Linux server is a Red Hat 7.2 Server. Samba will not let anyone to access the system unless "Map to Guest" is enabled, which does allow anyone to see files on the linux server, but not run them, of course.
ON the Windows 2008 Server.
Both SMB1 and 2 are enabled.
Group Policy has "Send Password in Clear Text" Enabled. It is something like that...
The Linux Server has an smb.conf file as follows.
workgroup = FC
# workgroup = xxxx.local
# server string = %h server
server string = local
netbios name = <servername> ....Actual server name here....
# passwd program = /usr/bin/passwd %u
# passdb backend = tdbsam
log file = /var/log/samba/log.%m
# log file = /var/log/samba:wq/%m.log
# max log size = 0
security = user
# security = domain
passdb backend = tdbsam
# map to guest = bad user
# guest account = administrator
server max protocol = SMB2
# valid users =
# encrypt passwords = no
# passdb backend = smbpasswd:/etc/samba/smbpasswd.db
# encrypt passwords = yes
# smb passwd file = /etc/samba/smbpasswd
# unix password sync = Yes
# passwd program = /usr/bin/passwd %u
# passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*
# socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
dns proxy = no
The reason so many # marks is I have been trying various things.
here is one of the shares.
[PC]
comment = XXXX Development
path = /u/pgm/<name of dir>
public = yes
writeable = yes
create mask = 775
directory mask =775
force create mode = 775
force directory mode = 775
force user = <a user>
force group = <a group>
I have added the administrator user as sudo smbpasswd -a administrator.
I can ping back and forth by name and or ip.
Ihave run tests on Samba, Testparm, etc. Seems ok.
Now, here is where it gets weird. This used to work just fine and stopped working last month. I am not an expert on Samba, or even linus. This is an older legacy system, so please Obi Wan, you are our only hope.


I am having a bear of a time with a Samba issue.
Only 1 Windows server needs to attach to this Linux server. It is a legacy Windows 2008 Server. The Linux server is a Red Hat 7.2 Server. Samba will not let anyone to access the system unless "Map to Guest" is enabled, which does allow anyone to see files on the linux server, but not run them, of course.
ON the Windows 2008 Server.
Both SMB1 and 2 are enabled.
Group Policy has "Send Password in Clear Text" Enabled. It is something like that...
The Linux Server has an smb.conf file as follows.
workgroup = FC
# workgroup = xxxx.local
# server string = %h server
server string = local
netbios name = <servername> ....Actual server name here....
# passwd program = /usr/bin/passwd %u
# passdb backend = tdbsam
log file = /var/log/samba/log.%m
# log file = /var/log/samba:wq/%m.log
# max log size = 0
security = user
# security = domain
passdb backend = tdbsam
# map to guest = bad user
# guest account = administrator
server max protocol = SMB2
# valid users =
# encrypt passwords = no
# passdb backend = smbpasswd:/etc/samba/smbpasswd.db
# encrypt passwords = yes
# smb passwd file = /etc/samba/smbpasswd
# unix password sync = Yes
# passwd program = /usr/bin/passwd %u
# passwd chat = *New*password* %n\n *Retype*new*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*
# socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
dns proxy = no
The reason so many # marks is I have been trying various things.
here is one of the shares.
[PC]
comment = XXXX Development
path = /u/pgm/<name of dir>
public = yes
writeable = yes
create mask = 775
directory mask =775
force create mode = 775
force directory mode = 775
force user = <a user>
force group = <a group>
I have added the administrator user as sudo smbpasswd -a administrator.
I can ping back and forth by name and or ip.
Ihave run tests on Samba, Testparm, etc. Seems ok.
Now, here is where it gets weird. This used to work just fine and stopped working last month. I am not an expert on Samba, or even linus. This is an older legacy system, so please Obi Wan, you are our only hope.