This intrigued me enough, to fire up two VMs in VirtualBox, one Win7, one
CentOS, bridged network, and copied your Samba configuration, used it as
you pasted it in the original message.
There are some questionable options in your smb.conf. For example, there is
an "interfaces" option, which is meant to limit the network interfaces on
which Samba listens, but then there is "bind interfaces only = no" which
negates the former. Also there is "browsable = yes" in the [homes] share
definition, which I think makes one user's home directory visible to other
users, which is not usually what you want. That said, your configuration
should still work fine.
In my case, to get it to work, I had to do "smbpasswd -a admin" and give
admin a samba password, which made it possible for user admin to browse his
own share _on_the_localhost_ (on CentOS machine).
To be able to browse if from Windows, either:
1. You need to also be logged in as "admin" in Windows 7 (worked for me
when I logged in as "admin" on Win7) or,
2. You need to create a user mapping, but adding a line in the [Global]
section of /etc/samba/smb.conf reading "username map =
/etc/samba/username.map" and the edit "/etc/samba/usename.map" and add one
line in it with "SambaUsername = WindowsUsername". For example. the line
"admin = marios" inside /etc/samba/username.map worked for me while logged
in Win7 as "marios" (not as admin any more).
I hope the above are useful.
On Sat, Oct 5, 2013 at 7:54 AM, Chris Weisiger <cweisiger@xxxxxxxxxxxxx>wrote:
> when I set it to share I don’t need a password....its configure like an
> anonymous file server. but I can tune the settings in actual shared section
> of the conf file
>
> -----Original Message-----
> From: John R Pierce
> Sent: Friday, October 04, 2013 11:43 PM
> To: centos@xxxxxxxxxx
> Subject: Re: Samba problem
>
> On 10/4/2013 9:27 PM, Chris Weisiger wrote:
> > You can set "security = share"
> >
> > I had mine set to see the user share but I changed my setup
>
> are share passwords even supported anymore? that was the default mode
> for windows 3.x and 95-98 sharing, each share could have two passwords,
> one for read-only and one for write, and there was no concept of a user.
>
> what Ive always found works adequately is to create a smbpassword for
> each windows user, with the same password as they log onto their
> desktop. then windows will just autoconnect. if you have unix clients,
> use nfs, not smb!!
>
> what works *best* is to have active directory or another ldap+kerberos
> implementation, and have all your windows systems joined to the domain
> and users logging onto domain accounts. THEN you share to the domain
> accounts and its all good.
>
> windows 7 and newer default to requiring more strict encryption and
> authentication, which older systems may not provide by default.
>
>
> --
> john r pierce 37N 122W
> somewhere on the middle of the left coast
>
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>
--
Marios Zindilis
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
