I am having exactly the same problem with smbfs shares. I can write to NT
shares when running as root, but can only read them when running as a
I have the following line in my fstab file;
//server/share /mnt/nt_files smbfs noauto,uid=500,gid=504 0 0
Where uid = a test user account ID & GID is the ID of a group I have setup
to allow a number of users to mount the share.
When the user mounts the share they type;
sudo mount -o username=nt-domain-acc-name,workgroup=domain /mnt/nt_files
followed by their NT Password
This actually works OK when I log-in as the test user, however, this only
works for the user whose uid is specified in fstab, the Group gid does not
appear to have any effect. I have to change the 'uid' in fstab to the ID of
the user that need to mount this share.
Is this something to do with ACL's etc?
Your help would be much appreciated.
> root, but as soon as I switch to a user account (same username/password as
> my windows box), the ability to write goes away.
> Using umask in the mounted directory, I get 002 as user and 022 as root.
> > > I'm trying to connect my Linux box to my Windows box, and am almost
> > > there, but have hit a snag -- I can mount a share via smb on my Linux
> > > box, and as root can read and write files just fine. But when I switch
> > > to my user account, I can read files on the mount point fine, but
> > > write to it.
> > You can add options to change user and group of the mounted disk.
> > mount -t smbfs -o username=WINDOWS_USER,uid=LOCAL_USER,gid=LOCAL_GROUP
> > //WINDOWS_COMPUTER//SHARE /MOUNTPOINT
> > You have to mount as root.
> > Perhaps you can also use the umask option, I didn't try it.
> > See man mount for details.
> > Hope this helps
> > Simon