Samba growing pains continue in OS X Lion

Samba growing pains continue in OS X Lion

Summary: Apple made a significant change in Samba support in OS X with its move to SMBX in OS X Lion. The changeover continues with the forthcoming OS X Mountain Lion. However, longtime Mac admins will likely find some frustration when dealing with the change.


A recent Apple support note points to the issue:

When attempting to use smbpasswd to change a user's password in Terminal, the command does not work. Instead, the message "smbpasswd: Command not found" appears in Terminal. Resolution To change a user account password in Lion, open the Users and Groups pane of System Preferences. The Mac must be bound to same domain the user belongs to. Additional Information The smbpasswd command line utility is part of Samba, which is not included with Lion or Lion Server.

If you ever want to find the list list of acceptable SMBX commands, type smbutil in Terminal.

Apple started bundling Samba in Mac OS X Jaguar, v.10.2, to support Microsoft's SMB (server message block) file and directory services. With the introduction of OS X Lion, it switched to an in-house software, which supports the MS-SMB2 protocol released in 2007. The previous Mac Samba implementation supported SMB1.

The switch hasn't been pain free, with a rash early complaints cropping up with NAS (network-attached storage) units that relied on SMB for file services. There still are plenty of file-sharing and access complaints on Apple's discussion boards. Often there will be no problem with Windows CIFS/Samba or the open-source Samba under Linuz, but when we get to SMBX, there's a different story.

We can hope for improvement in Mountain Lion.

Topics: Apple, Enterprise Software, Networking, Operating Systems, Software Development, Windows

Kick off your day with ZDNet's daily email newsletter. It's the freshest tech news and opinion, served hot. Get it.


Log in or register to join the discussion
  • Sounds more like an issue with incompetent IT personel

    From the article it is clear that the new version supports a different protocol. So why even install it if the protocol the company is using is different??

    Only a completely incompetent IT person would just install new software without testing it in an isolated way first. If your network is designed for an old obsolete protocol, don't expect software designed for newer protocols to be backwards compatible without doing some additional work.
    • "So why even install it if the protocol the company is using is different?"

      Because it "just works" or suppose to according to Apple.
  • not quite

    Samba 3.6 fully supports SMB2, the problem is Apple was bundling ancient version 3.0 with OSX (released in 2003) and they switched to in-house SMBX because they didn't like new SAMBA license.
    Both old Samba and new SMBX are nightmare on OSX btw - old samba client in particular.

    Oh - and it "Linux", not "Linuz"
  • Looks like it would be easier... compile Samba from source. Bummer.
    John L. Ries