Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 757
  • Last Modified:

Computer Browser not displaying all domain computers

Hi,

We have windows server 2003 domain with windows XP and windows 7 machines. The domain has 4 sites. I just introduced windows 2008 R2 domain controller.

I used to be able to see all computers in computer browser but now it will display the computers only within each site. So when any user brosw entire network, only computers belonging to that site will be visible.

Is there anyway I can get computers from entire domain listed when browsing entire network.

Thanks,
dd
0
OSDIT
Asked:
OSDIT
  • 2
1 Solution
 
Chris DentPowerShell DeveloperCommented:

You need a WINS server so your Domain Master Browser can find individual Master Browsers on each subnet.

Chris
0
 
OSDITAuthor Commented:
Hi,

I realise it must be something with NETBIOS name resolution OR WINS but We were not using WINS and were able to do this before. It has just stopped after introducing Windows Server 2008 R2 Domain controller in the system.

Anything else am I missing.? Please let me know.

dd
0
 
Chris DentPowerShell DeveloperCommented:

WINS is just a helper for NetBIOS, there is no Or there :)

However, Windows 2008 R2 has been known to cause a fair number of problems with Computer Browsing. You might start off by checking the Firewall on the system (there's a large set covering NetBIOS). You should also make sure the Computer Browser service is set to Automatic and Started, I believe it defaults to disabled on 2008+.

In more general terms, you either need:

1. To relay Broadcast traffic between (all) subnets / sites

Or:

2. To implement a WINS server

Those are the only choices, nothing else will work. And out of those, the second is recommended as it is far less mess.

And as a final note: Network Browsing is there for legacy support (Windows NT support), it's worth evaluating whether or not you actually need it because it's a pretty nasty pseudo-protocol by today's standards and has no impact on your AD domain outside of a small number of legacy applications and services.

Chris
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now