GNOME Bugzilla – Bug 147036
Navigation of SMB Shares
Last modified: 2005-02-12 08:21:14 UTC
Distribution: Debian testing/unstable Package: nautilus Severity: normal Version: GNOME2.6.1 unspecified Gnome-Distributor: Debian Synopsis: Navigation of SMB Shares Bugzilla-Product: nautilus Bugzilla-Component: Navigation Bugzilla-Version: unspecified Description: Description of Problem: When you attempt to connect to a SMB server through the network view, unless you explicitly type a share a username and password is not requested, and so I get a permission is denied error. This is not the case, however, if I explicitly try to connect to a share (such as C$) Steps to reproduce the problem: 1. Double click on "Computer" on the desktop. 2. Double click on "Network" in the resultant window. 3. Double click on any windows computer that you wish to connect to. Actual Results: Permission denied error is displayed without giving a chance to authenticate, and nothing is displayed in the new window. Expected Results: A list of valid shares should be displayed so that you can connect to them. How often does this happen? Always ------- Bug moved to this database by unknown@bugzilla.gnome.org 2004-07-09 10:51 ------- Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "nautilus". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was samfoo@gmail.com. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
There was a thread about this bug on nautilus-list a while ago: http://mail.gnome.org/archives/nautilus-list/2004-June/msg00025.html (Although I don't think the bug 129890 listed in this mail is not a duplicate of this bug, even though it contains some related discussion)
This is a bug in the gnome-vfs smb auth code. It should be fixed in 2.10. *** This bug has been marked as a duplicate of 132933 ***