<p dir="ltr">Ah. So use cifs. </p>
<div class="gmail_quote">On Aug 25, 2014 10:51 AM, "Lightner, Jeff" <<a href="mailto:JLightner@dsservices.com">JLightner@dsservices.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Just to re-iterate:<br>
The shares are being done by NAS dedupe appliances and I'm trying to mount the shares on the Windows 2008 R2 system. (i.e. the Windows system is the client mounting the shares not the server exporting them).<br>
<br>
There is no control over the NAS appliances other than to create shares as either NFS or CIFS so iSCSI is not an option.<br>
<br>
<br>
-----Original Message-----<br>
From: <a href="mailto:ale-bounces@ale.org">ale-bounces@ale.org</a> [mailto:<a href="mailto:ale-bounces@ale.org">ale-bounces@ale.org</a>] On Behalf Of Justin Goldberg<br>
Sent: Monday, August 25, 2014 9:51 AM<br>
To: Atlanta Linux Enthusiasts<br>
Subject: Re: [ale] Automatic and Persistent share mount on Windows 2008 R2?<br>
<br>
Another option is installing the Windows builtin iSCSI target and mounting it from Linux, then have the Linux machine, acting as the frontend, share out the box on the network. iSCSI is a one-to-one protocol and is block-level, one machine to another, mounting the drive on a lower level than SMB. It would obviate the need to mess around with Windows authentication, or at least that's my hope. Perhaps it would work better if the Windows server is in workgroup mode.<br>
<br>
- Justin<br>
<br>
On Fri, Aug 22, 2014 at 5:29 PM, Lightner, Jeff <<a href="mailto:JLightner@dsservices.com">JLightner@dsservices.com</a>><br>
wrote:<br>
<br>
> I have two data deduplication devices that do NAS style shares. They can<br>
> do NFS or CIFS (or both at same time using different shares). The NFS<br>
> shares have been there for quite some time and I successfully mount<br>
> those to various HP-UX and Linux servers with no issue.<br>
><br>
> We need to try to mount to a Windows 2008 R2 server. Today I got as far<br>
> as being able to login to the Windows server and map the share to a<br>
> drive letter then verify I could read and write from it.<br>
><br>
> The issue is that CIFS mount:<br>
><br>
> a) Is only available to the user I logged in as when I did the map on<br>
> the Windows side. (This was also true when I had the Windows Admin do it<br>
> using the domain administrative account.)<br>
><br>
> b) Is not available to the services that were already started<br>
> automatically at boot. It is these services that will be writing to and<br>
> reading from the drive.<br>
><br>
> So my question is how can I setup an automatic mount of a share in<br>
> Windows at boot AND insure that services started will have access to<br>
> read and write to it?<br>
><br>
> We did in fact try to enable NFS Services on the Windows server today<br>
> but for whatever reason it puked on doing that each time and forced a reboot.<br>
> If someone knows how to enable that on Windows 2008 R2 as well as<br>
> how to make a mount there persistent (similar to the way it would be<br>
> if in fstab on UNIX/Linux) I'd be happy to go that route instead.<br>
><br>
> Please don't point me at links that "might address" this if you<br>
> haven't already tried them and know they work. After working most of<br>
> the week on this I've not found anything that really solves it in many web searches.<br>
><br>
><br>
><br>
><br>
> Athena(R), Created for the Cause(tm)<br>
><br>
> Making a Difference in the Fight Against Breast Cancer<br>
><br>
> _________________________________________________________<br>
><br>
> CONFIDENTIALITY NOTICE: This e-mail may contain privileged<br>
><br>
> or confidential information and is for the sole use of the intended<br>
><br>
> recipient(s). If you are not the intended recipient, any disclosure,<br>
><br>
> copying, distribution, or use of the contents of this information<br>
><br>
> is prohibited and may be unlawful. If you have received this<br>
> electronic<br>
><br>
> transmission in error, please reply immediately to the sender that<br>
><br>
> you have received the message in error, and delete it. Thank you.<br>
> -------------- next part -------------- An HTML attachment was<br>
> scrubbed...<br>
> URL: <<br>
> <a href="http://mail.ale.org/pipermail/ale/attachments/20140822/a6fab4d2/attach" target="_blank">http://mail.ale.org/pipermail/ale/attachments/20140822/a6fab4d2/attach</a><br>
> ment.html<br>
> ><br>
> _______________________________________________<br>
> Ale mailing list<br>
> <a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
> <a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
> See JOBS, ANNOUNCE and SCHOOLS lists at<br>
> <a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <<a href="http://mail.ale.org/pipermail/ale/attachments/20140825/d1ec8ad4/attachment.html" target="_blank">http://mail.ale.org/pipermail/ale/attachments/20140825/d1ec8ad4/attachment.html</a>><br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
<br>
_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
See JOBS, ANNOUNCE and SCHOOLS lists at<br>
<a href="http://mail.ale.org/mailman/listinfo" target="_blank">http://mail.ale.org/mailman/listinfo</a><br>
</blockquote></div>