From owner-freebsd-questions@FreeBSD.ORG Thu Aug 30 03:08:44 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 7CA8C16A418 for ; Thu, 30 Aug 2007 03:08:44 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from mxout5.cac.washington.edu (mxout5.cac.washington.edu [140.142.32.135]) by mx1.freebsd.org (Postfix) with ESMTP id 1C31713C480 for ; Thu, 30 Aug 2007 03:08:44 +0000 (UTC) (envelope-from youshi10@u.washington.edu) Received: from smtp.washington.edu (smtp.washington.edu [140.142.32.141] (may be forged)) by mxout5.cac.washington.edu (8.13.7+UW06.06/8.13.7+UW07.06) with ESMTP id l7U38Tma011205 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Wed, 29 Aug 2007 20:08:29 -0700 X-Auth-Received: from [192.168.10.45] (c-24-10-12-194.hsd1.ca.comcast.net [24.10.12.194]) (authenticated authid=youshi10) by smtp.washington.edu (8.13.7+UW06.06/8.13.7+UW07.03) with ESMTP id l7U38TIV027955 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 29 Aug 2007 20:08:29 -0700 Message-ID: <46D634B5.4070904@u.washington.edu> Date: Wed, 29 Aug 2007 20:08:37 -0700 From: Garrett Cooper User-Agent: Thunderbird 2.0.0.6 (Windows/20070728) MIME-Version: 1.0 To: Steve Bertrand References: <821703.76521.qm@web58106.mail.re3.yahoo.com> <46D62F05.1000309@ibctech.ca> In-Reply-To: <46D62F05.1000309@ibctech.ca> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-PMX-Version: 5.3.3.310218, Antispam-Engine: 2.5.1.298604, Antispam-Data: 2007.8.29.194723 X-Uwash-Spam: Gauge=IIIIIII, Probability=7%, Report='__CT 0, __CTE 0, __CT_TEXT_PLAIN 0, __HAS_MSGID 0, __MIME_TEXT_ONLY 0, __MIME_VERSION 0, __SANE_MSGID 0, __USER_AGENT 0' 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:08:44 -0000 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