Solved

Computer Browser not displaying all domain computers

Posted on 2011-02-21
3
748 Views
Last Modified: 2012-05-11
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
Comment
Question by:OSDIT
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 2
3 Comments
 
LVL 71

Expert Comment

by:Chris Dent
ID: 34949591

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

Chris
0
 

Author Comment

by:OSDIT
ID: 34993560
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
 
LVL 71

Accepted Solution

by:
Chris Dent earned 125 total points
ID: 34995159

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

Featured Post

Get 15 Days FREE Full-Featured Trial

Benefit from a mission critical IT monitoring with Monitis Premium or get it FREE for your entry level monitoring needs.
-Over 200,000 users
-More than 300,000 websites monitored
-Used in 197 countries
-Recommended by 98% of users

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Resolve DNS query failed errors for Exchange
I was prompted to write this article after the recent World-Wide Ransomware outbreak. For years now, System Administrators around the world have used the excuse of "Waiting a Bit" before applying Security Patch Updates. This type of reasoning to me …
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…
This Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …

688 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question