From owner-freebsd-questions@FreeBSD.ORG Thu Aug 30 03:23:07 2007 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 6BD0716A419 for ; Thu, 30 Aug 2007 03:23:07 +0000 (UTC) (envelope-from xrayv19@yahoo.com) Received: from web58115.mail.re3.yahoo.com (web58115.mail.re3.yahoo.com [68.142.236.138]) by mx1.freebsd.org (Postfix) with SMTP id 2BEC413C467 for ; Thu, 30 Aug 2007 03:23:07 +0000 (UTC) (envelope-from xrayv19@yahoo.com) Received: (qmail 8292 invoked by uid 60001); 30 Aug 2007 03:22:41 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=Sg6WwrDzv5VKsD+NSVaG2DyxzuSwBlbHlsazom5cVBYqogPvW2KxM5c4OTTzm0DMx4IN0wW27mUYcZABYbdZQ4BnwpY3KZyqdbe9aPP0/FDo71T6+lDPtGd7JnwnipXeaydyXWmsw15NXpi6gUZgHxX22NuvNQ3Z78ozSSGO9OM=; X-YMail-OSG: KzyeBYsVM1npV.gaxO.p0o7LuFnZk8TFE1nlpMqnVt6bF5h7Wct6IDwHwsAyJKPDTcBVocHnBiyxNTmteATAUqScS32IVHqgclE6br.2CSe_WIzfDfiglQ-- Received: from [131.191.82.223] by web58115.mail.re3.yahoo.com via HTTP; Wed, 29 Aug 2007 20:22:41 PDT Date: Wed, 29 Aug 2007 20:22:41 -0700 (PDT) From: L Goodwin To: Garrett Cooper , Steve Bertrand In-Reply-To: <46D634B5.4070904@u.washington.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <357069.7951.qm@web58115.mail.re3.yahoo.com> Cc: freebsd-questions@freebsd.org Subject: Re: OT: Workgroup not available. The network name cannot be found. on Windows 2000 Pro SP4 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: Thu, 30 Aug 2007 03:23:07 -0000 This is what I was hoping for. Thanks all! BTW, I did my second successful FreeBSD installation this week on a server that I could not get it to run on for the longest time. :-) --- Garrett Cooper wrote: > Steve Bertrand wrote: > >> What is the "correct" procedure for recovering > from > >> this mishap? TIA! :-) > >> > > > > - download FreeBSD disk-1 from freebsd.org > > - insert CD into drive, and install :) > > > > Seriously.. > > > > It's been a while since I've actually managed a > Windows network per-se, > > but from what I recall, you can change the > workgroup to something else > > (then reboot), then re-assign the PC to the proper > workgroup (then > > reboot again), it may fix it. AFAIR, you can do > this by right-clicking > > on My Computer, and changing the computers > identity or name. > > > > If that doesn't work, then ensure that Norton or > some other so called > > 'firewall' or 'security suite' isn't blocking > outbound traffic via the > > NetBIOS protocol ports: > > > > # grep -i netbios /etc/services > > > > netbios-ns 137/tcp #NETBIOS Name Service > > netbios-ns 137/udp #NETBIOS Name Service > > netbios-dgm 138/tcp #NETBIOS Datagram > Service > > netbios-dgm 138/udp #NETBIOS Datagram > Service > > netbios-ssn 139/tcp #NETBIOS Session > Service > > netbios-ssn 139/udp #NETBIOS Session > Service > > > > Also, port 445 TCP and UDP may come into play > here. > > > > Interesting though that inbound is allowed/working > but outbound is fudged. > > > > Is this PC on a win2k Domain? Is there anything in > the 'logs' (stated > > very loosely) in the Event Viewer on the > remote/local hosts? > > > > Steve > > He hosed something with the network > configuration. > > *digs out old Windows tech support knowledge* > > 1. Executing: 'netsh int ip reset log' from > Start->Run will clean reset > the TCP/IP stack (it helps, on occasion). > 2. Uninstalling / reinstalling 'Client for Microsoft > Networks' and 'File > and Printer Sharing for Microsoft Networks' may be a > good bet if > something's corrupted. > 3. Adjusting 3rd party firewall rules to not block > ports 137-139 and 445 > (both TCP/UDP connection types) should eliminate the > problem, if any do > exist. > > And when all else fails.. backup and reinstall > (typically this is > less time consuming than root-cause debugging the > problem). With an OS > that age, your client really should be using XP > anyhow if he/she can > help it, because of the fact that it's not supported > by M$ anymore. > > Cheers, > -Garrett > ____________________________________________________________________________________ Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online. http://smallbusiness.yahoo.com/webhosting