Description of problem: after installing samba 3.4.1 update, cannot connect to share from win xp-sp3 Version-Release number of selected component (if applicable): 3.4.1 How reproducible: consistent on one machine Steps to Reproduce: 1.install update 2.try to connect 3.get unable to connect in windows and errors in samba log Actual results: cannot connect to samba share Expected results: connect to samba share Additional info: update works with no issue on i586 machine. same win xp machine connects fine seems to be some sort of authentication issue from the windows machine don't see any errors in logs but can provide anything you request.
*** Bug 525823 has been marked as a duplicate of this bug. ***
Just tried Windows XP SP3 connecting to a Fedora 11 x86_64 box that runs 3.4.1 (connect to a share, create, delete files) and that is a member of a Samba controlled domain, so winbind is running on that Fedora box as well. All worked fine and I was not able to reproduce the problem you are seeing. Can you share more information what it requires to reproduce your problem ? (please set "log level = 10" and send the samba logfiles).
I'm not sure why my bug got merged into this one.. I never said anything about XP. I can't get a connection from anywhere, including localhost.
Created attachment 363012 [details] 192.168.1.4.log
Created attachment 363013 [details] 192.168.1.18.log
Created attachment 363015 [details] arturo.log
Created attachment 363016 [details] log.nmbd
Created attachment 363017 [details] log.smbd
Created attachment 363018 [details] log.wb-ARTURO
Created attachment 363019 [details] log.winbindd
Created attachment 363020 [details] log.winbindd-dc-connect
Created attachment 363021 [details] log.winbindd-idmap
Created attachment 363022 [details] smbd.log
Created attachment 363023 [details] swordfish.log
Created attachment 363025 [details] winbindd.log
Samba 3.4 changed the default passdb backend (as outlined in /usr/share/doc/samba-common-3.4.1/WHATSNEW.txt) to tdbsam and your logs indicate that you were using smbpasswd before. Please either set "passdb backend = smbpasswd" in the [global] section of your smb.conf or convert your accounts to tdbsam using "pdbedit -i smbpasswd -e tdbsam".
Adding "passdb backend = smbpasswd" fixed the problem for me. Should the RPM apply this change to smb.conf? Otherwise we break people's (working) config, without a visible configuration change.
(In reply to comment #17) > Adding "passdb backend = smbpasswd" fixed the problem for me. Should the RPM > apply this change to smb.conf? Otherwise we break people's (working) config, > without a visible configuration change. This resolved my issue as well. FWIW, the default smb.conf states: # Backend to store user information in. New installations should # use either tdbsam or ldapsam. smbpasswd is available for backwards # compatibility. tdbsam requires no further configuration.
I ran into this issue, when I was doing the following: 1. Fresh installed samba service on a fresh installed Fedora FC11 (So latest up to 1/7) 2. The combination worked beautifully till I initiated a huge directory transfer from my XP-SP3. 3. On realizing it will take 15 hours, I stopped the transfer and since then I ran into this problem. A. A reinstall of the same version of samba did not resolve the issue. B. But force deleting /var/lib/samba/private DID resolve issue. I am not sure if this is the solution, but it does have something to do with the passwords file. Blow it away and let it reinstall.
This message is a reminder that Fedora 11 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 11. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '11'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 11's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 11 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 11 changed to end-of-life (EOL) status on 2010-06-25. Fedora 11 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.