Network drive volume name for same folder by multiple users

Question

I am using a 1TB USB hard disk attached to a ASUS RT-AC68U wireless router as network drive.  There are multiple user accounts created on the same MacBook Air and they need to access the same folders on the network drive.  For example, we have folder called "iTunes" created on the network drive.
The following steps resulted in some problems encountered.
Step 1: When user1 mounts the iTunes folder as a network drive, the general info shows:
General:
  Kind: Volume
  Server: smb://rt-ac68u/iTunes
Name & Extensions:
  iTunes
Step 2: When user2 mounts the same iTunes folder as a network drive, the general info shows:
General:
  Kind: Volume
  Server: smb://rt-ac68u/iTunes
Name & Extensions:
iTunes-1
Question: Why does OS X assign "iTunes-1" as the name of the same network folder on the network drive for user2?  Is there a way to retain the same original folder name for user1 and user2, such as "iTunes", so that it can be access as "/Volumes/iTunes" by both these users? 

Answer 1

tastyrico wrote:
Hi Drew,
Thanks for the recommendations.  They are useful tips to have in the arsenal, thanks.  However, the preferences discussed are intended for directly attached external hard disks and the specific discussion was to make it available to the network on a Mac that is powered up with no user logged in (like a OS X Server but user still need to log in).
That's correct, I'm sorry I am wrong.
I do remember another defaults write option for detaching network drives on 'switch to loginwindow' because I needed the same thing - eventually I gave up & disabled fast user switching, it reduced the amount of issues for the clients. Sorry for confusing the two.
Have you considered mounting it via a startup script. At the moment it is failing because the path exists when User2 mounts it. If you try a script (at the level of the system) it should mount only once. Obviously sticking usernames & passwords into a script is not the best for security.
I think this issue is what NFS mounts can overcome, but I haven't used them for so long. They should be able to mount with no user interaction, but they are less flexible with permissions IIRC.
If your NAS supports NFS look at that, I think you both need to remove the user as the agent that mounts the disk. If the OS does it once (& permissions are correct) it should remove the 'diskname-1' issue.
When it works you end up with volumes in /Network/diskname.
I don't have a good place to start with NFS, so take a look around here…
https://discussions.apple.com/thread/4144999
@ElisabethBraut, do you get this error form MS…
http://support.microsoft.com/kb/2712085
MS apps fall apart when you have disks mounted like this, it's a consequence of MS apps using an older way to represent filepaths.