If you are familiar with connecting via Linux via
/etc/fstab, then you know there are a lot of possibilities of what could go wrong simply because there are SO many different options for connecting to different types of network shares, and it seems like every OS handles these options differently.
I have encountered issues similar to this before, and in my cases, it was always either an issue with ownership/permissions and/or the specific mount point (or a combination of the two):
For instance, I have a ZFS pool setup using FreeNAS, and the mount point is set to
//x.x.x.x/share, and the login credentials are supposed to be for a specific user. I have no trouble connecting to it in Windows, but the only way I can connect to it in OS X is to connect directly to the IP using the root credentials. I know there is a way to fix it, but I haven't gotten around to looking into it yet.
So my first advice would be to try connecting directly to
smb://x.x.x.x/share, or any other variations that you can think of, using various sets of credentials that have access to that box.
It could also be a Samba version issue (which Samba is notorious for) that could be causing these 2 guys to not agree with each other.
Also, sometimes in OS X if I am trying to mount a share with one of the various
mount commands in Terminal, I find that it tends to give me trouble sometimes if mounting with my normal user, so in certain circumstances, I need to use
sudo in order to mount it as root.
If all else fails, I would try installing the Netatalk packages on your Raspberry Pi. Netatalk is an open source version of the Apple Filesharing Protocol (AFP), which OS X obviously tends to handle much better than Samba (SMB). If you enable the share to also use AFP, you can connect to it from Finder using
If you are running Raspbian, those packages should be available via
apt-get. I hope this helps!