You are correct, Alan; this works fine. Thanks for the good pointer.
Mark Muhlestein -- mmm@netapp.com
-----Original Message----- From: Allan Burrington allan@mirapoint.com To: Keith Brown keith@netapp.com; Alexander Strauss strauss@ti.com; toasters@mathworks.com toasters@mathworks.com Date: Thursday, March 11, 1999 11:48 AM Subject: Re: CIFS share access?
Assuming the filer can handle standard PC functionality - you can use
subst
to map any path to a drive letter.
Target has share: C$ Within the C$ share is a directory named 'foo'.
Do: subst z: \target\c$\foo
You now have z: rooted at the foo directory.
-A
----- Original Message ----- From: Keith Brown keith@netapp.com To: Alexander Strauss strauss@ti.com; toasters@mathworks.com Sent: Thursday, March 11, 1999 10:27 AM Subject: Re: CIFS share access?
I shared the directory where most of our Unix-Homes are located under the CIFS sharename UNIX_HOMES. There's no problem to connect \filer\unix_homes, but I cannot connect directly to a sub-directory, i.e. \filer\unix_homes\alex.
As has already been stated, the cifs.home_dir option of Data ONTAP might provide you with the functionality that you are looking for.
However... I suspect that you *might* be under the impression that CIFS
shares
are supposed to work like NFS exports in the above respect. Alas they
don't.
As you probably know, if you export "/home/keith" via NFS, it makes it
possible
to directly mount any subdirectory of "/home/keith" from an NFS client
(e.g.
"/home/keith/docs/cifs" or somesuch). Shares aren't like that. If you
share
"/home/keith" as "KEITHDIR", all that you can connect to from a CIFS
client
is
"\FILERNAME\KEITHDIR". You can't do something like a:
net use q: \FILERNAME\KEITHDIR\docs\cifs
Keith
-
Mark Muhlestein