Since I haven't had a response to my earlier post, I'm reposting this
with
some more info.
I'm running Samba version 2.07 on Redhat Linux 7.0.
Here is my smb.conf file:
# Samba config file created using SWAT
# from greyowl.swamp.ca (192.168.0.5)
# Date: 2002/06/26 00:29:59
# Global parameters
[global]
workgroup = SWAMP
netbios name = BALDEAGLE
server string = Samba Server %h
interfaces = 192.168.0.2/24 127.0.0.1/24
security = SHARE
encrypt passwords = Yes
update encrypted = Yes
null passwords = Yes
unix password sync = Yes
log file = /var/log/samba/%m.log
max log size = 50
time server = Yes
os level = 65
preferred master = Yes
dns proxy = No
wins support = Yes
guest account = smbuser
[homes]
comment = Home Directories
path = /home/%u
writeable = Yes
browseable = No
[public]
comment = Public Files
path = /public
writeable = Yes
create mask = 0664
guest ok = Yes
When the public folder was created (a couple of years ago), the SGID bit was
set so that all files would be owned by the smb group:
chmod 2777 /public
The /public folder has the following attributes:
drwxrwsrwx 13 smbuser smb 1024 May 14 18:29 public
The /public folder contains a number of subfolders:
drwxrwsr-x 6 smbuser smb 1024 May 25 00:50 Aviation
drwxrwsr-x 10 smbuser smb 1024 Jun 27 21:57 Documents
lrwxrwxrwx 1 root root 12 Nov 8 2000 Linuxdocs ->
/usr/doc/LDP
drwxrwsr-x 2 smbuser smb 1024 Jul 7 2001 RETScreen
drwxrwsr-x 4 smbuser smb 1024 Feb 9 16:43 Sandra
drwxrwsr-x 3 smbuser smb 1024 Jun 23 16:24 Software
drwxrwsr-x 10 smbuser smb 1024 Jun 26 21:08 archives
drwxr-xr-x 2 root root 12288 Nov 5 2000 lost+found
drwxrwsr-x 10 smbuser smb 1024 Aug 11 2001 msaccess
drwxrwsr-x 16 smbuser smb 1024 Sep 23 2000 msapps
drwxrwsr-x 15 smbuser smb 1024 Mar 27 2000 msoffice
drwxrwsr-x 2 smbuser smb 1024 Sep 30 2001 setup
The folder Computers is in /public/Documents:
drwxrwsr-x 13 smbuser smb 3072 Jun 30 09:36 Computers
-rw-rw-r-- 1 Janyce smb 16896 Jun 30 10:48 cables2.xls
-rw-rw-r-- 1 smbuser smb 18944 Jul 26 2001 cables1.xls
-rw-rw-r-- 1 smbuser smb 110 Feb 18 2001 case.b2d
drwxrwxr-x 2 smbuser smb 1024 Jun 30 10:57 m506
-rw-rw-r-- 1 smbuser smb 216 Mar 20 1997 bullet2.gif
-rw-rw-r-- 1 Janyce users 16896 Jun 30 09:53 cables2.xls
-rw-rw-r-- 1 Janyce users 16896 Jun 30 10:57 cables2b.xls
-rw-rw-r-- 1 smbuser smb 16896 Jun 30 10:40 cables3.xls
-rw-rw-r-- 1 smbuser smb 16896 Jun 30 10:47 cables4.xls
-rw-rw-r-- 1 smbuser smb 35 Mar 20 1997 dot_black.gif
-rw-rw-r-- 1 smbuser smb 43 Mar 20 1997 dot_clear.gif
Of particular interest are the cables*.xls files. They are the same file,
written by different users on different computers. cables2 and cables2b were
written by Janyce on the Win2k computer. cables3 was written by user Karl on a
Win98 box, and cables4 was written by Janyce on a WinME laptop. So, although
the Win2k computer can write files in this folder, the file permissions are
messed up. This keeps users on the other computers from writing to the same
file - they must give it a new name. But this isn't what is intended - all
of
the files in /public are supposed to be owned by everyone....
I'm sure there's' a simple fix. But I'm a bit of a newbie on
Win2K. Can someone
please help me out?
Janyce
---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.372 / Virus Database: 207 - Release Date: 02/06/20
I'll keep that under consideration (I'm a bit rusty at rpm's). But given the way the file ownership seems to be working, I think it's more of a Win2k configuration issue. I think I need to tell my Win2K machine (blackhawk) that Janyce is a member of the smb group on the samba server baldeagle. (And I don't know how to do that.) On June 30, 2002 6:46 PM, Neil Muller [SMTP:neil@neologix.net] wrote:> Hi Janyce, > > What about upgrading your samba to one of the 2.2.x series? If you're using > RedHat you can get rpms for 2.2.3a; the latest samba release is 2.2.5. > > Neil--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.372 / Virus Database: 207 - Release Date: 02/06/20
I'll keep that under consideration (I'm a bit rusty at rpm's). But given the way the file ownership seems to be working, I think it's more of a Win2k configuration issue. I think I need to tell my Win2K machine (blackhawk) that Janyce is a member of the smb group on the samba server baldeagle. (And I don't know how to do that.) On June 30, 2002 6:46 PM, Neil Muller [SMTP:neil@neologix.net] wrote:> Hi Janyce, > > What about upgrading your samba to one of the 2.2.x series? If you're using > RedHat you can get rpms for 2.2.3a; the latest samba release is 2.2.5. > > Neil--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.372 / Virus Database: 207 - Release Date: 02/06/20
I'll keep that under consideration (I'm a bit rusty at rpm's). But given the way the file ownership seems to be working, I think it's more of a Win2k configuration issue. I think I need to tell my Win2K machine (blackhawk) that Janyce is a member of the smb group on the samba server baldeagle. (And I don't know how to do that.) On June 30, 2002 6:46 PM, Neil Muller [SMTP:neil@neologix.net] wrote:> Hi Janyce, > > What about upgrading your samba to one of the 2.2.x series? If you're using > RedHat you can get rpms for 2.2.3a; the latest samba release is 2.2.5. > > Neil--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.372 / Virus Database: 207 - Release Date: 02/06/20
That's not the problem. The same usernames & passwords have been created everywhere. SEEING the shares isn't the problem. The problem is that files written to the public share should be written as the user smbuser:smb, just like on the Win98 and WinME computers (and not as user Janyce). Janyce On July 2, 2002 2:56 AM, Neil Muller [SMTP:neil@neologix.net] wrote:> On Sun, 2002-06-30 at 15:16, Janyce Wynter wrote: > > I'll keep that under consideration (I'm a bit rusty at rpm's). But giventhe> > > > way the file ownership seems to be working, I think it's more of a Win2k > > configuration issue. I think I need to tell my Win2K machine (blackhawk) > > that > > Janyce is a member of the smb group on the samba server baldeagle. (And I > > don't > > know how to do that.) > You need to add your user to the smbpasswd file > > eg. smbpasswd -a <username> > > If the username and password are the same as the user on your w2k > machine and both machines are in the same workgroup and you have > encrypted passwords enabled in smb.conf then you should be able to see > your samba shares from w2k. See > http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection.html (or pdf > if you prefer). > > Neil > > > > --- > Incoming mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.372 / Virus Database: 207 - Release Date: 02/06/20--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.372 / Virus Database: 207 - Release Date: 02/06/20
Have you looked at force user and force group ??
I tried this, and I was unable to set the variable for the names and groups. I used %U and %G. Im pretty sure those are them. When I set to force user or groupe using those variables, it didnt work for me... Should it? Maybe I was doing something wrong... Thanks Joe Giles> Have you looked at setting options like "force user" and "force group"? There > are similar options for "create mode", "directory security mask", "create mask". > > Neil > > > Quoting Janyce Wynter <janycewynter@cnwl.igs.net>: > > > That's not the problem. > > > > The same usernames & passwords have been created everywhere. SEEING the > > shares > > isn't the problem. The problem is that files written to the public share > > should > > be written as the user smbuser:smb, just like on the Win98 and WinME > > computers > > (and not as user Janyce). > > > > Janyce > > > > On July 2, 2002 2:56 AM, Neil Muller [SMTP:neil@neologix.net] wrote: > > > On Sun, 2002-06-30 at 15:16, Janyce Wynter wrote: > > > > I'll keep that under consideration (I'm a bit rusty at rpm's). But > > given > > the > > > > > > > > way the file ownership seems to be working, I think it's more of a > > Win2k > > > > configuration issue. I think I need to tell my Win2K machine > > (blackhawk) > > > > that > > > > Janyce is a member of the smb group on the samba server baldeagle. > > (And I > > > > don't > > > > know how to do that.) > > > You need to add your user to the smbpasswd file > > > > > > eg. smbpasswd -a <username> > > > > > > If the username and password are the same as the user on your w2k > > > machine and both machines are in the same workgroup and you have > > > encrypted passwords enabled in smb.conf then you should be able to > > see > > > your samba shares from w2k. See > > > http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection.html (or > > pdf > > > if you prefer). > > > > > > Neil > > > > > > > > > > > > --- > > > Incoming mail is certified Virus Free. > > > Checked by AVG anti-virus system (http://www.grisoft.com). > > > Version: 6.0.372 / Virus Database: 207 - Release Date: 02/06/20 > > > > > > --- > > Outgoing mail is certified Virus Free. > > Checked by AVG anti-virus system (http://www.grisoft.com). > > Version: 6.0.372 / Virus Database: 207 - Release Date: 02/06/20 > > > > > > > > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: http://lists.samba.org/mailman/listinfo/samba >Joe Giles jgiles@joeman1.com AOL ID: mcigiles
Yes, after much grief (Samba died and refused to work - I needed to wipe out smb.conf and smbpasswd and pretty much start over....) it seems to be working now. Thanks to everyone who helped. Janyce On July 1, 2002 5:36 PM, Neil Muller [SMTP:neil@neologix.net] wrote:> Have you looked at setting options like "force user" and "force group"? There > are similar options for "create mode", "directory security mask", "create > mask". >--- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.372 / Virus Database: 207 - Release Date: 02/06/20