Xref: utzoo comp.windows.ms:6492 comp.dcom.lans:6267 Path: utzoo!attcan!uunet!know!sdd.hp.com!uakari.primate.wisc.edu!uflorida!ziggy!screamer!tscs!tct!chip From: chip@tct.uucp (Chip Salzenberg) Newsgroups: comp.windows.ms,comp.dcom.lans Subject: Networking Windows with Unix: NFS or SMB? Message-ID: <272306AE.4A46@tct.uucp> Date: 22 Oct 90 14:48:13 GMT Organization: Teltronics/TCT, Sarasota, FL Lines: 32 An associate of mine is working on setting up an Ethernet network with a 386 Unix server and DOS machines running Windows 3.0 as clients. server. However, he hasn't decided which network software to use. I'd like to help him out. In addition, I'm looking for info we can use here at TCT. We have SCO Unix; he hasn't decided on a Unix, so he can choose the Unix variant based on availability of network software. Possible solution #1: I understand that FTP's NFS and Sun's PC-NFS will work with Windows 3.0; if not, please let us know! Then the NFS support for Unix can be purchased from the Unix vendor. Possible solution #2: I would expect that Microsoft's Lan Manager for DOS would work with Windows 3.0. (Assuming it's available, that is.) But from whom can we get Lan Manager/X for Unix/386? Is it even available yet? Possible solution #3: I once heard -- though it was not confirmed -- that Windows includes SMB (Server Message Block) protocol support. If true, this feature eliminates the need for Lan Manager client software. Of course, we would still need Lan Manager/X on the server. As a variation on this theme, could Windows 3.0 talk to a Xenix-Net server? Any information on the practicality of these solutions would be greatly appreciated. Please reply to an address in my signature. -- Chip Salzenberg at Teltronics/TCT , "I've been cranky ever since my comp.unix.wizards was removed by that evil Chip Salzenberg." -- John F. Haugh II