PC gets confused with rwx settings of ubuntu server?!
Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
PC gets confused with rwx settings of ubuntu server?!
Hi linux folks,
I have an ubuntu server with bunch of pcs (xp, vista, windows 7) connected to it. the server is just for file sharing and thats it. its been going fine for over a month now but recently one of the pc sees rights differently than what is setup in the server.
i have a folder that has read/write access for all. Only one pc has an issue where it sees it as read only. but when i restart the pc its working fine. but a day or so later it sees it as read only. i restart the pc and it works fine again.
i checked the server settings and they were always rwx. even when pc saw it as read only the server said the folder is rwx for all.
Does anyone know why the pc keeps doing it? this pc is pretty old. i believe its xp. does that have something to do with it? Also i've never setup any samba users or groups of anykind. does that pose any issue?
From your post it appears to be a workstation issue. It would be good if you could let us know the following:
1. How workstation access samba share?
2. Did you notice the same thing on any other workstation?
3. Did you setup any ACL on your samba share?
4. How user authenticate to samba share?
5. When the issue started. Is it something happened post Windows updates?
6. Do you have any other machine with the similar config that works fine.
Hi Terminator!! thanks a lot for your help yet again!
1) Workstations access the ubuntu server by me mapping the drive. I just opened network connections in pc and looked for "Server" and mapped it. that was it.
2) Yes I did notice it on two other workstations. One pc running windows 7 happened just once in 45 day period and another windows 7 happened twice in 45 day period and xp happened twice in two days so i put this post.
3) I don't know what ACL is . I just googled it and i really never did anything related to ACL. I wish i was good at Samba so i could properly configure my network with users and groups and give proper rights to folders and stuff. Im still struggling how to connect the pc username to samba username. like for eg. i created a samba username carl and there is a pc with username carl. but when i say that this particular folder has read only rights except for carl that has rwx. it doens work it becomes read only for everyone including carl. i did put write list on samba config file and all that after googling but nope. so im kinda struggling with that. just thought of letting you guys know where i stand
4) write now there is no user authentication. people freely "walk" into the folders, grab what they want and leave. everyone have rwx access to the shared folder.
5) This issue started about a week after i launched ubuntu server. happened twice to the windows 7 guy. after restarting his computer it was fine. then few weeks later to another windows 7 user and after rebooting the machine it was fine. then it happened to xp machine. rebooted the xp machine and it was fine. so im not sure whats going on.
6) hmmmm there is one other windows 7 that has not had any problems yet. and i checked the configuration of that and the windows 7 that had to be restarted they were identical.
---------- Post added 02-06-12 at 11:05 PM ----------
Hi devilboy,
Thanks for helping out! do i have to reinstall to samba to put swat? whats so beneficial about it?
Could you please post your smb.conf file. I would also like to know how many system connects to your Ubuntu machine. Are all of them connecting in the same way or there is a slight different between the way they connect?
It would be good if you post the acl config if any on your share. You can get the acl information using the following command:
Code:
getfacl /path/shared-folder
Example: If you have shared the folder /tmp/samba-share then you have will run above command as follows:
[global]
## Browsing/Identification ###
# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = workgroup
# server string is the equivalent of the NT Description field
server string = %h server (Samba, Ubuntu)
# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
# wins support = no
# WINS Server - Tells the NMBD components of Samba to be a WINS Client
# Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
; wins server = w.x.y.z
# This will prevent nmbd to search for NetBIOS names through DNS.
dns proxy = no
# What naming service and in what order should we use to resolve host names
# to IP addresses
; name resolve order = lmhosts host wins bcast
#### Networking ####
# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0
# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes
#### Debugging/Accounting ####
# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m
# Cap the size of the individual log files (in KiB).
max log size = 1000
# If you want Samba to only log through syslog then set the following
# parameter to 'yes'.
# syslog only = no
# We want Samba to log a minimum amount of information to syslog. Everything
# should go to /var/log/samba/log.{smbd,nmbd} instead. If you want to log
# through syslog you should set the following parameter to something higher.
syslog = 0
# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d
####### Authentication #######
# "security = user" is always a good idea. This will require a Unix account
# in this server for every user accessing the server. See
# /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/ServerType.html
# in the samba-doc package for details.
# security = share
# You may wish to use password encryption. See the section on
# 'encrypt passwords' in the smb.conf(5) manpage before enabling.
; encrypt passwords = yes
# If you are using encrypted passwords, Samba will need to know what
# password database type you are using.
; passdb backend = tdbsam
obey pam restrictions = yes
# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes
# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
pam password change = yes
# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user
########## Domains ###########
# Is this machine able to authenticate users. Both PDC and BDC
# must have this setting enabled. If you are the BDC you must
# change the 'domain master' setting to no
#
; domain logons = yes
#
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of the user's profile directory
# from the client point of view)
# The following required a [profiles] share to be setup on the
# samba server (see below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
# logon path = \\%N\%U\profile
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
# logon home = \\%N\%U
# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd
# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/adduser --quiet --disabled-password --gecos "" %u
# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u
# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup --force-badname %g
########## Printing ##########
# If you want to automatically load your printer list rather
# than setting them up individually then you'll need this
; load printers = yes
# lpr(ng) printing. You may wish to override the location of the
# printcap file
; printing = bsd
; printcap name = /etc/printcap
# CUPS printing. See also the cupsaddsmb(8) manpage in the
# cupsys-client package.
; printing = cups
; printcap name = cups
############ Misc ############
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name
# of the machine that is connecting
; include = /home/samba/etc/smb.conf.%m
# Most people will find that this option gives better performance.
# See smb.conf(5) and /usr/share/doc/samba-doc/htmldocs/Samba3-HOWTO/speed.html
# for details
# You may want to add the following on a Linux system:
# SO_RCVBUF=8192 SO_SNDBUF=8192
# socket options = TCP_NODELAY
# The following parameter is useful only if you have the linpopup package
# installed. The samba maintainer and the linpopup maintainer are
# working to ease installation and configuration of linpopup and samba.
; message command = /bin/sh -c '/usr/bin/linpopup "%f" "%m" %s; rm %s' &
# Domain Master specifies Samba to be the Domain Master Browser. If this
# machine will be configured as a BDC (a secondary logon server), you
# must set this to 'no'; otherwise, the default behavior is recommended.
# domain master = auto
# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap uid = 10000-20000
; idmap gid = 10000-20000
; template shell = /bin/bash
# The following was the default behaviour in sarge,
# but samba upstream reverted the default because it might induce
# performance issues in large organizations.
# See Debian bug #368251 for some of the consequences of *not*
# having this setting and smb.conf(5) for details.
; winbind enum groups = yes
; winbind enum users = yes
# Setup usershare options to enable non-root users to share folders
# with the net usershare command.
# Maximum number of usershare. 0 (default) means that usershare is disabled.
; usershare max shares = 100
# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes
security = share
; guest ok = yes
; guest account = nobody
#======================= Share Definitions =======================
# Un-comment the following (and tweak the other settings below to suit)
# to enable the default home directory shares. This will share each
# user's home director as \\server\username
;[homes]
; comment = Home Directories
; browseable = no
# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
; read only = yes
# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
; create mask = 0700
# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
; directory mask = 0700
# By default, \\server\username shares can be connected to by anyone
# with access to the samba server. Un-comment the following parameter
# to make sure that only "username" can connect to \\server\username
# The following parameter makes sure that only "username" can connect
#
# This might need tweaking when using external authentication schemes
; valid users = %S
# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes
# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700
[printers]
comment = All Printers
; browseable = yes
path = /var/spool/samba
printable = yes
guest ok = yes
; read only = yes
create mask = 0700
# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
; browseable = yes
; read only = yes
guest ok = yes
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
; write list = root, @lpadmin
# A sample share for sharing your CD-ROM with others.
;[cdrom]
; comment = Samba server's CD-ROM
; read only = yes
; locking = no
; path = /cdrom
; guest ok = yes
# The next two parameters show how to auto-mount a CD-ROM when the
# cdrom share is accesed. For this to work /etc/fstab must contain
# an entry like this:
#
# /dev/scd0 /cdrom iso9660 defaults,noauto,ro,user 0 0
#
# The CD-ROM gets unmounted automatically after the connection to the
#
# If you don't want to use auto-mounting/unmounting make sure the CD
# is mounted on /cdrom
#
; preexec = /bin/mount /cdrom
; postexec = /bin/umount /cdrom
[AutoCAD]
path = /media/P-drive/Projects/AutoCAD
; read only = yes
write list = NickF-PC
; browseable = yes
valid users = NickF-PC
; guest ok = no
[Projects]
path = /media/P-drive/Projects
writeable = yes
; browseable = yes
guest ok = yes
create mask = 0777
directory mask = 0777
[Smb test]
path = /media/P-drive/Projects/Smb test
writeable = yes
; browseable = yes
valid users = NickF-PC
I created a "smb test" folder to check if it works but no one has w access including "Nick".
There are 15 pc's connected to ubuntu machine. all have the ubuntu drive mapped to the machine. thats how they are connected.
Here's the ACL you asked for
Code:
kevin@Server:~$ sudo getfacl /media/P-drive/Projects
getfacl: Removing leading '/' from absolute path names
# file: media/P-drive/Projects
# owner: kevin
# group: kevin
user::rwx
group::rwx
other::rwx
Just a follow up on the smb test folder i created. i wanted only nick to have write access but it looks like no one including nick has write access. NickF-PC is his windows user name to login to pc and also this is the samba username created.
Alright. To start with does Nick got access to this smb test folder on the file system. In the config I can see the difference between the original folder and the test folder. Did you intentionall setup your test folder that way in smb.conf or you wanted it to be identical to original folder that.
As this happens with particular systems and the work after reboot it does not appear to be an issue with backend. Do you have samba running elsewhere in the network.
Could you share the logs from your samba server when this issue happens?
I wish i could answer your questions its just that I'm pretty much a beginner and dont know how to get logs from samba. didnt know it existed until you asked for one . Nick has access to the test folder but he does not have write access. I just created a test folder to see if it worked or not. I basically just installed samba and then mapped all pc's to the "Projects" folder. that was the easy way out. now as time pass by i needed to use "users" "groups" features to give read and write permission to only certain people for some folders within and i have no clue how.
samba is running only in ubuntu machine i think. all other computers are pc so the ubuntu machine is the only machine running samba. unless if samba can be run by pcs too? i dont know
i created nick username in ubuntu (without home folder or anything just username since no one should log into ubuntu machine except the admin)then i added this username to samba (thru gui samba) the username i put in samba and ubuntu is same as his pc. then i created the test folder if the write list = nick works. but seems like no one can write onto it. so it doesnt see nicks computer as his computer? dont know..
my setup is not proper i guess. could you tell me how to get samba log and i can then grab it and post it here. Thanks!
1) You're using security=share but want to deal with users. To gain knowledge about samba basics, take a look at "man smb.conf", the section about the different security models (and later, little by little, the rest of concepts in the man page). You might want to give security=user a try.
2) Together with the above, and to get rid of some extra messages, you want to get rid of usershare stuff, so try commenting out about usershares.
3) The shares seem to be from a mounted pendrive. There might be internal issues with this in the way the kernel might treat these devices, so I suggest to add another test share out of any external device.
4) Sum up your config with "testparm -L" instead of the smb.conf file.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.