When we try to browse the network, an error "Domain xxxx is not available." occurs. The error usually goes away...
By submitting your email address, you agree to receive emails regarding relevant topic offers from TechTarget and its partners. You can withdraw your consent at any time. Contact TechTarget at 275 Grove Street, Newton, MA.
in the next 5-10 minutes -- and voila -- we can browse the network again. We also have errors 8021 and 8032 in the application error logs from member servers who are not the master browser, but as backup browsers.
I read the article Q135404 from MS Web site, but it doesn't really apply. Can you assist? Thanks.
Windows 2000 machines favor DNS for looking up machines, but the browser list is seeded by the WINS database if it is present. So you may want to check on the WINS servers and make sure there are no errors, rogue entries or corruption in the WINS databases.
Also, check the Windows 2000 workstations for consistency of the network configuration. If the machines have LMHOSTS or HOSTS files with bad entries, it can lead to lots of little annoying problems.
Ultimately, since you do have an Active Directory, you should consider publishing shares, printers and other resources in the directory. Then you can educate the users on using AD search tools instead of browsing. This way you can leverage AD and other features like DFS.
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.