Topic: Problem with Apple Mac "leopard" and samba shares

[brianr]

Hi

One of my customers has a mixed office of MACs with "tiger" and two with "leopard" (these are previous and latest respectively versiojns of the MAC operating system).

I believe we are connecting to the SMEServer (7.3) using samba (my MAC knowledge is thin).

On the "leopard" systems, whenever a file is saved to a shared i-bay, the permissions are set to <username>:<username>, rather than  <username>:shared, resulting in the other MACs (and a PC) being unable to access the file.  when a "tiger" saves a file the group is set correctly.

The leopards are authenticating correctly as far as i can see (the correct "username" share is accessible).

Anyone else encountered this? Any thoughts welcomed.

[CharlieBrady]

Any thoughts welcomed.

Here's one you should be familiar with:

Don't report problems here.

You know the rest ...

[brianr]

Charlie

I thought long and hard about whether to post here or in bugzilla, but i am looking for someone who has experience of using MACs in a configuration with SMEServer, so i surmised that I am far more likely to find someone here, than in the bugzilla.  As it works fine for the "tiger" variant, it is unlikely (but not impossibly) to be an SMEServer bug, more likely a change in the way leopard works.  Possibly a (already known?) leopard bug.

So, I shall stick to my guns and wait and see...

[imcintyre]

Does this help? I see that it is for Ubuntu but perhaps there's an idea there.

http://www.neowin.net/forum/index.php?showtopic=598014

There seems to be a lot of people with apple samba issues judging from a google search.

[brianr]

yes, I saw this one, it seems to apply to a total lack of visibility of the server, whereas we can see the server, its just saving files that seem to be a problem.

Is there anyone out there knowingly using Leopard?

[judgej]

I know you are already listed for notifications against this bug (and yes, it is a bug) but for those that don't know, here is the bug that has been raised:

http://bugs.contribs.org/show_bug.cgi?id=4164

I have posted (against the bug) some simple instructions for added a custom template to sort this problem out on your server, since it does not look like there is any agreement on the best way forward as a general fix for SME Server, at least not yet. It is really causing us problems with the new Macs attached to the network, and I'm surprised it is not being more widely reported. Perhaps there is a fix that could be applied to the Mac side instead, but I've not found one.

I hope the post helps, and that reporting solutions to other users on this forum is allowed.

-- Jason

[brianr]

hi jason

Yes, I had seen your posting in the bug tracker, but i am sure people will benefit from your posting here as well.  My client is currently coping with the problem by having moved his Mac(s) back to tiger (I think it is).  We are still "cleaning" up the ibays as a result of the leopard attacks!

[mercyh]

Brianr,

Doesn't going into the Ibay on server manager, clicking on MODIFY and saving the current settings reset the group on all the files in that IBAY?

(I had used Winscp to drop a bunch of files in an IBAY and they inherited root:root. by doing the above all the files were reset to root:group.)

[brianr]

aha - what a good idea, am trying it now and will report back...

[janet]

mercyh

by doing the above all the files were reset to root:group.

That root user ownership will likely cause you problems later.
They should really be user:group
where user is a member of the group who owns that ibay,
and usually the user who created the file.

[brianr]

Actually in my case the ownership problems are user:user, so i guess I am ok (ahd the lack of the sticky bit on directories) .

[judgej]

Doesn't going into the Ibay on server manager, clicking on MODIFY and saving the current settings reset the group on all the files in that IBAY?

Yes - just tried that and it cleared up a lot of problems on an i-bay. I was going to write a script to do that, but your tip has saved me the effort. Thanks.

I also had the problem with WinSCP. There is an option in WinSCP to tell it not to change the privileges on an uploaded file. You might want to look into that. The option is set globally (not per-server) and is under Preferences->Transfer->Upload options->Set permissions. By default this is set to 'rw-r--r-- (+x)' but you can turn that off.

-- JJ

[mercyh]

Jason,

Thanks for the info on WinSCP. I just turned mine off. Hope it takes care of the issue.

Royce