Yes, this is WINS or master browser issue. Use browstat to troubleshooting or these search results may help,
Computer Browser The master browser has received a server announcement from the computer <computer ... You have a master browser issue if you have the following symptoms. ...
www.chicagotech.net/browser.htm
Troubleshooting browser issues The master browser has received a server announcement from the computer <computer name> that believes that it is the master browser ...
www.chicagotech.net/troubleshootingbrowser.htm
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"fly2moon2" <(E-Mail Removed)> wrote in message news:FC545982-A5F4-4F87-AE68-(E-Mail Removed)...
Hi,
My setup:
Server 2003: Windows 2003 Server Std. is the domain controller of the Active
Directory; is DNS server; is WINS Server
Server 2000: Windows 2000 Server, simply join the Active Directory.
Client PCs: Doesn't matter Windows XP/98; all PCs experience the problem
described below.
My problem:
Server2000 all alone has Shares accessible to all PCs. This week this is no
longer the case.
I can: net use {driveletter}: \\server2000\share by giving right credentials;
I CAN'T: at Explorer, it is ok click the Server2000 at Network Neighbourhood
but NOT ACCESSIBLE to the share folders within it. The error message states
that the computer can't be used or access rights not enough. (But I'm sure I
have enough rights)
I can: at Windows Start -> Run -> type \\10.1.1.1 (e.g. server2000's
ipaddress) and have the Explorer window shown up; \\10.1.1.1\share is OK
accessible also. It is still OK if I were to type \\server2000 -> Explorer
window still popup (again, only that the Shares within it can be accessed)
But I CAN'T: at Windows Start -> Run -> type \\server2000\share -> error
stating that it can't be accessed
The problem at first seems to me is a WINS problem as using \\IPaddress not
having the problem. But then it seems not totally as at least it has response
when using \\server2000 (at least name is resolved). So, I've my hair teared
out.
The Share Permissions and Access Rights has NO CHANGE before or after the
problem appears. No only one share, all shares of server2000 has the problem.
And some public shares even given EVERYONE rights and permission still having
the same problem.
I really need you experts help. Thanks in advance.
best regards,
jackLing