SMB Share with Leopard

Discussion in 'macOS' started by SDAVE, Dec 12, 2007.

  1. SDAVE macrumors 68040


    Jun 16, 2007
    I shared a drive (SMB) from OSX so a Windows machine can see it. All works fine except that from the Windows side, I cannot write any files to it. It says "Access denied". I can read without any problems.

    Under sharing in OSX, I enabled SMB & Read&Write for all the users for that drive.

    This is with Leopard 10.5.1
  2. SDAVE thread starter macrumors 68040


    Jun 16, 2007
  3. QuarterSwede macrumors G3


    Oct 1, 2005
    Colorado Springs, CO
    My wife's Windows box died (thankfully) so I can't help you. If I recall I had that problem a while back though. I'd Google search it.
  4. sejones macrumors newbie

    Dec 18, 2007
    When you connect from the windows side, does it even prompt you for a password? I'm running into a similar issue and it doesn't prompt. It just opens the share and I'm wondering if that's the problem.
  5. pitt1717 macrumors 6502

    Jul 13, 2007
    just a shot here but did you create a user account for the windows user. i share smb through linux. i believe the commands are the same though.

    in terminal type
    smbpasswd -a (user name on windows machine)

    then will prompt for password, i use the same password as what my user does on the windows box
  6. ScoobyMcDoo macrumors 65816

    Nov 26, 2007
    Austin, TX
    As I recall, when I finally go the SMB sharing to work right, I had to make sure that I setup a windows workgroup name on both computers that matched. After that all went smooth - got all my data copied from my windoze box, turned it off and have never powered it up since ;)
  7. nmonkee macrumors newbie

    Apr 8, 2008
    can't write to NTFS SMB shares - WORKAROUND/SOLUTION

    I have an issue with OSX Leopard (10.5.2) , where by I can't write to NTFS shares on W2K3 servers with SMB signing turned on and IPV6 disabled for the interface.

    To recreate the issue:

    Create a folder named test that contains two files one named ._test.txt and test.txt on OSX and copy to an SMB share on W2k3.

    This results in spurious errors about permissions and locked files.

    Copying a file larger than 4k results in the error:

    "The operation cannot be completed because you do not have sufficient privileges or some of the items."

    Using mount_smbfs from a shell on OSX results in the error: "Permission denied"

    host:~ user$ mount_smbfs //user@server/share /Volumes/test-smbmount/
    host:~ user$ cp test.docx /Volumes/test-smbmount/
    cp: /Volumes/test-smbmount/test.docx: Permission denied

    Using smbclient from a shell on OSX results in SUCCESS!!!

    host:~ user$ smbclient \\\\server\\\share -U user
    Domain=DOMAIN OS=Windows Server 2003 3790 Service Pack 2 Server=http://Windows Server 2003 5.2
    smb: \> put test.docx
    putting file test.docx as \test.docx (784.7 kb/s) (average 784.7 kb/s)
    smb: \>

    There is an alternative solution if you do need to drag and drop in your gui world, it'll cost you $120


    I have mailed the developer as he has obviously identified the root problem of the issue and I urged him to share his patch/resolution with Apple in the interests of the user community and a darn nice thing to do.I had a response form the developer to my request. I sent my workaround solution to the developer and stated that in my opinion the pricing for the software seems unnecessarily high based on the functionality it provides and way above what I would be willing to pay to resolve one small issue.

    <developers response>

    Pricing is a difficult topic to discuss -- but if you have no use for the product, any price is too much. As for reporting bugs to Apple, they'll listen to customers much sooner than they'll listen to developers. And they have some of the brightest engineers I know. If you report the bug to them, they'll likely have it fixed in the next update.

    </developers response>

    I couldn't find away to report the bug myself so I had a friend do it for me. The response I had back from Apple was less than satisfactory.

    They believe that the issue is to do with NTFS streams and that a file containing "" needs to be created and placed into the root of shared volumes. This is not a fix!

    If you want to prevent writing the "Apple Double" files to a remote share, enter the following into a terminal:

    $ defaults write DSDontWriteNetworkStores true

    Problem still exists.


    <apple double description>

    ref: f

    Before Mac OS X, the Mac OS used 'forked' files, which have two components: a data fork and a resource fork. The Mac OS Standard (HFS) and Mac OS Extended (HFS Plus) disk formats support forked files. When you move these types of files to other disk formats, the resource fork can be lost.

    With Mac OS X, there is a mechanism called "Apple Double" that allows the system to work with disk formats that do not have a forked file feature, such as remote NFS, SMB, WebDAV directories, or local UFS volumes. Apple Double does this by converting the file into two separate files. The first new file keeps the original name and contains the data fork of the original file. The second new file has the name of the original file prefixed by a "._ " and contains the resource fork of the original file. If you see both files, the ._ file can be safely ignored. Sometimes when deleting a file, the ._ component will not be deleted. If this occurs you can safely delete the ._ file.

    </apple double description>

    I am not the only one this issue. A quick peruse on will show that numerous people are suffering and numerous workarounds have been suggested. Sadly none of which work for me. Each work around is stranger than the previous. Such as disabling IPV6 and updating Daylight Savings Time.

    The issue lies with the samba integration. I am primarily a Gentoo Linux user and this kind of bug would have been resolved almost instantly if present in open source software.
  8. nmonkee macrumors newbie

    Apr 8, 2008
    OSX Leopard (10.5.2) cannot write to remote windows SMB shares if SMB signing is enab

    OSX Leopard (10.5.2) cannot write to remote windows SMB shares if SMB signing is enabled.

    Ok so more and more in depth googling has shown that tons of people are experiencing the same issue. The 'fixes' and workarounds that people have suggested, tried and in some cases had some success with baffle.

    * turn off IPv6
    * enable SMB file sharing and assign READ/WRITE for EVERYONE
    * re-install Leopard
    * delete all credentials in the Key Chain
    * add and remove the machine from the domain
    * delete and re-create network service profiles
    * delete and re-create shared folders on the server
    * change computer name, NetBIOS name, DNS entries
    * the list goes on and on...

    The only way I can find that will allow OSX Leopard 10.5.2 clients to mount, read and write to remote SMB shares on W2K3 servers is.....

    Turn off SMB signing. Apple have borked their implementation.


    Windows SMB Packet Signing
    Enjoy improved compatibility and security with Windows-based servers.

    To disable SMB signing:

    Open Default Domain Controller Security Settings.
    Go to Security Settings, Local Policies, security Options.

    Disable the following:

    Domain member: Digitaly encrypt or sign secure Channel Data (Always)
    Microsoft network server: Digitally sign communications (Always)
    Microsoft network server: Digitally sign communications (If client agrees)

    To refresh the policy:

    from a command prompt run gpupdate

    now OSX Leopard 10.5.2 clients can mount, read and write to remote SMB shares on W2K3 servers.

    ** Good luck convincing your domain admins to downgrade their enterpise security for OSX users. **

Share This Page