Network Neighborhood does not Include All Domain Computers

I am on a Windows Server 2003 AD network, and when I view my Network
Neighborhood or type "net view", I see only the machines on my local
subnet. I have DHCP configured to give me valid DNS and WINS servers,
and both WINS servers in the domain have records for all of the
machines in the domain. If I type "net view \\COMPUTERNAME", I see
every machine just fine. It is only the viewing of the domain which
is incomplete. Any ideas?

Rick Kasten wrote:
> I am on a Windows Server 2003 AD network, and when I view my Network
> Neighborhood or type "net view", I see only the machines on my local
> subnet. I have DHCP configured to give me valid DNS and WINS servers,
> and both WINS servers in the domain have records for all of the
> machines in the domain. If I type "net view \\COMPUTERNAME", I see
> every machine just fine. It is only the viewing of the domain which
> is incomplete. Any ideas?
Just a question for clarification: the WINS servers are replication
partners to one another?

WINS only gives you name resolution, and that is working if you can do
net view \\computername .

Network neighborhood and net view for the entire network depend on the
computer browser service. This is a bit of a can of worms, and can be tricky
in a segmented network. There are heaps of articles on it. You could start
with KB 188001 and 188305 . These refer to W2k and NT, but the browser
service and WINS haven't changed much since NT SP5 .

"Rick Kasten" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> I am on a Windows Server 2003 AD network, and when I view my Network
> Neighborhood or type "net view", I see only the machines on my local
> subnet. I have DHCP configured to give me valid DNS and WINS servers,
> and both WINS servers in the domain have records for all of the
> machines in the domain. If I type "net view \\COMPUTERNAME", I see
> every machine just fine. It is only the viewing of the domain which
> is incomplete. Any ideas?

Using the links you provided, I have determined that the Master
Browser for my segment is a Red Hat Linux box. I know for a fact that
I have worked on segmented networks before of sizes vastly larger than
the network I'm on now, and their Master Browsers were always the PDC
(NT) or one of the DC's (AD). My guess is this is a configuration
error on the Linux box that it is assuming the role for my segment, so
how do I go about setting my DC, which is on a different subnet than
me, as the master browser for my subnet?

RIck

"Bill Grant" <not.available@online> wrote in message news:<(E-Mail Removed)>...
> WINS only gives you name resolution, and that is working if you can do
> net view \\computername .
>
> Network neighborhood and net view for the entire network depend on the
> computer browser service. This is a bit of a can of worms, and can be tricky
> in a segmented network. There are heaps of articles on it. You could start
> with KB 188001 and 188305 . These refer to W2k and NT, but the browser
> service and WINS haven't changed much since NT SP5 .
>
> "Rick Kasten" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) om...
> > I am on a Windows Server 2003 AD network, and when I view my Network
> > Neighborhood or type "net view", I see only the machines on my local
> > subnet. I have DHCP configured to give me valid DNS and WINS servers,
> > and both WINS servers in the domain have records for all of the
> > machines in the domain. If I type "net view \\COMPUTERNAME", I see
> > every machine just fine. It is only the viewing of the domain which
> > is incomplete. Any ideas?

I suspect you are correct that you will need to change something on the
Linux box. The master browser is elected based on a number things, including
OS type. I recall reading a post where a user forced his Unix box to become
the master browser by altering its settings. Can't recall the details and
it was a long time ago. Perhaps someone running a mixed network can supply
the details.

"Rick Kasten" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> Using the links you provided, I have determined that the Master
> Browser for my segment is a Red Hat Linux box. I know for a fact that
> I have worked on segmented networks before of sizes vastly larger than
> the network I'm on now, and their Master Browsers were always the PDC
> (NT) or one of the DC's (AD). My guess is this is a configuration
> error on the Linux box that it is assuming the role for my segment, so
> how do I go about setting my DC, which is on a different subnet than
> me, as the master browser for my subnet?
>
> RIck
>
> "Bill Grant" <not.available@online> wrote in message
news:<(E-Mail Removed)>...
> > WINS only gives you name resolution, and that is working if you can do
> > net view \\computername .
> >
> > Network neighborhood and net view for the entire network depend on
the
> > computer browser service. This is a bit of a can of worms, and can be
tricky
> > in a segmented network. There are heaps of articles on it. You could
start
> > with KB 188001 and 188305 . These refer to W2k and NT, but the browser
> > service and WINS haven't changed much since NT SP5 .
> >
> > "Rick Kasten" <(E-Mail Removed)> wrote in message
> > news:(E-Mail Removed) om...
> > > I am on a Windows Server 2003 AD network, and when I view my Network
> > > Neighborhood or type "net view", I see only the machines on my local
> > > subnet. I have DHCP configured to give me valid DNS and WINS servers,
> > > and both WINS servers in the domain have records for all of the
> > > machines in the domain. If I type "net view \\COMPUTERNAME", I see
> > > every machine just fine. It is only the viewing of the domain which
> > > is incomplete. Any ideas?