10.6: Slow SMB browsing of Windows Servers fixed | 16 comments | Create New Account
Jul 28, 2009 I'm using samba on linux and grabbing files with it using samba clients on OS X all the time at home and I never see any kind of disconnections. Im not sure it should make a difference, but I have samba 3.0.5 on my OS X machines (the version coupled with MacOS 10.3.8) and samba 3.0.10 on.
- Sep 10, 2017 Heres a Tutorial showing you how to setup SAMBA in OS X/macOS. This will allow Kodi & Windows Clients to connect to your Mac or OS X Server/macOS Server. A lot of people have requested for this.
- Samba runs on most Unix, OpenVMS and Unix-like systems, such as Linux, Solaris, AIX and the BSD variants, including Apple's macOS Server, and macOS client (Mac OS X 10.2 and greater). Samba is standard on nearly all distributions of Linux and is commonly included as a basic system service on other Unix-based operating systems as well.
Click here to return to the '10.6: Slow SMB browsing of Windows Servers fixed' hint |
The following comments are owned by whoever posted them. This site is not responsible for what they say.
It's my understanding that Apple is ditching Samba with OS X Lion, anyway. Perhaps this is one of the reasons. (http://www.appleinsider.com/articles/11/03/23/inside_mac_os_x_10_7_lion_server_apple_replaces_samba_for_windows_networking_services.html) Thoughts?
Apple is ditching Samba (and uses a rather outdated version on 10.6) because Samba switched the licensing from GPLv2 to GPLv3. They haven't stated what their concern is with GPLv3 but the general impression is depending on how Samba is incorporated into Mac OS software, parts of Apple's software may have to be open sourced according to the license's terms.
![Samba client mac os x Samba client mac os x](/uploads/1/2/6/5/126591928/432949443.png)
GPL v3 releases patents for any users - so if there were any Apple patents involved in the SMB code, anybody that buys Lion is covered.
Apple can't refuse to run modified code (TiVoization).
Any code is released from DMCA.
Apple can't refuse to run modified code (TiVoization).
Any code is released from DMCA.
You can also use TextEdit if you launch it via the terminal.
Some people might find this easier to remember.
Is it possible to take this new samba.config file and share it amongst all of our Macs running in this Windows shop I'm in?
Just to be clear this 'fix' disables, Kerberos, Extended Attributes and the saving of Finder metadata in streams. It is unlikely that all of those are required and whichever one fixes it, might help you troubleshoot what is wrong with your server.
Note to those that use SMB to share to Windows: setting spnego to 'no' will prevent Windows 7 (possibly Vista also) from connecting to the Mac.
Samba Client For Mac Os X 10 11 Download Free
---
Mohammad A. Haque
http://www.haque.net/
mhaque()haque.net
Mohammad A. Haque
http://www.haque.net/
mhaque()haque.net
from: http://www.samba.org/samba/docs/man/manpages-3/smb.conf.5.html
'use spnego (G)
This variable controls controls whether samba will try to use Simple and Protected NEGOciation (as specified by rfc2478) with WindowsXP and Windows2000 clients to agree upon an authentication mechanism.
Unless further issues are discovered with our SPNEGO implementation, there is no reason this should ever be disabled.
Default: use spnego = yes'
This variable controls controls whether samba will try to use Simple and Protected NEGOciation (as specified by rfc2478) with WindowsXP and Windows2000 clients to agree upon an authentication mechanism.
Unless further issues are discovered with our SPNEGO implementation, there is no reason this should ever be disabled.
Default: use spnego = yes'
Another point in the man page explicitly says disabling spnego will disable Kerberos.
Interesting that this is needed. I just tested against a remote Win2k3 server and had no issues opening up dozens of folders that I'd never accessed via Finder's Samba client before and had zero latency problems. I'm not part of a highly tuned environment either, mostly stock, I'm curious as to what is the underlying problem that requires this fix.
![Mac Mac](/uploads/1/2/6/5/126591928/446242426.jpg)
There are some issues which seem to be related to the configuration of Windows servers. Default configurations, in my experience, have no problems with Mac clients. Yet, at the university where I work, we see these problems, with performance and, in some cases, also with Macs being able to connect to a share but not see the contents (files and folders are missing.) Ironically, it seems to happen with the file servers which have been in use for a long time and were configured specifically to work with Macs. Unfortunately, I have not been able to pin down the Windows system administrators and find out what is really going on. There is a Windows Server package called 'Services for Macintosh' and I wonder if that, or outdated versions of it, could be the problem.
Or do this:
http://macwindows.com/snowleopard-filesharing.html#121310a
http://macwindows.com/snowleopard-filesharing.html#121310a
I am unconvinced this will solve 'everyone's' slow browsing problems in every situation.
It is a specific fix for your setup and would probably break things in other situations such as Kerberos.
It is a specific fix for your setup and would probably break things in other situations such as Kerberos.
I think this is a bit of a complicated issued based on the Macs ability to resolve the Windows user and group GUIDs from Active Directory that are used to define the file share permissions.
I manage 4000 Macs for a school district, all bound to AD, and I've seen the ssllllooooowwwww SMB browsing when the AD communication breaks, and the Mac can no longer resolve the AD GUIDs.
In other words, the Mac logs onto the SMB server, tries to figure out it's permissions, sees the ACLs defined to GUID ########, tries to resolve that but can't, spins it's rainbow wheel for a while, then moves onto the next ACL, repeat, then the next, then finally to the next file/folder and repeats the process.
Unbinding and rebinding has resolved the issue for us, but if your Mac is not bound to AD, or if communication to the AD domain is otherwise interrupted, I'd say it's quite possible that this issue would also appear.
I manage 4000 Macs for a school district, all bound to AD, and I've seen the ssllllooooowwwww SMB browsing when the AD communication breaks, and the Mac can no longer resolve the AD GUIDs.
In other words, the Mac logs onto the SMB server, tries to figure out it's permissions, sees the ACLs defined to GUID ########, tries to resolve that but can't, spins it's rainbow wheel for a while, then moves onto the next ACL, repeat, then the next, then finally to the next file/folder and repeats the process.
Unbinding and rebinding has resolved the issue for us, but if your Mac is not bound to AD, or if communication to the AD domain is otherwise interrupted, I'd say it's quite possible that this issue would also appear.
I have to agree with agentx, this WILL NOT fix everyone's slow SMB browsing issue, I have been dealing with this issue since we refreshed 100+ macs in our 90% PC dominated environment. I have spoken with Applecare Enterprise Support engineers and they stated ' it is a know issue with engineering and that hopefully they will find a resolve'. They then proceeded to tell me they would refund our $700 payment for the price of our ticket. This was their exact response:
'I'm just following up on our phone conversation. Engineering is currently aware and is investigating the issue where 10.6 SMB browsing is slower than expected in the finder.
We understand that performance in 10.5 seemed better, this is because of issues with 10.5 not properly reading ACLs. This meant that 10.5 clients were pulling much less data when loading the contents of an SMB share.
Unfortunately to resolve the issues that 10.5 had with SMB, some performance had to be sacrificed. As you have observed, when an SMB share has many folders, in your 700 or more, the 10.6 finder takes quite some time to read the contents.
We expect that performance will be much better in Lion. As I suggested sign up for a Mac Developer Account if possible, that you will give you access to the Developer Releases of Lion so that you can do further testing for your Mac OS X Deployment. '
I have tried all the fixes I can find on the websites, from changing the way the user logs in (EX: Domainuser) to modifying the smb.conf and creating nsmb.conf files. I would really love to but this issue to rest once and for all.
'I'm just following up on our phone conversation. Engineering is currently aware and is investigating the issue where 10.6 SMB browsing is slower than expected in the finder.
We understand that performance in 10.5 seemed better, this is because of issues with 10.5 not properly reading ACLs. This meant that 10.5 clients were pulling much less data when loading the contents of an SMB share.
Unfortunately to resolve the issues that 10.5 had with SMB, some performance had to be sacrificed. As you have observed, when an SMB share has many folders, in your 700 or more, the 10.6 finder takes quite some time to read the contents.
We expect that performance will be much better in Lion. As I suggested sign up for a Mac Developer Account if possible, that you will give you access to the Developer Releases of Lion so that you can do further testing for your Mac OS X Deployment. '
I have tried all the fixes I can find on the websites, from changing the way the user logs in (EX: Domainuser) to modifying the smb.conf and creating nsmb.conf files. I would really love to but this issue to rest once and for all.
Thanks to the person who posted this fix, or workaround.
I manage a huge media library (>1.5 TB) located on a NAS. Connecting via AFP has had various permissions issues that I won't go into here, and has also not been particularly speedy. Connecting via SMB had no permissions issues, but browsing the folder structure has been painfully slow. My workaround thus far has been to use a Windows desktop specifically for this task, with which I have had neither permissions nor timing issues.
Having edited the SMB.CONF according to these instructions, I can now get the job done under OS X. It's a real shame that this otherwise sleek and efficient operating system has such problems with standard networking protocols. I'm working with 10.6.8, and holding off on the upgrade to 10.7 in the hope that these issues will be internally resolved sometime soon.
I manage a huge media library (>1.5 TB) located on a NAS. Connecting via AFP has had various permissions issues that I won't go into here, and has also not been particularly speedy. Connecting via SMB had no permissions issues, but browsing the folder structure has been painfully slow. My workaround thus far has been to use a Windows desktop specifically for this task, with which I have had neither permissions nor timing issues.
Having edited the SMB.CONF according to these instructions, I can now get the job done under OS X. It's a real shame that this otherwise sleek and efficient operating system has such problems with standard networking protocols. I'm working with 10.6.8, and holding off on the upgrade to 10.7 in the hope that these issues will be internally resolved sometime soon.
Learning has never been so easy!
I've seen a number of uninformed and misguided posts about 'Samba' in Mac OS X 10.7 and later, in various locations online, and most recently here in the Spiceworks 'Apple Group' area.
As of 10.7 and later, Apple no longer provides Samba server.
Emphasis on server.
Emphasis on server.
As far back as 10.5, Mac OS X does *NOT* use Samba for client connections
to a samba or cifs (Microsoft) server.
There is a smbclient binary supplied in 10.5 and 10.6 but that is not invoked when making a client
connection (to a Samba or CIFS (Microsoft server) sharepoint via the Mac OS X Finder.
In 10.7 and 10.8, mount_smbfs is still provided but that is also not invoked when making a client
connection via the Mac OS X Finder.
to a samba or cifs (Microsoft) server.
There is a smbclient binary supplied in 10.5 and 10.6 but that is not invoked when making a client
connection (to a Samba or CIFS (Microsoft server) sharepoint via the Mac OS X Finder.
In 10.7 and 10.8, mount_smbfs is still provided but that is also not invoked when making a client
connection via the Mac OS X Finder.
As far as 'Samba' server goes in 10.7 and later, /usr/bin/smbd is actually Apple's 'smbx'.
strings /usr/sbin/smbd | grep smbx | wc -l
60
Excerpt of strings /usr/sbin/smbd | grep smbx :
/SourceCache/smbx/smbx-136.18/src/cmd/smbd/write_file.cpp
/SourceCache/smbx/smbx-136.18/src/cmd/smbd/tree_disconnect.cpp
/SourceCache/smbx/smbx-136.18/src/cmd/smbd/tree_connect.cpp
/SourceCache/smbx/smbx-136.18/src/cmd/smbd/transact.cpp
strings /usr/sbin/smbd | grep smbx | wc -l
60
Excerpt of strings /usr/sbin/smbd | grep smbx :
/SourceCache/smbx/smbx-136.18/src/cmd/smbd/write_file.cpp
/SourceCache/smbx/smbx-136.18/src/cmd/smbd/tree_disconnect.cpp
/SourceCache/smbx/smbx-136.18/src/cmd/smbd/tree_connect.cpp
/SourceCache/smbx/smbx-136.18/src/cmd/smbd/transact.cpp
/SourceCache/smbx/smbx-136.18/src/cmd/smbd/smb_transport.cpp
/SourceCache/smbx/smbx-136.18/src/cmd/smbd/close_file.cpp
/SourceCache/smbx/smbx-136.18/src/cmd/smbd/create_file.cpp
/SourceCache/smbx/smbx-136.18/src/cmd/smbd/negotiate.cpp
/SourceCache/smbx/smbx-136.18/src/cmd/smbd/read_file.cpp
/SourceCache/smbx/smbx-136.18/src/cmd/smbd/session_setup.cpp
/SourceCache/smbx/smbx-136.18/src/cmd/smbd/smb_dispatch.cpp
/SourceCache/smbx/smbx-136.18/src/cmd/smbd/query_directory.cpp
/SourceCache/smbx/smbx-136.18/src/cmd/smbd/close_file.cpp
/SourceCache/smbx/smbx-136.18/src/cmd/smbd/create_file.cpp
/SourceCache/smbx/smbx-136.18/src/cmd/smbd/negotiate.cpp
/SourceCache/smbx/smbx-136.18/src/cmd/smbd/read_file.cpp
/SourceCache/smbx/smbx-136.18/src/cmd/smbd/session_setup.cpp
/SourceCache/smbx/smbx-136.18/src/cmd/smbd/smb_dispatch.cpp
/SourceCache/smbx/smbx-136.18/src/cmd/smbd/query_directory.cpp
/SourceCache/smbx/smbx-136.18/src/ntvfs/darwin/create_file.cpp
@(#)PROGRAM:smbd PROJECT:smbx-136.18
Lest anyone think otherwise, the prior (now extremely old) versions of Samba that Apple had been using (up tot but not after Mac OS X 10.6) do not provide support for domain-style accounts for Vista nor - especially - Windows 7- so nothing beyond basic file-sharing, ie: no domain-style profiles hosted on the server. That incompatibility was fixed in a version of Samba that Apple *cannot* use, due to the adoption of GPLv3 for current versions of Samba.
So Apple does not supply Samba server in 10.7 and later, because Apple can't just ignore the GPLv3 licensing terms for current versions of Samba - they are the required terms of use as put in place by Samba.org.
https://discussions.apple.com/thread/3206725?start=75&tstart=0
'GPLv3 makes it impossible to provide signed binaries without also providing the signing keys. A few seconds of thought will reveal why Apple is unwilling to provide copies of the keys they use to sign system software. Part of locking down OS X security profile required removing anythign that used GPLv3.
Short version: GPLv3 is specifially desinged to be anti-company, and you are going to see a ever widening schism in the FSS/OSS community between GPL and all the other licenses, and you will be seeing less and less GPL code in commercial OSes and more BSD/Apache/&c code.'
In terms of interoperation of Windows (Vista and later) clients and Mac OS X 10.7 (and later) server, in my own testing with proper working DNS entries for the server concerned, and no modifications to Windows, I have not seen any problems connecting (from Windows Vista, 7 and 8) to the Mac OS X Server. Some are experiencing problems but in those cases the pertinent question is: What about that environment is contributing to - or causing - the connectivity issue(s), that do not occur for others in different environments ?
Mac Os Samba Server
2 Comments
Samba Os Level
- DatilDavid_CSG Feb 25, 2013 at 05:41pmI wanted to (re) post this as a 'how-to' to preserve the (ease of) availability for this info.
- DatilDavid_CSG Mar 20, 2013 at 03:57amI should add, for further clarity: As of 10.7 and later, Apple no longer provides Samba server, they provide their own 'SMBX' (read on/above)