From owner-freebsd-chat Sat Jan 20 12:14:49 2001 Delivered-To: freebsd-chat@freebsd.org Received: from grumpy.dyndns.org (user-24-214-56-41.knology.net [24.214.56.41]) by hub.freebsd.org (Postfix) with ESMTP id 6002837B402 for ; Sat, 20 Jan 2001 12:14:31 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by grumpy.dyndns.org (8.11.1/8.11.1) with ESMTP id f0KKEEl66220; Sat, 20 Jan 2001 14:14:14 -0600 (CST) (envelope-from dkelly@grumpy.dyndns.org) Message-Id: <200101202014.f0KKEEl66220@grumpy.dyndns.org> X-Mailer: exmh version 2.2 06/23/2000 with nmh-1.0.4 To: Joe Warner Cc: freebsd-chat@FreeBSD.ORG Subject: Re: FreeBSD Stands Out! In-Reply-To: Message from Joe Warner of "Sat, 20 Jan 2001 19:53:48 MST." <3A6A4F3C.E31D628D@uswest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 20 Jan 2001 14:14:14 -0600 From: David Kelly Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Joe Warner writes: > After a couple of hours of working with the > rest of our IS staff to get all the servers back > up, I noticed something peculiar. We were > still having problems with one of our routers > (the config file got blown away) and we > kept checking "Network Neighborhood" on > a Windows machine to see what workstations > were showing up under our domain. For a > long time, the only workstations that would > show up was our primary pdc and the > FreeBSD 3.4 workstation I have in my > cubicle! We all got a chuckle out of this > but I still don't know why this happened. > > Does anyone have any ideas? Have never quite grasped the fine art of Samba tuning but last time I groped with it the defaults had Samba as a "secondary" or such domain controller. Found out because within my network segment up to the 1st router all of the network neighborhood was wiped out (nearby machines were not listed). Machines were getting the network neighborhood info off my Samba. And my Samba didn't have a correct list. Ran that way for months and the IT police didn't come knocking. But noticed it myself in one of those rare moments FreeBSD (and Samba) was not running. Knowing it was something I iterated the Samba configuration until it behaved more like a dumb Win machine with file sharing turned on. Maybe my problem was that I never pointed it at or added it to an official corporate SMB domain. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message