[also posted to comp.protocols.smb] I am running samba 2.0.7 on a solaris 2.8 machine, it is running as security=user to validate logins for a network of windows 98 workstations. I have no problems with this. I am having problems granting access to some shares on this system however. What I want to do is grant read/write access to shares on the basis of membership of secondary unix groups, and allow access to everyone else read only. If someone has this running can you e-mail me your smb.conf, so I can diff them and try and work out whats going on? I'm fairly sure what I need to do is as below for the share, I think there is something incorrect with my guest user setup.
Alex Madden wrote: snip> What I want to do is grant read/write access to shares on the basis of > membership of secondary unix groups, and allow access to everyone else > read only. If someone has this running can you e-mail me your smb.conf, so > I can diff them and try and work out whats going on?snip> [global]snip> guest account = guestsnip> [clients] > comment = Clients > valid users = @ovatedev > create mode = 0775 > directory mode = 0775 > path = /usr/local/documents/clients > writeable = yes > guest ok = yesI think valid users overrides your guest ok parameter. I'd set writeable to no and use "write list = @ovatedev" instead of valid users. I'd also suggest force group = +ovatedev. Then all users who can authenticate against your samba server should be able to read from the clients share, but only ovatedev members can write to it. Doesn't explain your guest account problem though. Have you reset your guest smbpasswd making sure it's the same as your Windows guest password? Lynn Danielson