From Bugzilla Helper: User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) Description of problem: Samba sever done Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Click <GNOME menu> -> [System Settings] -> [Server Settings] -> [Samba] 2.At the Samba server configuration window, Click [Preferences] -> [Server Settings] 3.At the Server Settings window, Click the [Security]tab 4.In the [Security] tab, set follows Authentication Mode [User], Encript Passwords [Yes], Guest Account [No guest account] 5.After that, Add user 6.SMB Service On (in [System Setting] -> [Server Setting] -> [Services]) 6.trusted device eth0 On in Security level ([System Setting]-> [Security Level]) Actual Results: From Windws PC, samba server can be found, however, to access the samba server, the user name and password is required (dialog box opens) even though the registered user to samba. So input the user name and password, but the same dialog box comes up again and again. Expected Results: Users directory should be opened without user name and password requirement. Additional info: audit2allow -d comand shows several messages for samba
[This is a mass update sent to many bugs that missed earlier such messages due to having their version set to a test version.] This bug was originally filed against a version of Fedora Core which is no longer supported, even for security updates. Many changes have occured since then. Please retest this bug against a still supported version. Note that FC3 and FC4 are supported by Fedora Legacy for security fixes only. If it still occurs on FC5 or FC6, please assign to the correct version. Otherwise, if this a security issue, please change the product to Fedora Legacy. Thanks, and we are sorry that we did not get to this bug earlier. This bug will be closed after a few weeks if no information is given indicating that the bug is still present in a supported release.
Closing per lack of response to previous request for information. This bug was originally filed against a much earlier version of Fedora Core, and significant changes have taken place since the last version for which this bug is confirmed. Note that FC3 and FC4 are supported by Fedora Legacy for security fixes only. Please install a still supported version and retest. If it still occurs on FC5 or FC6, please reopen and assign to the correct version. Otherwise, if this a security issue, please change the product to Fedora Legacy. Thanks, and we are sorry that we did not get to this bug earlier.