Linux

Ask something
Discussion Locked

Samba Permissions

0 helpful
4 replies

by jw-cats

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We are a small company who have a Linux (SUSE8.1) server running Samba for Files/sharing. Desktop clients are Win2K or XP Pro. The problem arises when one user creates a Directory: other users (in the group) cannot then save into that directory until I've been along and chmod-ed the permissions. Win2K doesn't seem to pass the permissions over to Samba. What haven't I done in configuring?

4 replies

by cpfeiffe

There are a few options on the Samba side that you may set in the global (affects all shares) or just in the particular share you are working on.

To fix the immediate issue you need

directory mask = 0775

You may also try setting

create mask = ????
force group = ?
map archive
map system
map hidden

create mask will work like similar to umask for new files created by assigning the attributes to the file. force group forces anyone that accesses the share to access it as the specified group. The map settings will map the respective DOS file attributes.

Hope this was helpful. Good luck.

by jw-cats

This resolved that problem perfectly (despite the above!) but I'm still left with a Win2K client receiving an Error message alluding to a failure to reconnect to this mapped drive, declaring the local device name being in use, and that the connection has not been restored. When the OK box (the only option!) is clicked, saving of the file is carried out successfully. Is this Micro$haft or Samba getting knickers in a twist?

by support

you could also use unix permissions to control user access. setting the group "sticky" bit on the real unix directory of your samba share will mean that everything under that directory will be created with the same group.

As for your maped drive problems....

disconnect all drives on the offending box. reboot win2k.
restart samba,
relogon to win2k, re-map drive. should be fine.

by escofalles

as far as your local device error in windows, change the drive letter that you are mapping. I always start with Z and work my way back just so I don't bother any actual devices.

This discussion is closed to new replies.