The Samba-Bugzilla – Bug 5032
Can't name a share "Public"
Last modified: 2007-10-31 23:52:45 UTC
If I name any share "Public", no matter what the other settings are, Windows clients cannot access it. They report "\\hostname\Public refers to a location that is unavailable. It could be on a hard drive......."
Here's my config:
workgroup = MSHOME
server string = %h server (Samba, Ubuntu)
dns proxy = no
log file = /var/log/samba/log.%m
max log size = 1000
syslog = 0
panic action = /usr/share/samba/panic-action %d
security = share
encrypt passwords = true
passdb backend = tdbsam
obey pam restrictions = yes
guest account = nobody
; invalid users = root
unix password sync = yes
# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<email@example.com> for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\sUNIX\spassword:* %n\n *Retype\snew\sUNIX\spassword:* %n\n *passwd:*password\supdated\ssuccessfully* .
socket options = TCP_NODELAY
path = /mnt/big/stuff
browseable = yes
read only = yes
guest ok = yes
Every server I run has a share named public. We'll need complete level
10 log files to do anything with this report.
Yeah, it was apparently some sort of caching issue on my Windows clients. If anyone else has this problem, try rebooting, or running "net use /delete *" to clear out all your network share info.