[SOLVED] Samba can't see shares with names over ?8? or so characters long
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Samba can't see shares with names over ?8? or so characters long
I'm wondering if anyone found a way to see shares with a name such as: "my-shares-on-such-and-such-computer" This worked in 12.1/12.2 but the shares don't show with the samba version in --current (13.0+). Of note, smbclient does not list the shares either. Any thoughts appreciated.
Looks like a but in Samba 3.4.2. I can reproduce it but have not checked if the latest release (3.4.3) has fixed this. I can see a reference to this bug in the debian/ubuntu bugtracker but since launchpad seems to be offline I can not get to the actual patch file for 3.4.2 (fix-smbclient-long-names.patch)
Thanks for the reply. I extracted the diff out of their office *.dsc file. Going to try and give it whirl. If I can't get it to work, well I'll just wait for the next version of Samba to hit --current then.
I'm going to mark this as solved since upstream at Samba they appear to have fixed this, and presumably Mr. V will add it to --current which I'm running.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.