<div class="gmail_quote"><div>A VPN link didn't do it for you? If not, why wouldn't this work? What have you tried?</div><div><br></div><div>From the needs/scenario you've outlined and to maintain some level of security, there's going to be significant overhead for which you must consider. </div>
<div><br></div><div>Networks that you don't control can sometimes goof 'just because they can'. </div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Message: 3<br>
Date: Wed, 22 Jun 2011 12:54:34 -0400<br>
From: "Michael B. Trausch" <<a href="mailto:mike@trausch.us">mike@trausch.us</a>><br>
Subject: [ale] File systems for hetergeneous networks?<br>
To: <a href="mailto:ale@ale.org">ale@ale.org</a><br>
Message-ID: <1308761674.3008.3.camel@redpepper><br>
Content-Type: text/plain; charset="UTF-8"<br>
<br>
I keep running into dead ends. Essentially, I'm looking for solutions<br>
that I can use to have both Windows and UNIX clients happily working<br>
side-by-side without having to worry about problems.<br>
<br>
Essentially, I want to support network configurations (possibly<br>
distributed over a WAN, though that will be more or less transparent<br>
since the over-the-WAN interconnections are routed IP networks) where I<br>
can have the following things:<br>
<br>
* LDAP replicated such that each network has its own copy of<br>
authentication data.<br>
* Kerberos such that passwords don't need to be re-entered time<br>
and time again.<br>
* Networked filesystems, preferably with client caching mechanisms,<br>
such that things aren't slow as lead even over a WAN link. That<br>
said, reliability and things like file locking should not be<br>
sacrificed.<br>
<br>
I am beginning to think that this is simply too much to ask. Is it?<br>
<br>
--- Mike<br></blockquote></div>