From owner-freebsd-questions@FreeBSD.ORG Tue Sep 22 18:44:10 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 3F6E31065670 for ; Tue, 22 Sep 2009 18:44:10 +0000 (UTC) (envelope-from dkelly@Grumpy.DynDNS.org) Received: from smtp.knology.net (smtp.knology.net [24.214.63.101]) by mx1.freebsd.org (Postfix) with ESMTP id B3B5E8FC08 for ; Tue, 22 Sep 2009 18:44:09 +0000 (UTC) Received: (qmail 29773 invoked by uid 0); 22 Sep 2009 18:44:08 -0000 Received: from unknown (HELO Grumpy.DynDNS.org) (24.42.224.110) by smtp5.knology.net with SMTP; 22 Sep 2009 18:44:08 -0000 Received: by Grumpy.DynDNS.org (Postfix, from userid 928) id 391F12841F; Tue, 22 Sep 2009 13:44:05 -0500 (CDT) Date: Tue, 22 Sep 2009 13:44:05 -0500 From: David Kelly To: freebsd-questions@freebsd.org Message-ID: <20090922184405.GB46344@Grumpy.DynDNS.org> References: <8DFC1B25-8AED-4CD1-ABDC-7A9DDF45C362@olivent.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i Subject: Re: network freebsd computers X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Sep 2009 18:44:10 -0000 On Tue, Sep 22, 2009 at 02:12:48PM -0400, Carmel NY wrote: > > I can find a virtual cornucopia of information on networking Windows > machines; Microsoft even includes a wizard to accomplish it. However, > there does not seem to be as much information regarding non-Windows > products. Perhaps because it is *harder* to network Windows than Unix? Skimming this thread something I would suggest that may be falling through the cracks is to unify your user accounts across all the machines. No matter that user "joe" isn't supposed to be using a particular machine do not reuse joe's userid on that machine. Also reconsider the need to share all filesystems across all machines. A typical Windows "network application" often runs client-fileserver rather than client-server. When one can not remotely login to a single-user Windows machine, filesharing band-aids that issue. Multi-user Unix systems trivially allow remote logins including ftp and scp file copying. -- David Kelly N4HHE, dkelly@HiWAAY.net ======================================================================== Whom computers would destroy, they must first drive mad.