Bug 5912 - Leopard can't connect when all shares set browsable = no
Summary: Leopard can't connect when all shares set browsable = no
Status: RESOLVED INVALID
Alias: None
Product: Samba 3.2
Classification: Unclassified
Component: File services (show other bugs)
Version: 3.2.1
Hardware: x86 Linux
: P3 minor
Target Milestone: ---
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-11-20 08:31 UTC by John Koelndorfer
Modified: 2009-05-13 04:40 UTC (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description John Koelndorfer 2008-11-20 08:31:33 UTC 
Forgive if my description is not very thorough, my coworker actually discovered this and I'm just reporting it through the grapevine since I figure it will help.

The issue is that Leopard would not connect (via "Connect to Server" in GUI) to Samba shares when none of the shares were browseable. In our smb.conf, we had set browseable = no in the global configuration, as well as browseable = no in every share's configuration. It was determined that setting a share to browseable = yes would allow Leopard to connect via GUI. In fact, setting ANY one share to browseable = yes would allow Leopard to connect via GUI to any share.

Around here, we don't make any shares browseable as it provides a little extra layer of security. To workaround this issue for now, we created a fake share with browseable = yes and everything works as expected.

Please let me know if there is any more useful information I can provide.
Comment 1 Volker Lendecke 2009-01-01 14:50:37 UTC 
How is this a Samba bug? I'd call this a Leopard issue.
Comment 2 Karolin Seeger 2009-05-13 04:40:15 UTC 
Closing out bug report.