SMB broken on Server 3.2.1 and OS 10.9.5 ?

Discussion in 'Mac OS X Server, Xserve, and Networking' started by initialsBB, Sep 18, 2014.

  1. initialsBB macrumors 6502a

    Joined:
    Oct 18, 2010
    #1
    Is anyone who updated to the latest version of OS X Server (3.2.1) and having problems with SMB sharing ?
    This was already hit and miss with previous Mavericks versions, but now seems totally broken. My Mac also running 10.9.5 still defaults to SMB when connecting to the Server's file sharing, and now results in a systematic error -36.
    If I connect using AFP there is no problem copying files to the server.
    Is there something I'm missing ?
     
  2. mvmanolov macrumors 6502a

    Joined:
    Aug 27, 2013
    #2
    no problem on smb here. sorry to hear you are having issues.
     
  3. chrfr macrumors 603

    Joined:
    Jul 11, 2009
    #3
    I'm connected to a server I upgraded as a test. No SMB issue so far.
     
  4. MacModMachine macrumors 68020

    MacModMachine

    Joined:
    Apr 3, 2009
    Location:
    Canada
    #4
    SMB has been broken for along time now.

    especially in a mixed platform environment.

    after spending several days with apple and screwing around i ended up switching our servers with freebsd.
     
  5. muddyfunster macrumors newbie

    Joined:
    Jan 6, 2013
    #5
    I tested this combo while in the latest beta and found it quite poor with Windows machines particularly with office document lock files hanging around and becoming inaccessible when users went idle. I filed feedback about this. I haven't had chance to test the released version yet but didn't receive any feedback about the beta issues.

    Am I allowed to comment about my Yosemite public beta 2/OS X Server 4 beta testing ? I'm not sure under the terms of the license agreement ... but I will say :cool: ( with some reg. tweaks for Win 8 machines )
     
  6. jeremysteele macrumors 6502

    Joined:
    Jul 13, 2011
    #6
    Yeah, thank you Apple. Their samba "improvements" are such a pain in the rear.
     
  7. initialsBB thread starter macrumors 6502a

    Joined:
    Oct 18, 2010
    #7
    Just an update:
    After Yosemite and Server 4 update I was still having this problem so I went through all the configurations again. I found that the SMB bug was due to a config error on my part, there was some sort of contradiction between user access rights, group access rights, and storage permissions.
    I can now leave AFP & SMB sharing on and not get any Finder errors when copying. My Mac defaults to SMB without any issue.
    Lesson learnt. When creating networks and servers, next time I'll draw a diagram of the needs before hand.
    And Mea Culpa to Apple.
     

Share This Page