Hello, We are having this issue with samba and OSX 10.2.3. We are using freebsd4.7 serving samba as a fileserver for our company, we have a mix of windows and macs connecting to it. The windows machines work just fine the macs are another story. I have narrowed it down to this: I can open a file/document from the fileserver on my mac and edit it but it tells me I dont have the permissions to copy it back. This is from a volume that I mounted on the desktop using the 'apple+k' to mount it. When I mount it by command line I can edit the file/document(anyfile) and copy it back with no problem. I have also found this to be true on my linux system. Exact same problem when trying to edit and copy a file back to the fileserver that has been mounted on the desktop, I get the permission denied error. When mounted by command line I can open any file and edit it then copy it back. Has anyone run into this before and have found a solution they would like to share? I have done google searches but from everything I find it doesn't answer my question or im just not posing the question correctly. Thanks for any help, Jon
I am having a permission denied error as well. I know that osx has huge default permissions error. if you create a file on the server then you no longer have access to read it, and various problems of the same sort. My problem is joining a system to a mac osx server 10.2.3 domain, if you have any expertise in that, I would love some help. Mac 10.2.4 should be out very soon. hopefully that will solve alot of problems. Good luck, mac osx is a baby, still growing up. Kyle Loree Rendek Communications Kyle@caisnet.com jonr@destar.net writes:>Hello, > > We are having this issue with samba and OSX 10.2.3. We are using >freebsd4.7 serving samba as a fileserver for our company, we have a mix >of windows and macs connecting to it. The windows machines work just >fine the macs are another story. > > I have narrowed it down to this: I can open a file/document from the >fileserver on my mac and edit it but it tells me I dont have the >permissions to copy it back. This is from a volume that I mounted on the >desktop using the 'apple+k' to mount it. When I mount it by command line >I can edit the file/document(anyfile) and copy it back with no problem. > > I have also found this to be true on my linux system. Exact same >problem when trying to edit and copy a file back to the fileserver that >has been mounted on the desktop, I get the permission denied error. When >mounted by command line I can open any file and edit it then copy it >back. > > Has anyone run into this before and have found a solution they would >like to share? I have done google searches but from everything I find it >doesn't answer my question or im just not posing the question correctly. > >Thanks for any help, > >Jon
Hi, I have a samba server on freebsd4.7 using samba-2.2.6.p2_1. When from command line I mount a share from our file server I can edit and copy any file or document and save it back to the fileserver no problem. If I mount the share on my desktop I can edit and copy any file or document but I cant save it back to the fileserver. I get a permission denied error. This happens on both my RH7.3 and my OSX 10.2.3 systems. Is there a setting I can put in my smb.conf file to fix this? Jon
On Thu, 2003-02-06 at 14:08, Jon Reynolds wrote: Hi,> > I have a samba server on freebsd4.7 using samba-2.2.6.p2_1. When from > command line I mount a share from our file server I can edit and copy > any file or document and save it back to the fileserver no problem. > > If I mount the share on my desktop I can edit and copy any file or > document but I cant save it back to the fileserver. I get a permission > denied error. This happens on both my RH7.3 and my OSX 10.2.3 systems. > > Is there a setting I can put in my smb.conf file to fix this? > > Jon >This is now working for us. Here is what we did to make this work. There are two possibilities to what made this work. One is what was told to me about creating '.' files for the Macs. The Macs create a '.' file in the directory to, I'm assuming, hold the resource fork for the file so the Mac can read it. The other solution might have been that when I looked back inot the ServerFiles share on the server I noticed there were already some '.' files created by the Macs. One of these was called '.FBCLockFolder' I deleted all the '.' files that I found to be created by the Macs and everthing is working as expected. Unfortunatley, I tried both solutions at once so can't say for sure which one was the fix. But I have posted both solutions in case anyone else runs into this problem. Jon