-3

We have multiple computers joined in domain. We also have domain controller (Windows server 2008 Enterprise).

The problem is, that sometimes computer browsing (Windows Explorer: My Network Places/Entire Network/MS Windows Network) works and sometimes doesn't.

Restarting Computer browser on domain controller helps poorly - usually not.

If users type other computer's name like Start/run: \\computer1
computer is accessible.

What seems to be the problem?


We already have WINS server installed.

enter image description here

user9517
  • 115,471
  • 20
  • 215
  • 297
user1452932
  • 25
  • 1
  • 4

1 Answers1

4

DNS doesn't facilitate network browsing. NetBIOS facilitates network browsing.

Network browsing has never been "reliable" in the sense that the list of computers is always accurate and complete.

If you want to have an accurate and complete list of computers while browsing the network then you'll have to implement a WINS server.

Personally, I don't understand why this is an issue. Why is it important that users be able to browse an accurate and complete list of computers on the network? Do they not know where resources are (shared folders and printers) and need to browse the network to find them? If so, that's poor infrastructure design and management, IMO.

joeqwerty
  • 109,901
  • 6
  • 81
  • 172
  • +1, I just want to note, that network browsing is working only on current IP broadcast, so at most 255 computers are shown (until you use WINS or enable broadcast traffic over subnets on switches) –  Oct 10 '12 at 09:23