From owner-freebsd-hackers Thu Jan 19 20:18:44 1995 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.9/8.6.6) id UAA28046 for hackers-outgoing; Thu, 19 Jan 1995 20:18:44 -0800 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.9/8.6.6) with SMTP id UAA28035 for ; Thu, 19 Jan 1995 20:18:38 -0800 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA10071; Thu, 19 Jan 95 21:12:45 MST From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9501200412.AA10071@cs.weber.edu> Subject: Re: NETBEUI for FreeBSD? Any docs? To: jkh@time.cdrom.com (Jordan K. Hubbard) Date: Thu, 19 Jan 95 21:12:44 MST Cc: roberto@blaise.ibp.fr, osyjm@schizo.coe.montana.edu, hackers@FreeBSD.org In-Reply-To: <4125.790548958@time.cdrom.com> from "Jordan K. Hubbard" at Jan 19, 95 12:55:58 pm X-Mailer: ELM [version 2.4dev PL52] Sender: hackers-owner@FreeBSD.org Precedence: bulk > My problem with SAMBA is that it's not a DOS solution, just a Windows > solution. I need both. Any suggestions? :) LANMAN under DOS using a TCP/IP transport can use Samba. As can the Artisoft Lantastic DOS client, which can talk SMB. AT&T LanManager also does this, as does DEC's PathWorks products. The default protocol for both of the former is NetBEUI. The default for both of the latter is proprietary (AT&T StarLan and DECNet Phase IV, respectively). Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.