Bug 726 - Guest account = yes does not work if security = server and Windows user is not in UNIX password file
Summary: Guest account = yes does not work if security = server and Windows user is no...
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: User/Group Accounts (show other bugs)
Version: 3.0.0
Hardware: All Solaris
: P3 normal
Target Milestone: none
Assignee: Tim Potter
QA Contact:
: 576 (view as bug list)
Depends on:
Reported: 2003-11-06 14:16 UTC by Ed Fortin
Modified: 2005-11-14 09:31 UTC (History)
2 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Ed Fortin 2003-11-06 14:16:48 UTC
A user connecting to a guest ok = yes samba share needs to have a user name in 
the UNIX /etc/password file, if the security is set to server.  It seems as 
though guest ok = yes does not work.  In Samba 2** guest ok = yes worked 
properly in that the user did not need to supply a username or password to 
access the share.  In this case the key (guest account = valid UNIX account) 
does not help.
Comment 1 Gerald (Jerry) Carter (dead mail address) 2003-11-07 06:43:12 UTC
You didn't read the release notes did you :-)

Changes in Behavior

The following issues are known changes in behavior between Samba 2.2 and
Samba 3.0 that may affect certain installations of Samba.

  1)  When operating as a member of a Windows domain, Samba 2.2 would
      map any users authenticated by the remote DC to the 'guest account'
      if a uid could not be obtained via the getpwnam() call.  Samba 3.0
      rejects the connection as NT_STATUS_LOGON_FAILURE.  There is no
      current work around to re-establish the 2.2 behavior.


If you want to map every connection to guest, then add
a username map entry

     nobody = *

Comment 2 Gerald (Jerry) Carter (dead mail address) 2003-12-04 08:08:29 UTC
*** Bug 576 has been marked as a duplicate of this bug. ***
Comment 3 Gerald (Jerry) Carter (dead mail address) 2005-11-14 09:31:06 UTC
database cleanup