#Smbup download install
#Smbup download free

This means that systems must have a Darwin-Specific workaround to work with OS X. To be completely true, Apple is breaking with 'tradition' here, even if it's not strictly breaking standards. This is because Darwin has nested groups, pretty much. The problem is, oversimplifying, that the OS reports a maximum number of groups but when queried reports a bigger number. I'm proficient enough technically to know what's causing the issue, but not proficient enough to fix it in the samba source. In the samba logs, if enabled, the error is If you try to connect you get an error with my user, not with any other. ref0, ref1, ref2 ) this is a common problem with Lion, as groups can easily spill over the 16 maximum limit. But my own user (the default admin user of the system) never works. If I try to set the smbpasswd of all users with sudo (as root) I can. This is a common problem in all Samba 3.2.15 implementations from MacPorts and it was my understanding it's unavoidable due to problems with the handling of groups in Lion, something Samba has acknowdledged. For them I can open even their home directories, but not for my own.

One for the main admin user, the other two a 'normal' user and an admin user.įor the latter two I can open all shares, authenticated, with their correct permissions. Three users had been 'activated' (created) in smbpasswd. Veto files = /Thumbs.db/.DS_Store/.TemporaryItems/TheVolumeSettingsFolder/TheFindB圜ontentFolder/Temporary Items/Network Trash Foder/.AppleDouble/.bin/.AppleDesktop/._*/ The problem with this approach is that most users have only one account in their systems so it's not an ideal solution. I currently can connect authenticating with any user but my own. But it would provide an ideal working starting point.

#Smbup download free

I can see that by default 'passdb backend = tdbsam', so I'll try this change anywayĬan you share your smb.conf? Feel free to edit it for privacy. When you say you use smbpasswd as the pass backend aren't you just using the default? Does it work for the default system account? If so, what do you use as your 'security' entry in smb.conf? As long as:ġ.-The users from smbpasswd exist in the system (can't create ad-hoc smbpasswd users not already in Lion)Ģ.-The default user (the default admin) won't ever work (this is the one that has group problems). By leaving the default 'security = share' I can store usernames and passwords with smbpasswd and it can authenticate. I should've clarified I can run authenticated to a degree. Newer versions either don't compile or crash on startup.ġ.-Have you been able to run MacPorts Samba version (3.2.15) in authentication mode? (guest mode works OK) If so, how did you manage to do so?Ģ.-Have you been able to compile/run a newer version of Samba in Lion where authentication (not only guest access) works? If so, how did you do it, did you modify MacPorts or Homebrew for it? This version has some issues with user group resolution so I've been trying to get a newer version to work, but I haven't had any luck.

#Smbup download install

I made it mainly because a bunch of friends of mine have mediacenters or old devices that can only communicate through SMB1 and Lion's SMB implementation doesn't work for them.įor this I have made an installer for Samba and its dependencies (my program allows the user to download and install it) but it's from the latest version supported by MacPorts (which is 3.2.15), a somewhat old one. I have made a tool (called SMBUp) that is supposed to be a front-end for Samba for Lion.