[ale] Automatic and Persistent share mount on Windows 2008 R2?

[Lightner, Jeff]

I'm not trying to use Windows as NFS server but rather as client (assuming there isn't a way to get CIFS to be persistent and automatic).   Our issue however was that enabling NFS (which as I read it turns on both server and client) itself was failing.

Does Filezilla on Windows provide an NFS client?   Can it be setup to mount the filesystem persistent and automatic so that it is seen by other services when they start?




-----Original Message-----
From: ale-bounces at ale.org [mailto:ale-bounces at ale.org] On Behalf Of Jim Kinney
Sent: Saturday, August 23, 2014 10:59 PM
To: Atlanta Linux Enthusiasts - Yes! We run Linux!
Subject: Re: [ale] Automatic and Persistent share mount on Windows 2008 R2?

NFS serving from Windows is sort of like a daily enema with broken glass and rubbing alcohol.
Their service is 32-bit so the number of files is limited. But the best part is all the file metadata is in the registry and not in the inodes/blocks.

The client for windows NFS is better but still very much a redheaded stepchild. Filezilla is better.
On Aug 23, 2014 9:50 PM, "Phil Turmel" <philip at turmel.org> wrote:

> On 08/22/2014 05:29 PM, Lightner, Jeff wrote:
>
> > We need to try to mount to a Windows 2008 R2 server.   Today I got as
> > far as being able to login to the Windows server and map the share
> > to a drive letter then verify I could read and write from it.
> >
> > The issue is that CIFS mount:
> >
> > a)      Is only available to the user I logged in as when I did the
> > map on the Windows side.   (This was also true when I had the Windows
> > Admin do it using the domain administrative account.)
> >
> > b)      Is not available to the services that were already started
> > automatically at boot.   It is these services that will be writing to
> > and reading from the drive.
> >
> > So my question is how can I setup an automatic mount of a share in
> > Windows at boot AND insure that services started will have access to
> > read and write to it?
>
> I ran into this some years ago...  If I recall correctly, you can't.
> At least, not for the LOCALSYSTEM account that services are typically
> installed as.  That account doesn't have network access.
>
> If you run the service under a specific user, the service will have
> network access, but only with "\\server\sharename" path syntax, and
> only if you've arranged some form of automatic authentication for that
> user on the target (domain membership, sync'ed passwords, etc).
>
> > We did in fact try to enable NFS Services on the Windows server
> > today but for whatever reason it puked on doing that each time and forced a
> > reboot.    If someone knows how to enable that on Windows 2008 R2 as
> > well as how to make a mount there persistent (similar to the way it
> > would be if in fstab on UNIX/Linux) I’d be happy to go that route
> > instead.
>
> Never tried NFS on Windows.  Just the idea makes me queasy.  Sorry.
>
> > Please don’t point me at links that “might address” this if you
> > haven’t already tried them and know they work.  After working most
> > of the week on this I’ve not found anything that really solves it in
> > many web searches.
>
> I'm not linking anything, as I don't know of any solutions that meet
> your criteria.  Hope you can use the work-around.
>
> Phil
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ale.org/pipermail/ale/attachments/20140823/b2118126/attachment.html>
_______________________________________________
Ale mailing list
Ale at ale.org
http://mail.ale.org/mailman/listinfo/ale
See JOBS, ANNOUNCE and SCHOOLS lists at
http://mail.ale.org/mailman/listinfo

Athena®, Created for the Cause™
Making a Difference in the Fight Against Breast Cancer

__________________________________________________________
CONFIDENTIALITY NOTICE: This e-mail may contain privileged

or confidential information and is for the sole use of the intended

recipient(s). If you are not the intended recipient, any disclosure,

copying, distribution, or use of the contents of this information

is prohibited and may be unlawful. If you have received this electronic

transmission in error, please reply immediately to the sender that

you have received the message in error, and delete it. Thank you