Bizarre Finder behavior with SMB shares in 10.6.x

Discussion in 'macOS' started by jmpage2, Sep 10, 2010.

  1. jmpage2 macrumors 68040


    Sep 14, 2007
    Well, I've been battling this problem off and on since converting to OS X a couple of years ago, but after spending all morning trying to find a solution I figured I would post here to see what others have to say about it.

    I have an iMac running 10.6.4 and I have a WHS that has a series of SMB shares set up on it.

    I have startup items in my account for a variety of the SMB shares (they host things like my iTunes music and so I get problems if they are not mounted immediately when I log in to OS X) and everything seems to work. The shares (usually) get mounted at log in, I can read and write to them and things seem fine. It is worth noting that I use my actual SMB share login/password to log in to the shares and NOT the guest account.

    Until that is I do certain operations in the Finder and then discover problems with the SMB shares.

    For example. I open up the Image Capture application and try to select a bunch of files for import. I try to select my 'Videos' SMB share for a destination but it is grayed out and cannot be selected. Yet my 'Users' share on the same server can be selected. The only difference between these two shares is that 'Users' is not a real WHS share and is instead a parent folder of a couple of actual shares.

    Permissions on WHS allow for full read/write access to ALL the above mentioned shares and I have no issue copying files into them, creating new files, etc, yet clearly there is some bizarre permission thing going on which results in the Finder thinking that, for certain operations, the shares are not read/write capable.

    Does anyone have any insight into this? How can I debug the permissions in OS X to figure out why Finder is being such a PITA with this stuff? I never have problems with these SMB shares with any of my non OS X devices.

    Here's a sample output of the shares I have;

    Jason-Pages-iMac:~ Jason$ df
    Filesystem 512-blocks Used Available Capacity Mounted on
    /dev/disk0s2 1037828096 69303256 968012840 7% /
    devfs 219 219 0 100% /dev
    map -hosts 0 0 0 100% /net
    map auto_home 0 0 0 100% /home
    //Jason@gizmo/Music 2888310280 0 4655150000 0% /Volumes/Music
    //Jason@gizmo/Photos 2888310280 0 4655150000 0% /Volumes/Photos
    //Jason@gizmo/Public 2888310280 0 4655150000 0% /Volumes/Public
    //Jason@gizmo/Software 2888310280 0 4655150000 0% /Volumes/Software
    //Jason@gizmo/Users 2888310280 0 4655150000 0% /Volumes/Users
    //Jason@gizmo/Videos 2888310280 0 4655150000 0% /Volumes/Videos
    //Jason@gizmo/Movies 2888310280 0 4655150000 0% /Volumes/Movies
    /dev/disk1s1 524287920 245848320 278439600 47% /Volumes/iMac Backup on Gizmo
    /dev/disk0s3 211761144 91716992 120044152 44% /Volumes/BOOTCAMP

    Any help is appreciated. I have been battling weird SMB share issues since moving to my Mac and I'd really like to get all of this stuff put away for once and for all.
  2. jmpage2 thread starter macrumors 68040


    Sep 14, 2007
    I'm sure others have run into this before.... would I be better off asking at the Apple support forums?
  3. 4np macrumors 6502a


    Feb 23, 2005
    The Netherlands
    'Finder' has the same rights to those shares as the user account has you use to access them (in your case: Jason). So if 'Jason' has full read and write access, you should be fine.

    Is WHS by any chance "Windows Home Server" or something? I have had extremely annoying experiences with windows shares on windows computers. Even though you give full read and write access to certain folders, others (also on XP machines) were unable to access it... We have never resolved these issues...

    So it might also be that your Windows is acting up... (would not be a surprise of course :p )
  4. jmpage2 thread starter macrumors 68040


    Sep 14, 2007
    Yes, it's Windows Home Server. No longer a big fan of Windows products but WHS is quite good for my uses.

    As I said, I can read and write the shares just fine when doing normal things, but some finder operations show the shares as grayed out and not accessible. It's really quite bizarre.

Share This Page