search for: authentisation

...99:99:Nobody:/: And this is where things go bad: Samba gives access to directories I do not want it to, for example / meaning the whole directory tree of my server. Is this intended to work this way? I would have expected that the conection is made to the home directory of the user used for the authentisation. The above works with 1.9.18p10 on solaris 2.3 (encrypted passwords and security = server) and with 2.0.6 on linux (RedHat, encryped passwords, the password server for the solaris machine; the system acconts are not in smbpasswd). And it works with 2.0.6 on aix 4.3. Is there a way to configure...

I just went through upgrading from 2.0.7 on Redhat 7.0 using the binary RPM provided by samba.org and noticed a problem with the swat install. It seems that the swat binary in the RPM is built to look for it's supporting files in /usr/share/samba/swat whereas the RPM installs said files in /usr/share/swat. This results in the following error message when you try to access swat: 400 Server

...ty=user > encrypt passwords = Yes > min password length = 6 > smb passwd file = /usr/local/samba/private/smbpasswd > passwd program = /usr/bin/passwd %u > passwd chat = *new*UNIX*password* %n\n *Retype*new*UNIX*password* %n\n *changed* My RedHat-System responds with "all authentisation tokens updated sucessfully", this way "changed" can't work. Have a look at your manual Linux password change. > unix password sync = Yes > domain logons = Yes > os level = 65 > preferred master = Yes > domain master = Yes > wins support = Yes > >...