Bug#533417: nautilus: can't connect to CIFS server if there are no read perms on root-folder

Jon Dowland jon+bts at alcopop.org
Wed Jun 17 11:02:39 UTC 2009


On Wed, Jun 17, 2009 at 12:25:13PM +0200, Josselin Mouette
wrote:
> Can you try with 1.2 ? There have been important fixes in
> the SMB backend.

Certainly. Thanks for your prompt response.

With 1.2, using the nautilus dialogue, I get the same
looping password request when defining server, share and
folder; but the dialogue has changed text to

    Cannot display location "smb://njd33@turret1/iss/unix
    Password dialogue cancelled

I can also produce the same behaviour using gvfs-mount from
the gvfs-bin package:

    $ gvfs-mount 'smb://CAMPUS;njd33@turret1/iss/unix'
    Password required for share iss on turret1
    Password: 
    Password required for share iss on turret1
    Password: 

The "alternative" DFS paths I mentioned in the bug
(//campus/...) do not work with gvfs-mount:

    $ gvfs-mount 'smb://CAMPUS;njd33@campus/dept/iss/unix'
    Password required for share dept on campus
    Password: 
    Error mounting location: Failed to mount Windows share

(same result ommitting /unix, or ommitting /iss/unix)

I have a separate SMB mount from a different Windows file
server which works: 

    $ gvfs-mount -l
    ...
    Mount(0): home13 on tower3 -> smb://CAMPUS;njd33@tower3/home13/
      Type: GDaemonMount

I can mount and unmount the pathname there with gvfs-mount
fine, and connect to it via the nautilus dialog fine.

I have read permissions in home13 which is what
distinguishes this from the paths that are causing me
problems. However, this working path has a DFS equivalent
which I can't get to work with gvfs:

    $ gvfs-mount 'smb://CAMPUS;njd33@campus/home/home13'
    Password required for share home13 on campus
    Password: 
    Error mounting location: Failed to mount Windows share

smbclient -U njd33 //campus/home/home13 works.

This leads me to believe that the paths I've attempted with
'campus' as the hostname are failing for different reasons
than the permissions-related behaviour with the ones with
the hostname 'turret1'.

Quick summary for clarity's sake:

 * 'smbclient -U njd33 //turret1/iss' works, I cannot read
   the contents of iss, but I can 'cd unix'. This is
   expected.
 * 'smbclient -U njd33 //turret1/iss -D unix' works
 * gvfs-mount 'smb://CAMPUS;njd33@turret1/iss/unix' fails,
   repeatedly requesting Password:
 * the same path via the nautilus dialogue fails, repeatedly
   requesting a password, and then responding with 
   "Password dialogue cancelled" when you cancel the
   dialogue
 * same behaviour for nautilus and gvfs-mount omitting /unix
   or not filling in "folder" field


-- 
Jon Dowland
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: Digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-gnome-maintainers/attachments/20090617/6c791828/attachment.pgp>


More information about the pkg-gnome-maintainers mailing list