View Full Version : mapped drive issue

Jul 29, 2011, 09:22 AM

I have an issue that may be unique, I'm not sure.

Here is what I have noticed in Lion:

When I Connect to Server with an address such as the following: smb://Server1/Share2/Subfolder3 that Lion puts Share2 in the finder. I'm fairly sure it didn't work that way in Snow Leopard. I remember it putting Subfolder3 as the mapped drive in Finder.

In most situations this is just annoying because if you are wanting to save something in the particular folder you had originally mapped, you now have to fish through your share to find the folder.

I have a situation that is a little different. On our network we have a home$ share that has everyone's home drive in the company. People don't have read ability on the home$ share because they don't need to know who has a home drive nor see any files that are located there. For them to access it, they have to go directly to their specific home drive. Now, when you map smb://server/home$/user it opens up their user folder initially but as I mentioned above only home$ will show in finder. When a user tries to go through finder to navigate to their folder (or save something) they can't because they get an error when they click on home$ that they don't have permissions. Windows users do not have this problem. Snow Leopard users do not have this problem. No one does but those who have upgraded to Lion. The only way to even view the home drive is to look at it through Terminal or use Go to Folder and type in /home$/user after mapping. This work ok for wanting to view or open items, but fails when you want to save something.

At this point, we don't want to change anything on the servers. How can I get around this in Lion? Can I create an alias somehow to this share than you can access? If so, how? I don't know how to make an alias in this situation. It doesn't show this folder anywhere in Finder to be able to drag it anywhere.

Any help will be very appreciated.


Aug 4, 2011, 12:11 PM
I called apple support on this. Is seems to be limited to the share being on a windows server. He duplicated the issue and confirmed it to be a bug. He said hopefully a patch will be released soon.

Just thought I'd let anyone know who might be looking to resolve this issue

Nov 3, 2011, 01:55 PM
Prior to Mac OS Lion, we were using Snow Leopard for Windows file sharing with no problems. The Windows clients have drive mapping for 1 or more shares, including user directories on the Mac OS Server. The clients regularly sync with the server using Windows Offline Files.
After moving to Lion, the Windows clients all show warnings that they are "No longer connected to the server", but this is actually not true. If you double-click on one of the share icons in My Computer, the share opens with no problems. It appears that somehow Lion broke something that was previously working fine. Calls to Apple Support yielded very little, and often come to a screeching halt once the words Windows XP or Windows 7 are mentioned.
I don't expect Apple to support the Windows products on our network (that's my job), but why did they have to break something that was previously working perfectly, and was also saving us oodles of $$$ in support/maintenance/headaches over the competing Windows Server products.
For the record: We have 35+ iMacs/MacMinis running a mixture of WinXP and Win7; 8 MacOS Servers (the clients must use Internet Explorer to access certain mission-critical data, but the iMacs look great on the showroom floor next to all the luxury autos. Now everyone wants an "Apple Computer" on their desk!).
Unfortunately, if this doesn't get sorted soon I fear we will begin the painful road down to Windows Server products (gag).