From owner-freebsd-isp Mon Dec 11 13:14:43 2000 From owner-freebsd-isp@FreeBSD.ORG Mon Dec 11 13:14:42 2000 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from cgi.sstar.com (cgi.sstar.com [209.205.176.12]) by hub.freebsd.org (Postfix) with ESMTP id 160F337B400 for ; Mon, 11 Dec 2000 13:14:42 -0800 (PST) Received: from jking (jking.lgc.com [134.132.76.82]) by cgi.sstar.com (8.11.1/8.11.1) with SMTP id eBBLEUl39701 (using TLSv1/SSLv3 with cipher RC4-MD5 (128 bits) verified NO); Mon, 11 Dec 2000 15:14:35 -0600 (CST) (envelope-from jim@jimking.net) Message-ID: <012c01c063b7$5d0ea620$524c8486@jking> From: "Jim King" To: , "Free" References: <3A353F35.55061AAB@tacni.net> Subject: Re: SMB over internet Date: Mon, 11 Dec 2000 15:14:29 -0600 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Tom ONeil" wrote: > Anyone ever allow SMB to be used, either NT or Samba, for a server? I > have a client who wants to share a database with remote employees. > My gut reaction is no, but I don't know the protocol well enough to > detail why it's a bad idea and what alternatives to offer. I've done it with Samba and NT; it works. Of course it's best to do this via a VPN setup. If you can't do that at least tell Samba to use encrypted passwords and make sure the Windows boxes are setup the same way; NT 4.0 SP3 or later defaults to encrypted passwords, and I think Win98 and later default that way also. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message