Date: Wed, 29 Aug 2007 20:48:06 -0500 From: Jonathan Horne <freebsd@dfwlp.com> To: freebsd-questions@freebsd.org Subject: Re: OT: Workgroup not available. The network name cannot be found. on Windows 2000 Pro SP4 Message-ID: <200708292048.06895.freebsd@dfwlp.com> In-Reply-To: <821703.76521.qm@web58106.mail.re3.yahoo.com> References: <821703.76521.qm@web58106.mail.re3.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200708292048.06895.freebsd>