Connecting to a Windows share from 10.9.2 takes a LONG time

Question

Level 1

8 points

Connecting to a Windows share from 10.9.2 takes a LONG time

Hi together,

I'm pretty sure that I had no problem with Mac OS X 10.9.1 but since the last update connecting to my Windows 8.1 share takes a really long time (several minutes) before I can use the share in a normal way. My machine is a MacBook Pro with Retina display (late 2013 model).

I use the Finder (⌘K) to open the "Connect to Server" dialog and enter the URL smb://beedo ("beedo" is the name of my windows box). Immediately a window pops up that lists the available shares. So far so good. But as soon as I select a share and click "OK" the trouble begins: My running iTunes as well as another filemanager become unresponsive and the Finder shows an empty share. Eventually, after waiting SEVERAL! minutes, things start to normalize: Finder shows the content of my share, iTunes and the filemanager become responsive again. I can then use the share in a normal way.

Looking at the system log via Console.app reveals some entries that might be interesting. During the waiting period these lines show up (every minute or so):

12.03.14 20:47:34,000 kernel[0]: smb2_rq_credit_decrement: Timed out waiting for credits 35

12.03.14 20:47:35,000 kernel[0]: smb_fid_get_kernel_fid: No smb2 fid found for fid 2cad65827d32a4ac

12.03.14 20:47:35,000 kernel[0]: smb_iod_reconnect: Reconnected share DATA with server BEEDO

12.03.14 20:47:35,000 kernel[0]: smb_fid_get_kernel_fid: No smb2 fid found for fid 2cad65827d32a4ac

12.03.14 20:47:35,000 kernel[0]: smb_iod_reconnect: Reconnected share DATA with server BEEDO

Finally when things normalize I stumble upon these lines (several more of them):

12.03.14 20:56:26,802 smbd[69614]: XPC: peer event: , ipc error: Connection invalid

12.03.14 20:56:26,809 smbd[69614]: XPC: peer event: , ipc error: Connection invalid

Does anyone know what might be the cause? Looks like some kind of timeout that happens here. Maybe something on the Windows side that needs to be considered?

Many thanks in advance,

Oliver

MacBook Pro with Retina display, OS X Mavericks (10.9.2)

Posted on Mar 12, 2014 1:40 PM

Reply

Answer 1

Top-ranking reply

lukash

Level 1

4 points

Apr 12, 2014 3:15 PM in response to sLoP

This problem drives me nuts. I operate a Windows 2012 server with a few shares and this problem only appeared after update to 10.9.2.

I've just spent quite some time debugging it and not even cifs:// helps me, just sometimes.. even if

Get-SmbSession | Select Dialect,ClientComputerName,ClientUserName

in Windows PowerShell shows I'm using Dialect 1.01 it's useless, negotiation takes ages..

For SMB2 the freaking rainbow circle never ends and dmesg shows:

smb2_rq_credit_decrement: Timed out waiting for credits 35 smb_iod_reconnect: Reconnected share _share_name_ with server _server_fqdn_ smb_fid_get_kernel_fid: No smb2 fid found for fid _fid_

Currently the only Mavericks 10.9.2 stable solutions remains:

echo "[default]" >> ~/Library/Preferences/nsmb.conf echo "smb_neg=smb1_only" >> ~/Library/Preferences/nsmb.conf

What's more there to say .. Y U NO FIX THIS APPLE! AIN'T NOBODY WANTS SMB1!

Reply

Answer 2

sLoP Author

Level 1

8 points

Apr 5, 2014 1:18 AM in response to AussatSpaceSparky1

So, I finally tested it at home and in fact using cifs instead of smb let me connect without delay. I can access and transfer files again. Thanks again. 🙂

Cheers,

Oliver

Reply

Answer 3

Apr 3, 2014 2:05 AM in response to sLoP

Had a similar problem. One way is to substitute cifs for the smb in the finder url.

Refer to http://forums.macrumors.com/showthread.php?t=1676896

Still can't drop files on to the opened WIN 8.1 folders. Chasing that up. May be Norton.

Neil

Reply

Answer 4

Apr 4, 2014 9:43 PM in response to sLoP

This link also shows the same reasoning. http://osxdaily.com/2013/10/30/connect-smb-nas-network-shares-os-x-mavericks/

With my not being able to drop files, it was just using the wrong name.

I figured out in my WIN 8.1 PC, the login name was not the same as my C:/Users/ account name. I had two accounts, one was the"new" WIN 8 preferred Name@outlook.com account and the other, my local Name account. The first had a c:/users/name home folder, and the second was c:/users/name_2 home folder! Just logged in as Name_2 with the password, and I could read/write files!

Reply

Answer 5

sLoP Author

Level 1

8 points

Apr 3, 2014 2:44 AM in response to AussatSpaceSparky1

Gee, thanks a lot! Will try that out when I come home. Sounds very promising. 😀

Regards,

Oliver

Reply