10.8.1 Server and windows smb issues

Jumping in here....

I just installed SMBup using all of the automatic installation options.

I've added shares, but I don't see how you restrict which users have what kind of access to each share.

More importantly, though, it didn't fix my file transfer issue. Is there something else I need to do??

I manually turned of SMB sharing in File Sharing in System Prefs, but that didn't do it.

can someone help with this?

thanks!

Charles.

Hello.

You've sent me a message but answering you here will give the answer more visibility.

First of all, you need to understand that the permissions of shared folders are the permissions of OS X itself. There are not (nor can there be) permissions separate to those.

So, what you do if you assign the permissions to the folders themselves in the tradicional way: Using the "sharing & permissions" section of the "Get info" property window or using the "Sharing" system preferences (but if you use SMBUp and Samba make sure you DON'T have windows file sharing (SMB) enabled, or nothing will work).

Another recommendation is to create ad-hoc "sharing-only" users and use those to assign permissions as needed.

One last thing: Every user you want to access your drives shared through Samba/SMBUp needs to exist in the Samba user database. For this you create them using the "Manage Users" section of SMBUp or manually, with the "smbpasswd" terminal command:

sudo /opt/local/bin/smbpasswd -a username

sudo /opt/local/bin/smbpasswd -e username

(the first command first asks for the admin password, then for the username's password, use the same ones you created before as sharing-only)

Thanks Eduardo.

I sent you a follow up email. But I'll post a few questions here too.

I reverted my system to a clone since I couldn't get things back to normal.

OK, so first off, you mention going to system prefs and messing with accounts there and File Sharing. With OS X Server, Apple recommends always doing everything through the Server App. So do you not recommend doing that?

I know you say to create Samba-specific users, but I really need the user names and passwords to mimic those that I already have set up on my client machines. I.e. if I log in as Charles on my windows client, that will automatically access the shares that have Charles added to them in OS X. So I really just want to access the same shares and usernames as I had set up in OS X Server.

also, even after I tried this the first time and got Samba to share some folders and was able to reach them through my windows client, I was still having the same file copy errors to the file shares as I was having before, which was very disheartening. I made sure to turn off SMB in File Sharing in system prefs.

And when I went to Manage Users for the first time in SMBup, one of the usernames I had added to OS X Server didn't show up there. I'm not sure why,

So, I tried SMBup again on a different 10.8.2 machine - still didn't fix file copy issue. I setup everything exactly as you suggested. Created a share-only suer, added it via terminal, added the folder share.

when I try to copy a large folder (15 gigs) across the network to that share from windows 7, I get this error towards the end every time:

http://www.evernote.com/shard/s15/sh/7288f557-d52f-443a-8466-9bc084f0d241/c25cf4 7db727cd62054af3d4993eb897

this is the issue I'm trying to solve.

does SMBup fix this issue? because I haven't found a way to get it to yet...

thanks in advance.

I'm having the same issues. According to the Apple article TS4149 "OS X Server: When saving files on SMB shares, the permissions may be changed so only the owner can read or write" you simply log into the Terminal and run the following line of code:

sudo defaults write /Library/Preferences/SystemConfiguration/com.apple.smb.server AclsEnabled -bool YES

This will "allow you to set very fine-grained control on how new files inherit access from the share. To allow group collaboration of files edited in a SMB shared folder, turn on SMB Access control lists (ACLs) on the server and set the ACL permissions to inherit group read and write permissions from the parent folder." Ok, I've done that and restarted file sharing, in fact to be safe, I restarted the whole computer. Still no love! Whenever a PC user creates a new folder or saves a new file on the shared drive the permissions get locked down and I have to manually log into the Server app and select the share point and then choose to propagate the permissions to the entire folder. I've got several people very upset with the current situation and unless I can come up with a solution this week, they are going to insist that we switch back to a Windows server which will be bad news for the Mac users becasue the Windows server breaks the resource forks on the Mac fonts and we can't search on Windows drives.

I also have an issue with moving large (~2GB) files from a PC to the shared drive. It always times out and says there was a network disruption. Other than those two issue, the OSX Server is running just fine.

Dakoda -

I totally feel your frustration. What's amazing is that the Apple business rep I have recommended I go this route knowing I have an euqal # of windows clients as I have mac clients. It;s ridiculous that they allow you to buy their stuff when they know it doesn't work. The amount of time I've spent on this is preposterous.

I downloaded Dave 10 yesterday in the hopes that would solve all my probelms. It did, sort of. It solved the problem of being able to save properly to shares in the server (thank god!) but I seem to have uncovered a new bug and the Dave people are working on a solution. Basically I can drag and drop just fine to the shares, but saving from an application to the share gives an access denied message and renaming a folder isn't allowed, even though I can create a new one. It's very strange. I'm hoping that weirdness is just a quick fix. If so, then all you'll need to fi all your problems is the $70 Dave, since I can't get Samba and SMBup to work erither.

Apple really needs to take care of this.

Charlesdem,

I was using this "hack" to run every 60 seconds which worked but really bogged down my computer before switching to OSX Server:

chmod -R 770 /path/to/shared/directory

chmod -R +a "group:GroupName allow read,write,append,readattr,writeattr,readextattr,writeextattr,readsecurity" /path/to/shared/directory

This would run every minute and everyone was able to assess all the files. But this really isn't a solution to this issue. My brother has some good friends that work at Apple so I've asked him to reach out to them hoping that someone at Apple can help with this promlem. I'll keep you posted if I get any good news from Apple.

I installed Dave 10 and it solved everything. Super easy. Thank the lord!

Hoping that Apple will fix it soon anyway...

I installed Dave 10 but had to remove it right away. Didn't realize it was it's own server application. Knocked everyone off my Mac this morning. I'm not sure this is the route I want to go, especially with already having the OSX Server application already installed and running.

My brother did suggest running something like <find ./ -mtime -5m> to find any file that had been updated in the last 5 minutes and then run my chmod on those files. This would be a lot more efficient than what I was going before, I just don't know the proper syntax to pull this off.

I spent an hour and a half on the phone yesterday with 3 different support people and we still didn't get either issue resolved. I have 7 more days to find a solution before they pull my Pegasus R6 drive!!!! I love this drive, I really hope I can find a solution next week.

yeah, the whole thing is pretty offensive, I have to say. I'd much rather be able to know that SMB was being handled by Apple in their OWN Server. It's ridiculous that this isn't a serious priority.

Anyone have a solution for this yet? I had a level 1 enterprise support engineer from Apple tell me it was a known issue, and then forwarded on to level two. Level two engineer told me it was not a known issue, that my problem was unique, and that since the problem is not simply an Apple server issue (I only have problems when I am trying to connect from a Windows PC), that I would have to pay $700 to open a support ticket for further help. I am debating trying SMBup, but it sounds like there has been mixed results for the resolution of the problem. We had this drive & share on a 10.7 server originally without this problem, but when we moed it to a new 10.8 server, our Win7 clients started dropping connections left and right. I tried a registry entry to force the Win7 machines back to SMBv1, but that didn't seem to fix the issue either.