joekmaclinux

Q: 10.9.2 Mavericks and can no longer connect to our SMB file share on the network.

Smb was working under 10.9.1. Now  smb and usning the finder I get "connection failed".  Both of my NAS are not out when i am using my mac book pro  thru the wifi connection.    Is any one else have the same problem?

Mac Pro, OS X Mavericks (10.9.2)

Posted on Mar 2, 2014 2:28 PM

Close

Q: 10.9.2 Mavericks and can no longer connect to our SMB file share on the network.

  • All replies
  • Helpful answers

first Previous Page 4 of 6 last Next
  • by PaakWaan,

    PaakWaan PaakWaan May 29, 2014 1:59 AM in response to itsmayes
    Level 1 (0 points)
    May 29, 2014 1:59 AM in response to itsmayes

    It must be a Win Server issue, as i never ever had any issue to mount shared drive with maverick.

    As i said, i now have 30 macbooks, all works perfectly fine.

    When i first saw this thread i had only 10 mackbook so i was not sure if i was just being lucky.

    My only issues i had was that i had to put the IP because of DNS problems, it wasn't resolving.

    Now i have fix that and it's all good.

    I'm 99.9% sure it's not OS X related, so you guys can wait a long time to get help by Apple.

    Seriously look at your Win Servers settings.

  • by RemcoFromOuterSpace,

    RemcoFromOuterSpace RemcoFromOuterSpace May 29, 2014 2:25 AM in response to PaakWaan
    Level 1 (0 points)
    May 29, 2014 2:25 AM in response to PaakWaan

    So your solution is to buy Apple products exclusively?

     

    I shall pass that thru to my workplace where we serve about 9000 students and staff.

     

    Don't think they will react very enthusiastic to this plan though.

     

    At home I use an old Xserve "Xeon" (Gainestown) from I believe early 2009 as a server. My Windows and Linux machines can connect perfectly to a SMB network shares. Mavericks machine (2013 MacBook Pro) craps out.

  • by IsNull,

    IsNull IsNull May 29, 2014 2:32 AM in response to PaakWaan
    Level 1 (5 points)
    May 29, 2014 2:32 AM in response to PaakWaan

    @PaakWaan

    Just because you can connect to a Windows Server with 30 Mac Books does not proove anything. For example, I am able to conect to a Windows Server 2012 perfectly (even over slow WAN / VPN Tunnels), but I am not able to get a usable connection to a normal Windows 8.1 Share in my LAN.

     

    With other Windows Computers, and even a Windows running in a VM on my Mac Book, I have no trouble to access the share of the Win 8.1.

     

    It is obvious that the problem is not occuring in all constelations, thus it might be harder to track down. Yet there are so many people expiriencing issues with it, it can not be discussed away.

  • by PaakWaan,

    PaakWaan PaakWaan May 29, 2014 2:49 AM in response to IsNull
    Level 1 (0 points)
    May 29, 2014 2:49 AM in response to IsNull

    i understand your frustration, but explain me how could it be an OS X issue if i can mount shared drive with SMB ?

  • by RemcoFromOuterSpace,

    RemcoFromOuterSpace RemcoFromOuterSpace May 29, 2014 3:45 AM in response to PaakWaan
    Level 1 (0 points)
    May 29, 2014 3:45 AM in response to PaakWaan

    Because there is a difference between the SMB2 protocol which Apple use in Mavericks (with it's own flavoring I might add) as a replacement of it's proprietary SMBx (which was useless) and AFP (Appletalk Filing Protocol), and the SMB protocol.

     

    It might be that on an all Mavericks based network things SEEM to be working right. For the rest of the World it doesn't.

  • by itsmayes,

    itsmayes itsmayes May 29, 2014 6:37 AM in response to RemcoFromOuterSpace
    Level 1 (0 points)
    May 29, 2014 6:37 AM in response to RemcoFromOuterSpace

    I tried a Win Server adjustment this morning after reading the below article earlier this week. As hopeful as I was, our Macs still experience extremely long wait times to connect & dropped connections to shares...using SMB, CIFS, or any other of the proposed "tricks" noted above.

     

    http://redmondmag.com/articles/2014/05/16/network-performance-problems.aspx

     

    I'm really hoping that Apple's silence on this will be all be fixed in the proposed upcoming OS update in June.

  • by paulo555,

    paulo555 paulo555 May 29, 2014 7:23 AM in response to PaakWaan
    Level 1 (0 points)
    May 29, 2014 7:23 AM in response to PaakWaan

    I'm new in mac world and my problem is this:

     

    In my home, I have a domestic network with some shared folders between pc's (1 windows vista; 1 windows 8.1 pro; modem-router Technicolor TG784n v3).

     

    With the new Macbook pro (OS X 10.9.2), I'm trying to use the same resources and communications between computers.

     

    After some basics configurations, my mac recognizes the other two computers. However, when I try to access them sometimes that works, sometimes not. When it works, the process is very slow and, after some solicitations, the connection crash.

    On Console, I identify some erros like this:

    - kernel: smb2_rq_credit_decrement: Timed out waiting for credits 35

    - kernel: smb2_smb_parse_change_notify: smb_rq_reply failed 60

    - kernel: smb_iod_reconnect: Reconnected share XXXXX with server PC-W81

    - kernel: smb_fid_get_kernel_fid: No smb2 fid found for fid 57550ef47cc64007

    etc.

     

    All this occurs when i try access a shared folders on windows pc's (not the reverse).

     

    So, my problem isn't a server question but a simple access to shared folders! No problems between pc's but only between mac and pc! A obvious mac problem, no?

  • by RemcoFromOuterSpace,

    RemcoFromOuterSpace RemcoFromOuterSpace May 29, 2014 11:36 AM in response to paulo555
    Level 1 (0 points)
    May 29, 2014 11:36 AM in response to paulo555

    Looks like it.

     

    Somewhere in this thread there are some tips to set the Mac to use SMB instead of SMB2. You could try those as a start.

     

    Bit hit and miss and not the fastest though.

  • by PleasantSpectrum,

    PleasantSpectrum PleasantSpectrum May 29, 2014 11:50 AM in response to paulo555
    Level 1 (10 points)
    May 29, 2014 11:50 AM in response to paulo555

    I'm curious to know which versions of Windows are being connected to.  I played around with this a bit more today, connecting to shares on Windows Server 2012 R2, Server 2008 R2, and Server 2003 R2 using smb:// (NOT cifs://).  The connections to the latter two seemed to work fine no mater what I tried, and the connection with the 2012 R2 share worked fine, as long as I connected to one of the other server shares FIRST, AND left that first share connected.  If I disconnect from all shares, and connect to the 2012 R2 share "fresh," I get the browsing delays.

     

    Another interesting observation, is that if I connect to a remote 2012 R2 share (over a WAN connection), it does not seem to have problems.

     

    So my theory seems to go, that there is some problem with SMB2 protocol negotiation on a LAN, between OS X 10.9.3 and Windows SMB3 shares (Windows 8[.1] and Server 2012 [R2]).  And when the Mac mounts a share on an SMB2 server first (Server 2008 R2), it then correctly negotiates an additional connection to an SMB3 server. 

     

    The newer Windows servers with SMB3 support backwards-compatibility with SMB2, but perhaps Apple's implementation of that downward negotiation is what's to blame.

  • by RemcoFromOuterSpace,

    RemcoFromOuterSpace RemcoFromOuterSpace May 29, 2014 12:39 PM in response to PleasantSpectrum
    Level 1 (0 points)
    May 29, 2014 12:39 PM in response to PleasantSpectrum

    At work (technical university) we have all kinds of Win Servers (Almost all Windows version, Linux, Mac, etc) and network sharing solutions.

     

    We came to the same conclusion as you, although we also experienced some trouble with Mac's SMB2 implementation (they seem to have used their own flavoring of some sort) communicating with SMB3.

     

    We believe it's not only the SMB2 implementation that is to blame, because other network protocols have issues to. Build in Mavericks screen sharing solution for instance, even between two computers with same OS and hardware.

     

    Maybe they messed something up in the networking stack. We just don't have time to investigate deeply.

  • by PleasantSpectrum,

    PleasantSpectrum PleasantSpectrum May 29, 2014 1:43 PM in response to RemcoFromOuterSpace
    Level 1 (10 points)
    May 29, 2014 1:43 PM in response to RemcoFromOuterSpace

    Then there's this site:  http://macsmbissues.com/

     

    Their test config doesn't involve *any* Windows servers at all, just Linux servers running Samba..further evidence that this isn't a Microsoft issue.

  • by boomish,

    boomish boomish May 30, 2014 4:21 AM in response to PleasantSpectrum
    Level 1 (4 points)
    Mac OS X
    May 30, 2014 4:21 AM in response to PleasantSpectrum

    I have the same issue with my small home Lan network, been workign fine for years, upgraded to Mavericks now nothing will talk to each other, well it will if you wait 20-30 mins..jeez Apple please fix this , even the Apple TV is at a crawl!

  • by kazop,

    kazop kazop May 30, 2014 9:29 PM in response to joekmaclinux
    Level 1 (0 points)
    May 30, 2014 9:29 PM in response to joekmaclinux

    Hello,

     

    So far i have done quite a bit of work to find a fix to the SMB issues in OSX mavericks. By this time I have tried every single posted "solution" out there.

     

    There are multiple issues with Mavericks SMB and Finder implementations. These issues stack on one another. Some issues may only be evident under the right circumstances.  For example lots of small files and directories and very large SMB shares.  This explains why some people report issues some don't. I belive that the people that report Maverics as working "wonderfully" simple do not have the scale to see an issue. Mavericks works great until you put it under stress.  Here are my findings (general terms is late to type)

     

    Issue 1) Listings of large directories in SMB shares take a long time.   This is one issue that can be fixed if the directory listing is made of other subdirectories.  It is simply a matter of removing all .DS_Store files and modifying the OSX clients to not write these files to network shares. (defaults write com.apple.desktopservices DSDontWriteNetworkStores true)  If the directory/subdirectory structure is well planned then some of of the below SMB issues can be alleviated.

     

    Issue 2) Slow small file operations (list read write).  OSX's SMB implementation does not perform well with small file operations.  This causes slow listings of directories that are full of small files.  The work around is to modify the file structure to avoid large directories of small files. 

     

    Issue 3) Finder likes to adquire all metadata from a directory before it renders the listing.  No fix for this. it just adds to issue 2. However work around is to modify the file structure to avoid large directories of small files.

     

    Issue 4) Slow reads and writes of "files" that are actually directories full of small files, for example keynote files and iPhoto libraries.  I have not found a single solution for this but it comes down to poor small file performance in OSX's SMB

     

    I have done my testings with both single Samba servers.  and Clustered Samba servers. I am very confident on the Samba server side. I have also tried server side tweaks. It always comes down to the OSX client being at fault. Windows Linux clients always perform well.  Working for a creative company means that a large majority of our user base is OSX and I am really eager for apple to address this issues.

     

    I have to add that large file operations work great in Mavericks i ussually get full bandwidth 100MBps to 120MBps when reading and writing single large files.

  • by RemcoFromOuterSpace,

    RemcoFromOuterSpace RemcoFromOuterSpace May 30, 2014 9:36 PM in response to kazop
    Level 1 (0 points)
    May 30, 2014 9:36 PM in response to kazop

    @Kazop

     

    Regarding issue 2. Do you experience Finder crashes when using the "quicklook" feature on multimedia files (video, photo, music)?

  • by itsmayes,

    itsmayes itsmayes Jun 11, 2014 11:58 AM in response to kazop
    Level 1 (0 points)
    Jun 11, 2014 11:58 AM in response to kazop

    Thanks kazop! Your work seems to bring some things to light. I am going to try the fix you mention in Issue 1 and will report back.

     

    However, in the past week, I have moved some shares that my Macs access more frequently to a Mac Server with OS X 10.9.2 hoping to help with connectivity. It helped somewhat but now we are experiencing connection issues with it as well. I'm seeing these issues arriving when, as you said, Mavericks are "put under stress".

     

    Finder crashes and must be relaunched...taking nearly 3-5 minutes to relaunch.

     

    Windows stations purring along without a skip.

first Previous Page 4 of 6 last Next