Apexadmin
asked on
Browsing network shares in Network Places is inconsistent.
Certain people are not able to browse the network for a handful of servers and PCs. It seems to be a sporadic issue. It does not appear to matter which version of windows we are on. I have 7, others have vista or XP and we all can’t see a few servers and other various computers. There are different VLANs, not all are on the same VLAN. They are all joined to the domain and have antivirus and firewalls are disabled.
My setup is:
Windows 7 with up to date forefront with firewall turned off. We can access them by using a direct path (i.e. //servername/path). This has happened in the past but it seemed to go away.
My setup is:
Windows 7 with up to date forefront with firewall turned off. We can access them by using a direct path (i.e. //servername/path). This has happened in the past but it seemed to go away.
kevinhsieh
Browsing the network for servers is archaic and doesn't scale well. Try it on a networks with hundreds or thousands of computers. The browse list is compiled via network broadcasts, which stop at the VLAN border. You should always be able to connect to \\servername, even if it doesn't appear in your browse list. If you really want to be able to browse to everything, you need to install and configure WINS in your environment.
ASKER
I'm sorry, we have WINS running on a virtual Windows 2008 R2 Enterprise. The entry for the server I'm testing out is correct.
ASKER
Also, firewall settings are set to allow through doimain and WINS service.
Does the WINNS database show all of your computers?
ASKER
Yes, I can see all of them.
Does all of the clients have Computer Browser service started?
WINS is showing all of your client computers?
WINS is showing all of your client computers?
ASKER
It's showing the server that I can't access from the PC I'm trying to access from. As far as all the computers connected, I'm not sure but I'd be willing to bet it's 90%
And yes the Computer Browser service is started.
And yes the Computer Browser service is started.
ASKER
Had to call Microsoft in on this one. The issue was solved by created registry key for isdomainmaster , maintainserverlist on the PDC role server because multiple computers were attempting to become the domain master and the election wasn't working properly.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Microsoft fixed the issue.