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.
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
