Dear list, I have a Sun running Samba 2.0.7 that I recently switched from security=share to security=user. I have about 200 users who connect locally, situated on a private network 172.17.0.0/16. On top of that, I have about 200 more users who connect through VPNs, but I inherited a weird topology, and so they have addresses like 192.168.113.192/6, 192.168.114.0/4, 192.168.114.16/4 and so on. Before, when security=share, they were able to connect to various 'guest ok=yes' shares, but now that security=user, they are locked out. What can I do to let them have access again? Do I have to create user accounts for all of them on the Sun, or is there some other way around this (given that they won't ever use any authenticated shares). Thanks for the clues, David Landgren
[David LANDGREN <david.landgren@bpinet.com>]> Before, when security=share, they were able to connect to various > 'guest ok=yes' shares, but now that security=user, they are locked > out. What can I do to let them have access again? Do I have to create > user accounts for all of them on the Sun, or is there some other way > around this (given that they won't ever use any authenticated > shares).Investigate map to guest = bad user which may well be what you want. Peter
|[David LANDGREN <david.landgren@bpinet.com>]
|> Before, when security=share, they were able to connect to various
|> 'guest ok=yes' shares, but now that security=user, they are locked
|> out. What can I do to let them have access again? Do I have to create
|> user accounts for all of them on the Sun, or is there some other way
|> around this (given that they won't ever use any authenticated
|> shares).
|
|Investigate
|
| map to guest = bad user
|
|which may well be what you want.
I managed to figure this out by myself (isn't this always the way?)
Curiously enough, the only thing I had to do was
[global]
hosts allow = 172.xxx. 192.168.xxx. 192.168.xxx.
David