On Sun, Dec 15, 2013, at 5:01, Marcus MERIGHI wrote: > Hello Byron, > > the answer to all your questions of course is THE CLOUD :)
I prefer to solve problems on THE GROUND :) > Am 12/15/13 07:56, schrieb Byron Klippert: > > I'm looking at options for sharing machine resources > > (drives/directories/files) over LAN between OpenBSD server and Windows7 > > clients. > > Welcome to my world ;-) > > > The Windows7 clients already belong to a corporate domain system, and my > > lack of experience with Samba is telling me not to converge the two. > > See below. If you find a way to accomplish this PLEASE let me know! > > > My first choice is NFS, but... Windows7 Pro 64-bit doesn't seem to have > > a NFS client built-in. > > There used to be one IIRC. Have you tried sysctl -> programms -> > add/remove windows components (do not take these labels literally as I > usually see them in german). Again, Windows7 Pro 64-bit doesn't offer this option. And I've tried the MS Unix supplements with no success - instead wasted several hours I'll never get back. At least you know that time spent digging into issues on OpenBSD usually pays off (insight, knowledge, experience) but with MS its usually just a %!@$ing waste of time. > If you cannot find it there go search for "resource kit" on the > microsoft website. Good luck, you might need it :-) > > > All the alternatives I've tried cost money or suck (or both). > > IIRC there used to be something called sshfs for windows which was said > not to suck. > Just found: http://dokan-dev.net/en/download/ Tried this dokan/nekodrive thing but my conclusion is it's no where near production ready. Doesn't appear to be very active development. > > Questions to the list... > > > > - what, besides ftp/http can I use to get as close to a "shared" disk > > over LAN? > > webdav should work natively on recent (> win98) microsoft systems. But > actually this falls in the "http" category. This has been recommended off-list (thanks Patrick) and is looking like an option at this point. > > - can I share a drive using Samba without interfering with the existing > > domain system? > > Windows clients will use their logon credentials for connecting to > network shares by default. Thusly, if you manage to have the same > usernames/passwords in your samba password database (OpenBSD machine) it > could work. This will be a maintainance nightmare (user changes password > for domain -> access to share fails). > > On the other hand you can have a domain logon script that connects each > client to the same ressource (e.g. \\openbsd-server\public) with the > same username/password. This is a security nightmare (who the hell > deleted that file?). > > Integrating your OpenBSD/samba system into microsoft active directory > will provide some challanges (hint: nsswitch, winbind(d), ads vs. ldap, > kerberos). What I collected recently: > > http://serverfault.com/questions/20202/authenticating-openbsd-against-active-directory > https://lists.samba.org/archive/samba/2004-June/087764.html > https://wiki.samba.org/index.php/Samba_%26_Active_Directory > https://wiki.samba.org/index.php/Samba,_Active_Directory_%26_LDAP > > I for myself haven't come to a conclusion yet on which way to waste my > time most uselessly. I'm not the admin for the domain side so this would be a challenge. Plus these efforts should really be under the radar. :) > > The LAN I'm running the OpenBSD server on is a different subnet and > > accessed over WiFi. The Windows7 clients access the domain over > > Ethernet. > > Sounds weird for a fileserver to have it on the slow wireless. SMB uses > broadcasts but works without so I would not get scared by the need to > route the traffic between subnets. Most clients have only x1 ethernet and x1 wifi... don't really have the option to change the topology. > I have seen lots of strange things happen when real world microsoft > windows applications open files on network shares. Some need write > permissions on parent directories to create .lock files etc. Do early > testing no matter which route you go! > > Bye, Marcus -- Byron Klippert byronklipp...@ml1.net c. 867-336-1306
