Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!zombie.ncsc.mil!news.mathworks.com!gatech!swrinde!cam.news.pipex.net!pipex!edi.news.pipex.net!pipex!demon!not-for-mail
From: Andrew Gordon <andrew.gordon@net-tel.co.uk>
Newsgroups: comp.unix.bsd.freebsd.misc
Subject: Re: Hooking FBSD2+ machine to a DOS network
Date: Sun, 02 Jul 1995 00:32:35 GMT
Lines: 36
Message-ID: <804645155.18948@imp.demon.co.uk>
References: <3t4cib$64@uuneo.neosoft.com>
NNTP-Posting-Host: pencotts.demon.co.uk
X-NNTP-Posting-Host: pencotts.demon.co.uk
X-Mailer: Mozilla 1.1N (X11; I; BSD/386 uname failed)
MIME-Version: 1.0
X-URL: news:3t4cib$64@uuneo.neosoft.com
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=us-ascii
jkurtz@starbase.neosoft.com (John Kurtz) wrote:
>Has anyone successfully connected a FreeBSD 2.x machine to a network of MSDOS
>machines and been able to login to the FBSD box from a DOS box? Information
>on whether this is possible and, if anyone has done it, recommendable network
>cards and system configurations needed would be majorly helpful.
Certainly it is possible. Most solutions involve running TCP/IP on the DOS
machines. You have a choice of where you get the TCP software for the DOS box,
and a choice of which higher layer protocol you run if you want to use the
FreeBSD machine as a fileserver.
I have used the following different setups:
1) Sun PC-NFS ver 5.1 on the PCs, using NFS as fileserver protocol. PC-NFS
contains a tolerable Telnet for DOS, and an abysmal one for Windows. FreeBSD
is an NFS server out-of-the-box, but requires pcnfsd to be built from the ports
collection (to allow the PCs to authenticate themselves) and requires mountd to
be started with the -n option [that bit always takes me about 10 minutes to
work out why it doesn't work when I set up a new server!].
2) FTP Software Inc. PC-TCP on the PCs, NFS as fileserver protocol. Very much
the same as option 1 - the quality of support applications and selection of
bugs varies between the two, but not much to choose between them
3) Windows for Workgroups 3.11 plus Microsoft TCP/IP32 (available from
ftp.microsoft.com) on the PCs, SMB ("LAN manager") over TCP/IP as the
fileserver protocol. Requires Samba (from the ports collection) installed on
the FreeBSD machine to act as fileserver. The Microsoft TCP/IP includes a
minimalist but functional Telnet; we normally use QVT (downloadable from
somewhere or other) instead.
Option 3, in my experience, works much better than the others - and it costs
less too!