cannot browse "nested" SMB shares

benscant · 08-10-2005, 11:59 PM

Hi,
Had a fish around in the hints (best mac support resource on the www, btw! thanks, have helped me out of innumerable pickles!!), but couldnt find a fix:
macs (10.3.?) in windows environment, can connect to shares on a Netapp filer, but cannot browse nested folders - i.e. can connect to //server/share, but cannot see //server/<share>/share. It appears that this is probably a permissions issue in AD or on the netapp, Some accts, e.g. mine, can browse ths folder ok, i have rights to the intermediate folder, but I cant map directly to //server/<share>/share. It mounts //server/share as a network vol (icon on the desktop, then opens .../share in a finder window. Now I have searched everywhere on the web, and no-one has any instructions for mounting a nested smb share directly. All the articles make out that connecting to smb://server/share is like this amazing piece of wizardry, and that the savages in wintel and/or creative land should impressed by this. Yeah, I was impressed when I first saw this in earlier OSX versions many moons ago, but now "big smb stick go bang" is kinda not doing what I want it to do. Any ideas? Thanks in advance.

Raven · 08-11-2005, 08:34 AM

If I were you I woudl start by asking the AD admins if they are using DFS on the shared drives. This file system is used by MS so that the original files themselves can be moved around without the having to change the "official" path to files. This is incompatible with the version of samba currently being used on Mac OS and would prevent you from seeing those shares. And in your case, since it works when you put in a full path, it may simply be that this is the issue as your Mac will not see the DFS paths.

08-10-2005, 11:59 PM	#1
benscant Prospect Join Date: Aug 2005 Posts: 2	cannot browse "nested" SMB shares Hi, Had a fish around in the hints (best mac support resource on the www, btw! thanks, have helped me out of innumerable pickles!!), but couldnt find a fix: macs (10.3.?) in windows environment, can connect to shares on a Netapp filer, but cannot browse nested folders - i.e. can connect to //server/share, but cannot see //server/<share>/share. It appears that this is probably a permissions issue in AD or on the netapp, Some accts, e.g. mine, can browse ths folder ok, i have rights to the intermediate folder, but I cant map directly to //server/<share>/share. It mounts //server/share as a network vol (icon on the desktop, then opens .../share in a finder window. Now I have searched everywhere on the web, and no-one has any instructions for mounting a nested smb share directly. All the articles make out that connecting to smb://server/share is like this amazing piece of wizardry, and that the savages in wintel and/or creative land should impressed by this. Yeah, I was impressed when I first saw this in earlier OSX versions many moons ago, but now "big smb stick go bang" is kinda not doing what I want it to do. Any ideas? Thanks in advance.

08-11-2005, 08:34 AM	#2
Raven Hall of Famer Join Date: Jul 2003 Location: Montreal Posts: 4,782	If I were you I woudl start by asking the AD admins if they are using DFS on the shared drives. This file system is used by MS so that the original files themselves can be moved around without the having to change the "official" path to files. This is incompatible with the version of samba currently being used on Mac OS and would prevent you from seeing those shares. And in your case, since it works when you put in a full path, it may simply be that this is the issue as your Mac will not see the DFS paths. __________________ Waffled foreheads are a symptom of broken keyboards and inexperienced users

Thread Tools
Show Printable Version Email this Page
Display Modes	Rate This Thread
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode	Rate This Thread: