Date: Tue, 22 Sep 2009 13:44:05 -0500 From: David Kelly <dkelly@hiwaay.net> To: freebsd-questions@freebsd.org Subject: Re: network freebsd computers Message-ID: <20090922184405.GB46344@Grumpy.DynDNS.org> In-Reply-To: <BLU0-SMTP22DAC69001869CA07A8B4793DC0@phx.gbl> References: <BLU0-SMTP94A0279291FD20358E7D2E93DC0@phx.gbl> <8DFC1B25-8AED-4CD1-ABDC-7A9DDF45C362@olivent.com> <BLU0-SMTP22DAC69001869CA07A8B4793DC0@phx.gbl>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090922184405.GB46344>