smb_iod_timeout - SMB Home directory problems - regular 2 minute beach ball

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?

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.

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

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...

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.

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...

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!

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.