Date: Thu, 30 Aug 2007 08:38:10 -0500 From: Derek Ragona <derek@computinginnovations.com> To: L Goodwin <xrayv19@yahoo.com>, freebsd-questions@freebsd.org Subject: Re: OT: Workgroup not available. The network name cannot be found. on Windows 2000 Pro SP4 Message-ID: <6.0.0.22.2.20070830083707.0267ec78@mail.computinginnovations.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
At 07:40 PM 8/29/2007, 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! :-)
You need to unjoin the domain or workgroup, reboot. Then rejoin the domain
or workgroup and reboot yet again.
-Derek
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6.0.0.22.2.20070830083707.0267ec78>