-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

I understand the way in which homedirs are working on the filer, and I am confident that the permissions are set correctly.

There are really two issues at hand.

#1. Users see their homedir when the list available shares when the connect to the server (Start -> Run -> \filer or using Windows Explorer through Network Neighborhood). The user then looks in the share with their user name, and sees all the files stored in their homedir. They panic thinking that somehow their data is being shared out on the network for everyone to see. They run to me and say, "HELP! There's a share on FILER with my name on it!!!!" and I get to explain this to them amid the many other projects going on. Even the more savvy users come by and ask, "What's up with this?" and I get to explain it once again.. And yes, we'll ignore that this was all explained in an email a week or so ago.

#2. Our local domain will soon be migrated to a resource domain. Users will then log in to the corporate-master-globular-user domain. The filer will stay a memeber of the resource domain, because it _is_ a local resource. and cifs.home_dir does not work across domains. So, spending the time to educate the user community is a wasted effort. :}

I want cifs.home_dir off. I cannot set it to null because that is not a valid pathname. I am almost to the point of creating a volume, pointing cifs.home_dir at it, and then killing the volume. I have concidered killing the CIFS.HOMEDIR share under server manager, but I have this horrible fear that in doing either one I will cause my filer to panic or crash.

Bill

-----Original Message----- From: Uren, Jim [mailto:jim.uren@netapp.com] Sent: Friday, November 19, 1999 6:13 PM To: 'Jones, Bill' Subject: RE: options cift.home_dir question

Hi Bill, I replied to this question via toasters. But I have a further question. If you have time to answer (sounds like you are harrassed and busy) :) I'd like to know a little more about the problem.

When the cifs.home_dir option is set to some legal path, users can have home directories. But each homedir is individual. Suppose your homedir path is /vol/vol0/home. Underneath home there are directories bill and susie.

When bill accesses the filer he will see all the filer's shares and also a share called "bill" that is at /vol/vol0/home/bill. If susie looks at the share list, it will also have all the "real" shares and also a share called susie which is at /vol/vol0/home/susie. But bill doesn't see a share called "susie", and susie doesn't see "bill".

Also, the sysadmin can set the permissions/ACLs on each user's homedir to give them ownership privileges. Then, the user can the security to restrict access to files from others.

So I wonder if your users browse the filer with Explorer or do "net view \filer" from a DOS prompt and see a share with their name and think everyone else sees it too? Jim Uren

...

-----Original Message----- From: Jones, Bill [mailto:Bill_Jones@NAI.com] Sent: Friday, November 19, 1999 5:21 PM To: 'toasters@mathworks.com' Subject: options cift.home_dir question

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

How do I turn it off???

It seemed like a good idea at the time, but now users are concerned that their homedirs are a share for everyone to see. The question load is getting very repetitive and annoying!!!!

Thanks in advance.

Bill

-----BEGIN PGP SIGNATURE----- Version: PGP Personal Privacy 6.5.1

iQA/AwUBODX4t/poFdhjwhvjEQL8pgCfZx9qsvekgCGtS11y79pLADYCvRMAnijQ V88oVOycQszl87SJ2zFwC7F5 =kZjI -----END PGP SIGNATURE-----