Hello Byron, the answer to all your questions of course is THE CLOUD :)
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). 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/ > 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. > - 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. > 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. 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
