A customer has an expanding number of Mac computers. Last Friday and existing machine started having problems writing files to a Samba share on a CentOS 5.x server. They had no problems prior to Friday. They are getting permission failure errors in creating files and folders. I made the sare owned by the user and group with group write enabled. Even with him as the owner he can not write to the share. I stopped / started Samba, same problem. I had him reconnect, same problem. Even had him reboot his Mac but problem persists. I ran Wireshark traces but the session generates 30 to 40 thousand packets and I am unable to find the packets that might pinpoint why he now has problems writing to the server. I just ran a yum update of the CentOS server and it downloaded samba-common-3.0.33-3.15. I don't know if this release fixes my problem. Has anyone else had problems with OS/X writing to a Samba share AFTER it's been working for for a while (in my case 2 months)?
On Tue, Apr 20, 2010 at 12:22 PM, jjrowan <samba at rownetco.com> wrote:> A customer has an expanding number of Mac computers. Last Friday and > existing machine started having problems writing files to a Samba share on a > CentOS 5.x server. They had no problems prior to Friday. They are getting > permission failure errors in creating files and folders. I made the sare > owned by the user and group with group write enabled. Even with him as the > owner he can not write to the share. I stopped / started Samba, same > problem. I had him reconnect, same problem. Even had him reboot his Mac > but problem persists. I ran Wireshark traces but the session generates 30 > to 40 thousand packets and I am unable to find the packets that might > pinpoint why he now has problems writing to the server. I just ran a yum > update of the CentOS server and it downloaded samba-common-3.0.33-3.15. I > don't know if this release fixes my problem. Has anyone else had problems > with OS/X writing to a Samba share AFTER it's been working for for a while > (in my case 2 months)? > > For us, the fix was to add "unix extensions = no" in the global section.Robert LeBlanc Life Sciences & Undergraduate Education Computer Support Brigham Young University
On Tue, Apr 20, 2010 at 02:22:17PM -0400, jjrowan wrote:> A customer has an expanding number of Mac computers. Last Friday and > existing machine started having problems writing files to a Samba share > on a CentOS 5.x server. They had no problems prior to Friday. They are > getting permission failure errors in creating files and folders. I made > the sare owned by the user and group with group write enabled. Even > with him as the owner he can not write to the share. I stopped / > started Samba, same problem. I had him reconnect, same problem. Even > had him reboot his Mac but problem persists. I ran Wireshark traces but > the session generates 30 to 40 thousand packets and I am unable to find > the packets that might pinpoint why he now has problems writing to the > server. I just ran a yum update of the CentOS server and it downloaded > samba-common-3.0.33-3.15. I don't know if this release fixes my > problem. Has anyone else had problems with OS/X writing to a Samba > share AFTER it's been working for for a while (in my case 2 months)?What changed last Friday ? Find that out and you'll find the problem. Jeremy.
jjrowan wrote:> A customer has an expanding number of Mac computers. Last Friday and > existing machine started having problems writing files to a Samba > share on a CentOS 5.x server. They had no problems prior to Friday. > They are getting permission failure errors in creating files and > folders. I made the sare owned by the user and group with group write > enabled. Even with him as the owner he can not write to the share. I > stopped / started Samba, same problem. I had him reconnect, same > problem. Even had him reboot his Mac but problem persists. I ran > Wireshark traces but the session generates 30 to 40 thousand packets > and I am unable to find the packets that might pinpoint why he now has > problems writing to the server. I just ran a yum update of the > CentOS server and it downloaded samba-common-3.0.33-3.15. I don't > know if this release fixes my problem. Has anyone else had problems > with OS/X writing to a Samba share AFTER it's been working for for a > while (in my case 2 months)? >With respect to Mr. Allison, figuring out what changed isn't always simple. Sometimes it can be something that is only peripherally connected to Samba, such as a DNS server upgrade. In general, the Unix permissions need to be permissive enough to allow Samba to control the access. You may also want to check that the users are actually logging on. Try checking the Samba logs to see if there is a problem being reported. If that doesn't work, set the Samba loglevel to 10, restart Samba and try again.
On Wed, Apr 21, 2010 at 6:22 AM, jjrowan <samba at rownetco.com> wrote:> A customer has an expanding number of Mac computers. Last Friday and > existing machine started having problems writing files to a Samba share on a > CentOS 5.x server. They had no problems prior to Friday. > >This issue is caused by the recent OSX 10.6.3 update not supporting wide links (see the Samba wide links security problem: secunia.com/advisories/38454/). See here for a discussion: splatdot.com/fixing-snow-leopard-10-6-3-samba-write-access <http://splatdot.com/fixing-snow-leopard-10-6-3-samba-write-access> If you are running the latest versions of Samba you will not experience this problem because wide links are disabled by default. If you are not running a current version, you do not need to disable unix extensions entirely, simply disable wide links in your Samba's smb.conf file: wide links = no getwd cache = yes * Enabling the getwd cache is recommended here: oreilly.com/catalog/samba/chapter/book/appb_02.html But whether it is relevant in this day and age I don't know. David
On Tue, Apr 20, 2010 at 2:22 PM, jjrowan <samba at rownetco.com> wrote:> A customer has an expanding number of Mac computers. ?Last Friday and > existing machine started having problems writing files to a Samba share on a > CentOS 5.x server. ?They had no problems prior to Friday. ?They are getting > permission failure errors in creating files and folders. ?I made the sare > owned by the user and group with group write enabled. ?Even with him as the > owner he can not write to the share. ?I stopped / started Samba, same > problem. ?I had him reconnect, same problem. ?Even had him reboot his Mac > but problem persists. ?I ran Wireshark traces but the session generates 30 > to 40 thousand packets and I am unable to find the packets that might > pinpoint why he now has problems writing to the server. ? I just ran a yum > update of the CentOS server and it downloaded samba-common-3.0.33-3.15. ?I > don't know if this release fixes my problem. ?Has anyone else had problems > with OS/X writing to a Samba share AFTER it's been working for for a while > (in my case 2 months)?For starters, plan an update. Even RedHat has been publishing the "samba3x-3.3.8" package as part of their "Supplementary" support channel for RHEL 5. I'm sorry this hasn't made it to CentOS, but that 3.0.33 code base is relatively old. As clients evolve, it's worth keeping the servers up to date, and RHEL 5 has gotten pretty long in the tooth. There's are very nice 3.5.2 SRPM's and RPM's at ftp://ftp.sernet.de/pub/samba/3.5/rhel/ I'm working with them right now, and they seem quite solid on RHEL 5 and CentOS 5.