"map to guest" seems to be ignored when "security = server". "map to guest" works when "security = user" and a local smbpasswd file is used. When using "security = server", attempting to connect to a guest accessable share with a non-existant account and an incorrect password, the connection fails: % smbclient '\\stampy\public' mypass -U phoneyuser added interface ip=132.177.137.23 bcast=132.177.139.255 nmask=255.255.252.0 session setup failed: NT_STATUS_LOGON_FAILURE Changing smb.conf to 'security = user' allowes access with the bad password: % smbclient '\\stampy\public' mypass -U phoneyuser added interface ip=132.177.137.23 bcast=132.177.139.255 nmask=255.255.252.0 Domain=[CENTERS] OS=[Unix] Server=[Samba 3.0.0] smb: \> quit
It is not possible to fix this, as the server will not tell us if the error was bad password, or bad user. Map to guest = 'bad password' should still work. This is one of the many, very good reason why 'security=server' should never be used. Try 'security=domain' or 'security=ads' instead.
database cleanup