Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NFS client mount not persistent

Status
Not open for further replies.

mdwsgl

IS-IT--Management
Nov 15, 2004
10
US
Howdy folks!
Referencing this thread which was closed without a response: thread90-1119984 (Not a lot of responses to these NFS queries, are there?)
I'm trying to do exactly the same thing allbymyself was attempting with NFS volumes, hopefully keep the mapping available as a "service" in Windows Server 2003 R2, SP2. Once the volume is accessible via a hard or soft mount, a UNC path is allowed to access it, which would be preferable.
There are a lot of details on both the UNIX and Windows ends which I'm intentionally leaving out. Suffice it to say I can mount the volume anonymously only, and can only write under the root folder of the volume, not directly to it.
Has anyone had any success resolving a similar problem?
Thanks,
mdwsgl
 
it is almost different net-mount strategy between Unix and Windows (client speaking).

In unix a "mount" is done by root (also the CD on a WorkStation). Once mounted, all users (unix borns multi-users) see the volume, respecting the permissions.

Windows borns mono user, and many things remain at this level. The command "net use" is for user (anyone can use them, and the result depends from permission: the system can ask autentication on the fly). The net use has the flag
of "persistent" : this means that when you re-login the system re-mount (re net use) the share.

What you can try, is to run a service that perform a net use
(or what has to do using SFU), but remember thet the permissions are that for the user of the service, and is your load to unprotect or share them to match the ones of the common users.

ciao
vittorio

 
victorv,
Thanks very much for your reply. We got around this issue using CIFS, primarily because of the lack of confidence between Windows and UNIX authentication in an environment where there is no MSADS and no UNIX name server (such as a DMZ). CIFS works fine whether or not a user is logged into the Windows server, using pass-through authentication with permissions at the "share level" on a NetApp device, again with a local user account on the Windows box. Elegant enough that it works, despite the CIFS license.
NFS Unix to Windows interoperability is not quite there yet.

Thanks again, and Merry Christmas!
-mdwsgl
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top