You can connect to a samba share without user or password authentication. That's how I have my server setup at my house. I dont know the settings off hand but illpost them shortly
-----Original Message----- From: Earl Ramirez Sent: 10/04/13 8:35 PM To: CentOS mailing list Subject: Re: [CentOS] Samba problem
On Fri, 2013-10-04 at 18:27 -0500, Joseph Hesse wrote:
On 10/04/2013 02:39 PM, John R Pierce wrote:
On 10/4/2013 12:11 PM, Joseph Hesse wrote:
security = user
you'll need to run
smbpasswd -a adminon the samba server, and give the 'admin' SMB user a password. Samba can't use the unix /etc/password|shadow combination as the hashes used by SMB aren't compatible.
I used "smbpasswd "to assign a Samba password to user "admin". My Win7 virtual machine still couldn't see the share. It is my impression that the smb.conf file in the book I am using allows passwordless access to the shares.
<snip> Are you able to authenticate to the samba server from the Windows 7 machine?
Also, if it helps, here is some more output.
[root@CentOS ~]# smbclient -L localhost -U Enter root's password: Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.6.9-151.el6_4.1]
Sharename Type Comment --------- ---- ------- homes Disk Home Directories IPC$ IPC IPC Service (CentOS)Domain=[WORKGROUP] OS=[Unix] Server=[Samba 3.6.9-151.el6_4.1]
Server Comment --------- ------- CENTOS CentOS WIN7VM Workgroup Master --------- ------- WORKGROUP WIN7VM
What is the out put from smbclient -L localhost -U admin?
I saw that you have the home directory enabled, by default SELinux does not permit access to the home directory, unless you enable the boolean
$ sudo setsebool -P samba_enable_home_dirs on
When you try to access the samba share from the windows 7 machine, what is happening? Are you being prompt for the credentials?
If you do not have a backup of the smb.conf file, I have placed a copy from a clean install [0]
[0] http://trinipino.com/share/smb.conf
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On Fri, Oct 4, 2013 at 8:44 PM, Chris Weisiger cweisiger@bellsouth.net wrote:
You can connect to a samba share without user or password authentication. That's how I have my server setup at my house. I dont know the settings off hand but illpost them shortly
You can set a share to publc or guest ok = yes. But then you won't see the home share of some other user.
You can set "security = share"
I had mine set to see the user share but I changed my setup
-----Original Message----- From: Les Mikesell Sent: Friday, October 04, 2013 8:54 PM To: CentOS mailing list Subject: Re: [CentOS] Samba problem
On Fri, Oct 4, 2013 at 8:44 PM, Chris Weisiger cweisiger@bellsouth.net wrote:
You can connect to a samba share without user or password authentication. That's how I have my server setup at my house. I dont know the settings off hand but illpost them shortly
You can set a share to publc or guest ok = yes. But then you won't see the home share of some other user.
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
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@centos.org Subject: Re: [CentOS] 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@centos.org http://lists.centos.org/mailman/listinfo/centos
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@bellsouth.netwrote:
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@centos.org Subject: Re: [CentOS] 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@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
On 10/05/2013 03:49 AM, Marios Zindilis wrote:
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:
- You need to also be logged in as "admin" in Windows 7 (worked for me
when I logged in as "admin" on Win7) or,
- 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@bellsouth.netwrote:
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@centos.org Subject: Re: [CentOS] 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@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
I thank you and everyone who replied to my Samba problem. What worked for me is to have a Windows user with the same name as the user on the CentOS computer and set a Samba password to be the same on both machines. What confused me is that many times I log on to a service on another computer and only have to know the name and password of the computer I am logging in to.
My real home network consists of my wife's Windows computer and multiple Linux desktops. I backup my computers using rsync. For the windows computer I looked at Cygwin which has the rsync program but decided instead to map a drive letter on her computer to a Samba share. She then could use the Windows backup program and backup to the Samba share. Afaik, the Windows backup program mirrors the selected files on the backup device. She has no need of restoring files prior to a certain date.
On 10/5/2013 7:31 AM, Joseph Hesse wrote:
My real home network consists of my wife's Windows computer and multiple Linux desktops. I backup my computers using rsync. For the windows computer I looked at Cygwin which has the rsync program but decided instead to map a drive letter on her computer to a Samba share. She then could use the Windows backup program and backup to the Samba share. Afaik, the Windows backup program mirrors the selected files on the backup device. She has no need of restoring files prior to a certain date.
*I* setup BackupPC at work for backing up a hetereogenous development server environment... this runs on a beefy linux box with a big disk farm, and 'pulls' the backups from the various target systems (a mix of Windows, Solaris, AIX, and Linux in my case). you can use a variety of different protocols for the backups, including rsync, nfs... for the several windows servers, I use a stripped down cygwin/rsync package, running in 'services' mode on the windows box, and pull the files via that. for my database servers, the backup runs a SQL script on the target that does a database dump, then it backs up that dump file rather than the raw datafiles.
BackupPC does incremental backups that are totally deduplicated by the use of hard links, and compresses the individual files. I'm backing up something like 15 servers and VMs, and have daily incrementals going back a couple weeks, weeklies going back a couple months, and monthlies going back to May when I started, and the WHOLE thing is only using like 1.5TB of disk space. wow. I planned for up to 32TB, using a whole lot of 3TB drives in raid60, with XFS.
BackupPC has a web interface so a user can browse their own backups and pull back a file or directory or what from any point in time.
On Sat, Oct 5, 2013 at 2:01 PM, John R Pierce pierce@hogranch.com wrote:
On 10/5/2013 7:31 AM, Joseph Hesse wrote:
My real home network consists of my wife's Windows computer and multiple Linux desktops. I backup my computers using rsync. For the windows computer I looked at Cygwin which has the rsync program but decided instead to map a drive letter on her computer to a Samba share. She then could use the Windows backup program and backup to the Samba share. Afaik, the Windows backup program mirrors the selected files on the backup device. She has no need of restoring files prior to a certain date.
*I* setup BackupPC at work for backing up a hetereogenous development server environment... this runs on a beefy linux box with a big disk farm, and 'pulls' the backups from the various target systems (a mix of Windows, Solaris, AIX, and Linux in my case). you can use a variety of different protocols for the backups, including rsync, nfs... for the several windows servers, I use a stripped down cygwin/rsync package, running in 'services' mode on the windows box, and pull the files via that. for my database servers, the backup runs a SQL script on the target that does a database dump, then it backs up that dump file rather than the raw datafiles.
BackupPC does incremental backups that are totally deduplicated by the use of hard links, and compresses the individual files. I'm backing up something like 15 servers and VMs, and have daily incrementals going back a couple weeks, weeklies going back a couple months, and monthlies going back to May when I started, and the WHOLE thing is only using like 1.5TB of disk space. wow. I planned for up to 32TB, using a whole lot of 3TB drives in raid60, with XFS.
BackupPC has a web interface so a user can browse their own backups and pull back a file or directory or what from any point in time.
Yes, I was going to recommend backuppc too. The de-dupe scheme lets you keep a fairly long history on line without using a lot of disk space. It can work directly with windows shares, but it is not that much trouble to set up rsync.
-
Chris Weisiger -
John R Pierce -
Joseph Hesse -
Les Mikesell -
Marios Zindilis