| Summary: | Unable to connect to windows share via GUI, but smbclient works fine | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Thomas L. Shinnick <tshinnic> | ||||
| Component: | nautilus | Assignee: | Tomáš Bžatek <tbzatek> | ||||
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 16 | CC: | brian.dudek, ccecchi, extras-orphan, notting, tbzatek, tsmetana | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | i386 | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-02-13 22:37:38 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Attachments: |
|
||||||
Try using domain/user in Nautilus as I pointed out in Bug 756316. Does this help? (sigh) At the moment I am unable to reproduce this, except sporadically. Something has changed apparently, but I'm pretty sure it isn't the parameters I am supplying the dialog. I have tried varying the parameters, such as alternate letter-casing. It seems the initial "Connect to server..." is now succeeding, always? However, if I should now "unmount" that initially successfully connection, often I can't then connect again, using the very same parameters that succeed the first time. I don't know what to think. I don't think nautilus has changed. I know Samba has been updated (on 3.6.1-75 currently) Created attachment 546266 [details]
Working Nautilus w/ 'domain/user' specified
I will agree with "sporadically" in the sense that once the Nautilus "Connect to Server" dialog box as bad credentials entered it will never accept good credentials. I will need to be closed then opended again. But I think this is another issue entirely. I will check for a bug on it an file one if need be. I have attached an image of my working Nautilus connection dialog. Another thing to check if you have enver checked the box "Remember this Password": Applications --> Accessories --> Passwords and Encryption Keys Once a good connection string has been saved Nautilus will accept ANY password correct or not, even no password. (In reply to comment #5) > Once a good connection string has been saved Nautilus will accept ANY password > correct or not, even no password. That looks like a bug - can you please open a separate bugreport providing further details? Would be interesting to see what is actually stored in the keyring - seahorse would help here. Bug 767419 was created for Nautilus ignoring bad/no password for that of the Sea Horse entry. This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. 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 '16'. 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 16'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 16 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, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. 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 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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. |
Description of problem: Starting from "Places" then "Connect to Server..." then set type "Windows share", I then fill in all the correct parameters, on "Continue" get error message "Please verify your user details". Always. I am able to access the same share using smbclient just fine: smbclient //tlsw7a/c -W tlswg -U Tom I have also tried turning off the firewall and turning off SELinux (temp permissive mode) and retested with no joy. Version-Release number of selected component (if applicable): Quite new install of Fedora 16 How reproducible: Unfortunately always with this install. Steps to Reproduce: 1. As above 2. 3. Actual results: Expected results: Additional info: As this is hosted under VMware under Windows, and as I have F15 running alongside, I just tested F15 with same parameters and "Connect to Server" works under F15. As this is hosted under VMware, the user session dropped back to gnome2 (or whatever) because gnome3 said the display (via VMware) wasn't good enough. I'm willing to install another copy and/or retest with any suggestions.