After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 103748 - Cannot connect to shared directory if its name length is over 13 symbols
Cannot connect to shared directory if its name length is over 13 symbols
Product: gnome-vfs-extras
Classification: Deprecated
Component: smb
Other Linux
: Normal normal
: ---
Assigned To: GNOME VFS Extras Maintainers
GNOME VFS Extras Maintainers
: 152099 (view as bug list)
Depends on:
Reported: 2003-01-17 14:52 UTC by Vaidotas Zemlys
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---

Description Vaidotas Zemlys 2003-01-17 14:52:38 UTC
If on remote Samba server there is shared folder which has sharename longer
than 13 symbols it is not browseable. 

For example if on remote Samba server Samba there is a shared folder with
sharename name_which_is_way_longer_than_13_symbols, and I would go with
nautilus to
then the same folder will be displayed as name_which_is and nautilus will
show that it has ? items. If you double click on that folder, then nautilus
will display error message:

Nautilus cannot display "smb://Samba/name_which_is"

It is interesting that this restriction applies only to folders which are
shared on Samba server. If for example there is a folder shared with name
short_name and it has a subfolder another_name_which_is_too_long going to


everything is displayed properly, and subfolder
another_name_which_is_too_long is browseable.

Using smbclient I can connect to folders with long names:

smbclient //Samba/name_which_is_way_longer_than_13_symbols

works perfectly. 

I suspect it is somehow related to smbclient, because

smbclient -L //Samba

displays first 13 symbols of shared folder names.

Since I noticed this bug I have upgraded Gnome2 from Sid few times, but the
bug is still there.
Comment 1 Bastien Nocera 2003-07-22 19:26:56 UTC
Bug still exists with the libsmbclient backend.
Filed upstream:
Comment 2 Bastien Nocera 2004-09-07 20:53:14 UTC
*** Bug 152099 has been marked as a duplicate of this bug. ***