8 Replies Latest reply: Oct 19, 2011 4:32 PM by Graham Lower
John_Goss Level 1 Level 1 (0 points)
Regularly our Macs are freezing for approx. 2 minutes with the spinning beach ball. This is happening often, with intermittent frequency. All windows unresponsive during this time, and Activity monitor showing little activity.

With a console window open you will see a smbiodsendall timeout message appear – the second it does, the computer is usable again. E.g.:


02/03/2011 01:34:11 kernel smbiodsendall: Timed out waiting on the response for 0xa0 mid = 0xe9f5
02/03/2011 02:02:45 kernel smbiodsendall: Timed out waiting on the response for 0xa0 mid = 0xafbc
02/03/2011 02:04:47 kernel smbiodsendall: Timed out waiting on the response for 0xa0 mid = 0xb29d
02/03/2011 02:09:08 kernel smbiodsendall: Timed out waiting on the response for 0xa0 mid = 0xe9f8
02/03/2011 02:21:32 kernel smbiodsendall: Timed out waiting on the response for 0xa0 mid = 0x50f1
02/03/2011 02:23:33 kernel smbiodsendall: Timed out waiting on the response for 0xa0 mid = 0x52a0
02/03/2011 14:01:44 kernel smbiodsendall: Timed out waiting on the response for 0xa0 mid = 0xe16
02/03/2011 14:02:30 kernel smbiodsendall: Timed out waiting on the response for 0xa0 mid = 0x3f2f
02/03/2011 14:05:08 kernel smbiodsendall: Timed out waiting on the response for 0xa0 mid = 0xe19
02/03/2011 14:30:01 kernel smbiodsendall: Timed out waiting on the response for 0xa0 mid = 0x286f

Network Configuration
• Macs are bound directly to the Active Directory
• Extended the AD schema to include Mac OS X extensions
• AD contains MCX settings
• User’s home directory is mounted on a Windows 2003 Domain Controller via SMB
• Student shared areas is also mounted via SMB against a Windows Server 2008 server


Google shows only 69 results for the term ‘smbiodsendall’, most of which are the source code for the SMB stack itself.

The following discussions reference users with the same problem, none with solutions.

GoldenWonder – Apple Discussions
http://discussions.apple.com/thread.jspa?threadID=2656781&tstart=29

Checkict – Apple Discussions
http://discussions.info.apple.com/thread.jspa?threadID=2618819&tstart=1

GoldenWonder – edugeek
http://www.edugeek.net/forums/mac/print-66264-about-throw-macs-through-window.ht ml?pp=50
User ‘Sheridan’ reports identical problem, referencing smbiodsendall


SMB 2.0
Some suggestions are made this could be a Windows 2008 issue due to the introduction of SMB 2.0. However, I have tried unmounted the connections to the Windows 2008 server leaving the 2003 Home directory mount open, and this problem still persists.


Any ideas welcome, as this is a major headache!

Mac OS X (10.6.6)
  • AtomicMapleLeaf Level 1 Level 1 (0 points)

    We're haviing almost exactly the same problem, 2003 AD integration, but we're connecting to an EMC NS120 as our primary fileserver.

     

    Have you had any luck?

  • ThHelpdesk Level 1 Level 1 (0 points)

    Same or similar issue here.

     

    We are also getting an exact 2 minute delay and the same SMB timeout errors in the system log.

     

    So far we have tried modifying the TCP_ack setting and chamnging it to 0 from 3, we have turned off the smb notify in the NSMB.conf file as well.

     

    We have also tried running in 64 bit mode, deleting extra keychain entries, connecting using FQDN.

     

    We are using AD as well with snow leopard. Only instead of Win server 2008, we use an EMC NAS.

     

    I would be interested to see if anyone else has encountered this or if they have found a permenant fix yet.

  • Bilmed Level 1 Level 1 (0 points)

    We have the same issue!

    We have testet any fixes that we found on the Internet but nothing helped.

    Have you found any fix yet

  • ThHelpdesk Level 1 Level 1 (0 points)

    No resolution yet, although the problem has gotten less noticable.

     

    We have tried pretty much everything out there on the internet as well but still no luck.

     

    EMC blames apple and Apple blames EMC...

  • Graham Lower Level 1 Level 1 (0 points)

    I do not have a resolution, but we are experiencing some of the same issues, so maybe this information will be helpful to someone who can eventually solve it...

     

    We have 4 Macs (of various forms) which encounter the same issue, and several that don't, when communicating with a Windows Server.  We tried diabling SMB 2.0 and rebuilding permissions, with no luck.

    After a lot of testing, we believe this is a combination of a server issue and a machine based issue:  The server encounters an error and some of the Macs respond well... others less so.

     

    Using a packet sniffer, we've been able to match an error reported on a Mac exhibiting issues to the server reporting an error using the Multiplex ID (mid).  The server returned an error (a "Non-specific" error, per the description), and it seems the Mac either missed or ignored it.  This lead the Mac to wait until the time out before resuming dialog. 

     

    I speculate there are multiple conversation per thread and when one of the conversations get hung up, it blocks the thread leading to the beach balls.  The reasons I think this is that when testing we can request a folder listing, get the beach ball, then eventually see the files.  The error, however, has nothing to do with the path request, but instead a totally different file/path.  You can also see the delay in the conversation that is dealing with the path being tested.  Interestingly enough, there are other conversations going on at the time.

     

    At this point we are looking into how to reduce the timeout period, which we hope will bring immeidate relief.  Several of our Macs exhibit no slowdowns, even when moved to the same network port as ones exhibiting errors.  Thusly our long term goal is to figure out if a) the "good" Macs either see the SMB error response and move forward, b) are not generating errors on the server, ir c) are just set to timeout much quicker than the "bad" Macs.  If the Mac is not spawning the SMB errors, we'd like to eventually address those as well. 

     

    If anyone knows where to find/tweak SMB timeouts, it would be appreacited.

     

    Cheers. 

  • eLud Level 1 Level 1 (0 points)

    Same problem here. 6 Mac Pro using 10.6.8, in a Windows 2K3/2K8 environement. Graphic designers are experiencing many 2 minutes delay very frequently (several times a day).

     

    Same error in the logs : smb_iod_sendall: Timed out waiting on the response for 0xa0 mid = 0x7d03

     

    I'am trying to update the machine to Lion as a user reported on AFP458 forums that this may solve the issue...

  • eLud Level 1 Level 1 (0 points)

    As I was saying before: Lion upgrade corrects the problem. So if your are experiencing those issues, it might be a good idea to upgrade!

  • Graham Lower Level 1 Level 1 (0 points)

    We can't upgrade to Lion because of incompatibility of some of the software we need for production.   Also, I stated 4 machines had an issue, when it was 3.  2 do not have an issue.  So far the only correlation we've been able to discover is the three with a problem all have CS5, while the two that don't have CS4.  Unforuntately, we are not in a position to install CS5 on either of the two that don't, nor remove it from the three that do, so testing further will require creativity.