I have installed Samba 2.0.7 (downloaded from QUICS) and it works fine
so long as I do not have to use passwords to authenticate users.
Some of the parameters I use in my smb.conf are:
[global]
security = share
null passwords = Yes
encrypt passwords = No
…
[test]
comment = Test
path = /tmp
I have tried all tests suggested in DIAGNOSIS.txt, even more extensive
tests from the ‘Using Samba’ book, read various FAQs and still cannot
solve the problem.
If I use smbclient locally, I can connect if specifying username that
does not have password. If I specify a username which requires
password, then I get ‘ERRbadpw’. I also get ‘Incorrect password’ from
net use under Win95 client.
As far as I can gather from looking at the log file, passwords supplied
by Win95 client are not encrypted. And I had the same Win95 client
connecting to the older version of Samba (1.9.16).
One of the Samba versions I got off the QNX site (1.9.18p10) was hardcoded
to access /etc/master.passwd instead of /etc/shadow. The binary in the
download worked, but when I rebuilt it from the source it didn’t. When I
changed the source it started working. I don’t know who put it there, or how
it happened, but the binary clearly wasn’t built from the source that came
with it. Maybe you’ve got a similar issue.
I have installed Samba 2.0.7 (downloaded from QUICS) and it works fine
so long as I do not have to use passwords to authenticate users.
Some of the parameters I use in my smb.conf are:
[global]
security = share
null passwords = Yes
encrypt passwords = No
…
[test]
comment = Test
path = /tmp
I have tried all tests suggested in DIAGNOSIS.txt, even more extensive
tests from the ‘Using Samba’ book, read various FAQs and still cannot
solve the problem.
If I use smbclient locally, I can connect if specifying username that
does not have password. If I specify a username which requires
password, then I get ‘ERRbadpw’. I also get ‘Incorrect password’ from
net use under Win95 client.
As far as I can gather from looking at the log file, passwords supplied
by Win95 client are not encrypted. And I had the same Win95 client
connecting to the older version of Samba (1.9.16).
On QUICS there should also be a readme accompanying the tgz file.
Somehow I don’t see that through my browser. However via telnet it can
be found under
Anyway, in the readme file there’s a clear note stating that this
version was linked with QNX’s new encryption algorithm. You should
either upgrade your system with the new security patch from QUICS
(preferably), or you can create a new style encrypted password string
(using a util which uses this new algorithm, or on an already patched
system) and than manually add this to your shadow file for your samba
account.
I have installed Samba 2.0.7 (downloaded from QUICS) and it works fine
so long as I do not have to use passwords to authenticate users.
Some of the parameters I use in my smb.conf are:
[global]
security = share
null passwords = Yes
encrypt passwords = No
…
[test]
comment = Test
path = /tmp
I have tried all tests suggested in DIAGNOSIS.txt, even more extensive
tests from the ‘Using Samba’ book, read various FAQs and still cannot
solve the problem.
If I use smbclient locally, I can connect if specifying username that
does not have password. If I specify a username which requires
password, then I get ‘ERRbadpw’. I also get ‘Incorrect password’ from
net use under Win95 client.
As far as I can gather from looking at the log file, passwords supplied
by Win95 client are not encrypted. And I had the same Win95 client
connecting to the older version of Samba (1.9.16).
Have you also installed the security fix talked about recently on this group
and recently released/anounced?
I believe it is necessary for this version of Samba Binaries.
-Paul
I have installed Samba 2.0.7 (downloaded from QUICS) and it works fine
so long as I do not have to use passwords to authenticate users.
Some of the parameters I use in my smb.conf are:
[global]
security = share
null passwords = Yes
encrypt passwords = No
…
[test]
comment = Test
path = /tmp
I have tried all tests suggested in DIAGNOSIS.txt, even more extensive
tests from the ‘Using Samba’ book, read various FAQs and still cannot
solve the problem.
If I use smbclient locally, I can connect if specifying username that
does not have password. If I specify a username which requires
password, then I get ‘ERRbadpw’. I also get ‘Incorrect password’ from
net use under Win95 client.
As far as I can gather from looking at the log file, passwords supplied
by Win95 client are not encrypted. And I had the same Win95 client
connecting to the older version of Samba (1.9.16).