Bug 88114 - authentication issues with smb://
authentication issues with smb://
Status: CLOSED DUPLICATE of bug 78864
Product: Red Hat Linux
Classification: Retired
Component: gnome-vfs2-extras (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Alexander Larsson
Jay Turner
Depends On:
  Show dependency treegraph
Reported: 2003-04-05 20:01 EST by Edward Muller
Modified: 2015-01-07 19:04 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 13:52:30 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Edward Muller 2003-04-05 20:01:31 EST
Description of problem:

Nautilus is constantly asking for a username/password when working with
samba/smb shares. I am trying to browse a share on another Redhat 9.0 machine.

This happens wether I specify smb://username:password@host/share or just

Copying files this way also prompts for a password for each file.

This basically makes smb:// useless for working with smb/samba shares.

Version-Release number of selected component (if applicable):

How reproducible:

Every time.

Steps to Reproduce:
1. Open up nautilus.
2. enter smb://username:password@host/share (replacing them with real info) in
the Location: box.
3. Attempt to work with the files (copy them move them, etc)

Actual results:

Username/Password box repetedly opens up. Over and over again.

Expected results:

enter username/password once (or specify it on the Location: line)

Additional info:
Comment 1 Edward Muller 2003-04-05 20:08:28 EST
This may be the same bug as in:


Comment 2 Leonard den Ottolander 2004-03-09 10:59:22 EST
This is a duplicate of bug 78864. It is however still an issue with FC
1, gnome-vfs2-extras-0.99.10-3.1.


*** This bug has been marked as a duplicate of 78864 ***
Comment 3 Red Hat Bugzilla 2006-02-21 13:52:30 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.