Apple’s OS X Leopard (10.5) had problems with accessing Samba shares. Most of them got fixed in late Leopard releases, 10.5.4/10.5.5. During the last Leopard releases the hope arose, that finally OS X will make it into office environments sharing Windows networks.
Then, Apple released Snow Leopard (10.6). Another step into the right direction by providing built-in support for Exchange Server and Google services. But what happened with SMB? The whole story started all over again. While Samba-shares worked pretty well on Leopard, in Snow Leopard all seemed to be messed up again.
In Snow Leopard, every second try, SMB mounts stall, often even making it impossible to unmount a Windows share. Often the whole system gets unstable and crashes. Not really what we would expect from a system like OS X, huh?
That’s how we mount a Samba share in Finder over Go -> Connect To Server… (Cmd-K)
- stalled connection, Finder hangs (no timeout on hanging SMB mounts)
- whole system crashes
- impossible unmounts without restarting Finder
- copy of a directory only copies the empty directory without its contents
- permission problems, Finder doesn’t allow to write to SMB share, even though permissions are correct
- various other mysterious problems…
The whole thing made working with SMB shares under Snow Leopard a huge pain in the a…, simply impossible. At home, I’m connecting to Debian Linux (Lenny) servers, at work to Windows servers in a Windows network. On both networks I experienced similar problems.
Finally I found a solution for Samba on Debian Lenny. Checkout these two articles:
- Mac OS X Probleme mit SMB Shares
- TIP for Snow Leopard issues with SMB: keywords, WINS, & case sensitive Samba
Here’s my recommended setup,
[global] # What naming service and in what order should we use to resolve host names # to IP addresses name resolve order = lmhosts host bcast wins # avoid problems with Mac OS X 10.5 (Leopard), 10.6 (Snow Leopard) unix extensions = off # avoid some further problems case sensitive = yes
The most important is
name resolve order. Make sure,
bcast comes before
wins. This fixed my name resolve issues and made SMB shares again nice and snappy.
This solution is for Samba under Linux only. Please post your tips and tricks for Windows networks.