From owner-freebsd-questions@FreeBSD.ORG Thu Aug 30 01:48:12 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 95E0E16A417 for ; Thu, 30 Aug 2007 01:48:12 +0000 (UTC) (envelope-from freebsd@dfwlp.com) Received: from pollux.dfwlp.com (rrcs-64-183-212-244.sw.biz.rr.com [64.183.212.244]) by mx1.freebsd.org (Postfix) with ESMTP id 621E013C459 for ; Thu, 30 Aug 2007 01:48:12 +0000 (UTC) (envelope-from freebsd@dfwlp.com) Received: from athena.dfwlp.com (athena.dfwlp.com [192.168.125.83]) (authenticated bits=0) by pollux.dfwlp.com (8.13.8/8.13.8) with ESMTP id l7U1m7f0051016 for ; Wed, 29 Aug 2007 20:48:07 -0500 (CDT) (envelope-from freebsd@dfwlp.com) From: Jonathan Horne To: freebsd-questions@freebsd.org Date: Wed, 29 Aug 2007 20:48:06 -0500 User-Agent: KMail/1.9.7 References: <821703.76521.qm@web58106.mail.re3.yahoo.com> In-Reply-To: <821703.76521.qm@web58106.mail.re3.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200708292048.06895.freebsd@dfwlp.com> X-Spam-Status: No, score=-4.4 required=3.6 tests=ALL_TRUSTED,BAYES_00 autolearn=ham version=3.2.1 X-Spam-Checker-Version: SpamAssassin 3.2.1 (2007-05-02) on pollux.dfwlp.com 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 01:48:12 -0000 On Wednesday 29 August 2007 19:40:09 L Goodwin wrote: > I apologize for asking this question, but people who > know UNIX often know a lot about operating systems in > general. > > I have a client with a Windows 2000 Pro SP4 host. He > cycled power without shutting down Windows, and now > the Windows network (Network Neighborhood) is hosed. > When he tries to access Network Neighborhood (from > Windows Explorer), he get "Workgroup not available. > The network name cannot be found.". > > This host can ping other hosts on LAN and has Internet > access, and other hosts on LAN see this host and can > access its shared resources (filesytem and printer), > AND connect to it via VPN (it is set up as a VPN > Host). > > What is the "correct" procedure for recovering from > this mishap? TIA! :-) > youll probably want to start here: http://groups.google.com/groups/dir?&sel=33607436&expand=1 ... and now that thats out of the way... let the flames begin! -- Jonathan Horne http://dfwlpiki.dfwlp.org freebsd@dfwlp.com