I would say the best wey is to add:
map to guest = Bad User
why? because default settings of ubuntu smb.conf will allow user nobody
but will not allow any other user what not exist in /etc/passwd . With
nautilus this working because this has some workaround and it try to
login as $user and after it failed, will try to login as nobody or NULL.
windows xp do not do this second try. So we need to make it before.
See: man smb.conf
....
map to guest (G)
......
Bad User - Means user logins with an invalid password are
rejected, unless the username does not exist, in which case
it is treated as a guest login and mapped into the guest account.
.............
and
..................... SECURITY = USER
This is the default security setting in Samba 3.0. With user-
level security a client must first "log-on" with a valid user‐
name and password (which can be mapped using the username map
parameter). Encrypted passwords (see the encrypted passwords
parameter) can also be used in this security mode. Parameters
such as user and guest only if set are then applied and may
change the UNIX user to use on this connection, but only after
the user has been successfully authenticated.
I would say the best wey is to add:
map to guest = Bad User
why? because default settings of ubuntu smb.conf will allow user nobody
but will not allow any other user what not exist in /etc/passwd . With
nautilus this working because this has some workaround and it try to
login as $user and after it failed, will try to login as nobody or NULL.
windows xp do not do this second try. So we need to make it before.
See: man smb.conf
account. ....... .......
SECURITY = USER
....
map to guest (G)
......
Bad User - Means user logins with an invalid password are
rejected, unless the username does not exist, in which case
it is treated as a guest login and mapped into the guest
.............
and
.......
This is the default security setting in Samba 3.0. With user-
level security a client must first "log-on" with a valid user‐
name and password (which can be mapped using the username map
parameter). Encrypted passwords (see the encrypted passwords
parameter) can also be used in this security mode. Parameters
such as user and guest only if set are then applied and may
change the UNIX user to use on this connection, but only after
the user has been successfully authenticated.