I have an established server initially created with CentOS 6.5 and updated weekly. Last week there was a massive update that I believe upgraded my server to 6.6.
I had a number of issues after the upgrade---like my firewall being turned on and blocking all inbound ports. (I have an external firewall.) I've fixed all the issues created by this upgrade except for one.
I have a number of samba shares on this server used by some WinXP boxes on my network and two other linux (Fedora) workstations. Since the upgrade, guest/nobody write access no longer works. The smb.conf file is unchanged.
The config file below has been unchanged since my initial installation. Anyone know how I can restore guest write access? Guest can read, but not write to the share.
Mike W
#======================= Global Settings =====================================
[global] log file = /var/log/samba/log.%m lpq command = lpq -L restrict anonymous = no socket options = SO_KEEPALIVE TCP_NODELAY sync always = yes ntlm auth = no guest ok = yes client use spnego = no null passwords = yes hide dot files = no domain master = no username map = /etc/samba/user.map use spnego = no winbind trusted domains only = yes winbind use default domain = yes lprm command = lprm logon home = \%25N%25U cups options = raw print command = lpr -l -P%p %s read only = no server string = Orion Samba Server Version %v default service = global path = /var/spool/samba remote announce = 192.168.1.5/MAYNARD 192.168.1.10/MAYNARD 192.168.1.16/MAYNARD 192.168.1.20/MAYNARD 192.168.1.25/MAYNARD 192.168.1.30/MAYNARD 192.168.1.100/MAYNARD 192.168.1.101/MAYNARD 192.168.1.102/MAYNARD 192.168.1.103/MAYNARD 192.168.1.104/MAYNARD 192.168.1.105/MAYNARD 192.168.1.106/MAYNARD 192.168.1.107/MAYNARD 192.168.1.108/MAYNARD 192.168.1.109/MAYNARD
workgroup = maynard
logon path = \%25N%25U\profile
preload = global
security = share
max log size = 50
encrypt passwords = no
#============================ Share Definitions ==============================
[Home] comment = Home Directories delete readonly = yes path = /home strict sync = yes ; valid users = %S ; valid users = MYDOMAIN%S
[printers] comment = All Printers browseable = no printable = yes
[Var] comment = Var-Web-Ebooks delete readonly = yes inherit permissions = yes path = /var strict sync = yes
[mikew] comment = Home Directory delete readonly = yes inherit permissions = yes path = /home/Home
[Stuff] path = /home/stuff
[Root] path = /
Am 2014-11-06 19:05, schrieb Mike Watson:
I have an established server initially created with CentOS 6.5 and updated weekly. Last week there was a massive update that I believe upgraded my server to 6.6.
I had a number of issues after the upgrade---like my firewall being turned on and blocking all inbound ports. (I have an external firewall.) I've fixed all the issues created by this upgrade except for one.
I have a number of samba shares on this server used by some WinXP boxes on my network and two other linux (Fedora) workstations. Since the upgrade, guest/nobody write access no longer works. The smb.conf file is unchanged.
The config file below has been unchanged since my initial installation. Anyone know how I can restore guest write access? Guest can read, but not write to the share.
Mike W
Check for SELinux AVCs.
Alexander
--
"Lose not thy airspeed, lest the ground rises up and smites thee." -- William Kershner http://crucis-court.com http://www.crucis.net/1632search
On 11/06/2014 12:08 PM, Alexander Dalloz wrote:
Am 2014-11-06 19:05, schrieb Mike Watson:
I have an established server initially created with CentOS 6.5 and updated weekly. Last week there was a massive update that I believe upgraded my server to 6.6.
I had a number of issues after the upgrade---like my firewall being turned on and blocking all inbound ports. (I have an external firewall.) I've fixed all the issues created by this upgrade except for one.
I have a number of samba shares on this server used by some WinXP boxes on my network and two other linux (Fedora) workstations. Since the upgrade, guest/nobody write access no longer works. The smb.conf file is unchanged.
The config file below has been unchanged since my initial installation. Anyone know how I can restore guest write access? Guest can read, but not write to the share.
Mike W
Check for SELinux AVCs.
Alexander
SELinux is/has been disabled.
mw
On 11/6/2014 1:05 PM, Mike Watson wrote:
I have an established server initially created with CentOS 6.5 and updated weekly. Last week there was a massive update that I believe upgraded my server to 6.6.
I had a number of issues after the upgrade---like my firewall being turned on and blocking all inbound ports. (I have an external firewall.) I've fixed all the issues created by this upgrade except for one.
I have a number of samba shares on this server used by some WinXP boxes on my network and two other linux (Fedora) workstations. Since the upgrade, guest/nobody write access no longer works. The smb.conf file is unchanged.
The config file below has been unchanged since my initial installation. Anyone know how I can restore guest write access? Guest can read, but not write to the share.
I don't see anything obvious. The first thing I would do is to take a look at 'smbstatus' while a guest user is logged on and make sure it is connecting as the user you expect.
On 11/06/2014 01:47 PM, Bowie Bailey wrote:
On 11/6/2014 1:05 PM, Mike Watson wrote:
I have an established server initially created with CentOS 6.5 and updated weekly. Last week there was a massive update that I believe upgraded my server to 6.6.
I had a number of issues after the upgrade---like my firewall being turned on and blocking all inbound ports. (I have an external firewall.) I've fixed all the issues created by this upgrade except for one.
I have a number of samba shares on this server used by some WinXP boxes on my network and two other linux (Fedora) workstations. Since the upgrade, guest/nobody write access no longer works. The smb.conf file is unchanged.
The config file below has been unchanged since my initial installation. Anyone know how I can restore guest write access? Guest can read, but not write to the share.
I don't see anything obvious. The first thing I would do is to take a look at 'smbstatus' while a guest user is logged on and make sure it is connecting as the user you expect.
It is.
Samba version 3.6.23-12.el6 PID Username Group Machine ------------------------------------------------------------------- <processes do not show up in anonymous mode>
Service pid machine Connected at ------------------------------------------------------- Stuff 16177 remington Thu Nov 6 15:21:12 2014 Var 16177 remington Thu Nov 6 15:21:56 2014
Locked files: Pid Uid DenyMode Access R/W Oplock SharePath Name Time -------------------------------------------------------------------------------------------------- 16177 99 DENY_NONE 0x100081 RDONLY NONE /home/stuff . Thu Nov 6 15:21:25 2014
mw