Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Click here to return to the 'One way to make 'hidden' SMB shares reappear' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
One way to make 'hidden' SMB shares reappear
Authored by: mm2270 on Aug 15, '07 06:58:26AM
How interesting this would be posted today, when just yesterday I ran across something similar involving AFP shares.

We had an issue that would pop up from time to time that was bugging us here at work, where an AFP share would have difficulty mounting. Usually an error stating it couldn't mount the volume or something similar would pop up.
Afterwards, we noticed that mounting this volume would result in the volume showing up as "share_name-1". This would cause issues when using certain applications, like Capture One, which uses absolute paths. The links to session files would end up broken when using Capture One on any Mac having this share-1 issue.

I discovered by poking around in the terminal that the system apparently created some invisible temp directory in the location /Volumes that would stay there, even after reboots, and had the name of the share. Because of this the OS had no choice but to append the -1 to the end of the name of the actual share when it mounted in the Finder.

The fix was to actually do an rm -R on the offending file. Before doing this, I completely disconnected the affected Mac from the network, just to be sure it wasn't reading some actual network share. Even with it disconnected, it would show in /Volumes, so it was definitely a local file. After removing it, the actual AFP share would then show up with its proper name.

I know this hint is based on a slightly different issue, but it seems somehow related to how Mac OS X is mounting shares. Must be some kind of bug in how Tiger mounts volumes that causes this issue, and the one this hint is about.

[ Reply to This | # ]
One way to make 'hidden' SMB shares reappear
Authored by: JimMueller on Aug 16, '07 01:28:55PM

You are the only other person I have seen mention the sharename-1 behaviour, and I have searched many online resources and asked about it several times with no acknowledgment. We get it in a different situation - if another user on the FUS-enabled Mac has a share on another mac mounted, then when you mount the same share it appears with a -1 after the sharename. Not much of a problem except they both appear in the sidebar in the Finder and file open/save dialogue. Aliases to folders and files on this share often get confused and sometimes cannot find the file or open the folder with nothing appearing in it.
Not really pertinent to this discussion, but I was happy to see it happened to someone else too.

[ Reply to This | # ]