client do not show up in my network places

Up until a couple of weeks ago I was working in a Windows 2000 server
environment with XP and 2000 Pro clients. From any computer in the
network, if you went to My Network Places - Entire Network - Microsoft
Windows Network - Domain Name, you would find all clients and servers
listed.

Recently, we added a Windows Server 2003 server and promotoed it to a
domain controller. This server was given a copy of the global catalog
(each of our three, soon to be two, domain controllers has it). I also
transfered all of the FSMO roles to the new 2003 box. It has a static
IP address. We also moved the domain functionality level from Windows
2000 mixed mode to Windows 2000 native mode. The 2003 Server currently
co-exists with the previously existing two server 2000 boxes.

Now, when you go to my network places - entire netowrk - microsoft
windows network - domain name, you only see servers and a select few
workstations. The only commonality I can see in the computers that I
can still see are that they all have static IP addresses.

This is a problem of convenience, since it was easy to browse to a
computer to install a printer remotely or just check the computer name.
It is a problem of functionality in that my McAfee EPO server needs to
see the full list of domain workstations to detect when a new computer
is added to a system and keep it's virus protection up to date.

Any thoughts on why I can no longer see clients in My Network Places
and how I might be able to do so again?

Thanks,

Jim

Tell us how many IP subnets you have and tell us about
your WINS SERVERS.

Hint: if you have more than one IP subnet you probably
need a (set of replicating) WINS Server(s).

If you have more than one domain, then you have even
more need for the WINS servers.

All computers (including Servers, DCs, and even WINS
servers themselves) need to be WINS CLIENTS (NIC->
IP properties->Advanced->WINS tab.

--
Herb Martin


"Jim Johnson" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> Up until a couple of weeks ago I was working in a Windows 2000 server
> environment with XP and 2000 Pro clients. From any computer in the
> network, if you went to My Network Places - Entire Network - Microsoft
> Windows Network - Domain Name, you would find all clients and servers
> listed.
>
> Recently, we added a Windows Server 2003 server and promotoed it to a
> domain controller. This server was given a copy of the global catalog
> (each of our three, soon to be two, domain controllers has it). I also
> transfered all of the FSMO roles to the new 2003 box. It has a static
> IP address. We also moved the domain functionality level from Windows
> 2000 mixed mode to Windows 2000 native mode. The 2003 Server currently
> co-exists with the previously existing two server 2000 boxes.
>
> Now, when you go to my network places - entire netowrk - microsoft
> windows network - domain name, you only see servers and a select few
> workstations. The only commonality I can see in the computers that I
> can still see are that they all have static IP addresses.
>
> This is a problem of convenience, since it was easy to browse to a
> computer to install a printer remotely or just check the computer name.
> It is a problem of functionality in that my McAfee EPO server needs to
> see the full list of domain workstations to detect when a new computer
> is added to a system and keep it's virus protection up to date.
>
> Any thoughts on why I can no longer see clients in My Network Places
> and how I might be able to do so again?
>
> Thanks,
>
> Jim
>

I have 3 domain controllers. Two are Windows Server 2000, the new one
is 2003. One of the Windows 2000 Servers is acting as WINS, DNS and
DHCP server (as well as being a print server). It is the same server
that originally had the FSMO roles, but they have been moved.

I have one domain, with several different IP subnets, if I'm using the
terminology correctly. One for servers (a.a.x.x), one for IP phones
(a.b.x.x), one for clients (a.c.x.x), etc.

Do you think running WINS, etc. from the 2003 server, or running it on
a set of replicating servers, might solve my problem?

Jim

Herb Martin wrote:
> Tell us how many IP subnets you have and tell us about
> your WINS SERVERS.
>
> Hint: if you have more than one IP subnet you probably
> need a (set of replicating) WINS Server(s).
>
> If you have more than one domain, then you have even
> more need for the WINS servers.
>
> All computers (including Servers, DCs, and even WINS
> servers themselves) need to be WINS CLIENTS (NIC->
> IP properties->Advanced->WINS tab.
>
> --
> Herb Martin
>
>
> "Jim Johnson" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) ups.com...
> > Up until a couple of weeks ago I was working in a Windows 2000
server
> > environment with XP and 2000 Pro clients. From any computer in the
> > network, if you went to My Network Places - Entire Network -
Microsoft
> > Windows Network - Domain Name, you would find all clients and
servers
> > listed.
> >
> > Recently, we added a Windows Server 2003 server and promotoed it to
a
> > domain controller. This server was given a copy of the global
catalog
> > (each of our three, soon to be two, domain controllers has it). I
also
> > transfered all of the FSMO roles to the new 2003 box. It has a
static
> > IP address. We also moved the domain functionality level from
Windows
> > 2000 mixed mode to Windows 2000 native mode. The 2003 Server
currently
> > co-exists with the previously existing two server 2000 boxes.
> >
> > Now, when you go to my network places - entire netowrk - microsoft
> > windows network - domain name, you only see servers and a select
few
> > workstations. The only commonality I can see in the computers that
I
> > can still see are that they all have static IP addresses.
> >
> > This is a problem of convenience, since it was easy to browse to a
> > computer to install a printer remotely or just check the computer
name.
> > It is a problem of functionality in that my McAfee EPO server needs
to
> > see the full list of domain workstations to detect when a new
computer
> > is added to a system and keep it's virus protection up to date.
> >
> > Any thoughts on why I can no longer see clients in My Network
Places
> > and how I might be able to do so again?
> >
> > Thanks,
> >
> > Jim
> >

Replicating WINS servers is not really required e.g.,
you could use 1 single WINS server which all clients
point towards.

Browsing relies on the server service to send a host name
announcement packet to a local SMB or segment master
browser. The SMB gathers the local browse list and passes
it on to the DMB or domain master browser. The DMB gathers
the entire list and passes back to all SMBs who then provide the
list to clients who request them. The DMB will also query WINS
in order to find other DMBs to get their domain wide browse list.
Each DMB/PDC registers a domain name 1b unique name for
domains with the WINS service. I'd start by verifying the 1b name
for the missing domain is present in WINS. Note: This whole process
also relies on NetBios broadcasts in order to work. Netbios should
not be filtered.

"Jim Johnson" <(E-Mail Removed)> wrote in message news:
> I have 3 domain controllers. Two are Windows Server 2000, the new one
> is 2003. One of the Windows 2000 Servers is acting as WINS, DNS and
> DHCP server (as well as being a print server). It is the same server
> that originally had the FSMO roles, but they have been moved.
>
> I have one domain, with several different IP subnets, if I'm using the
> terminology correctly. One for servers (a.a.x.x), one for IP phones
> (a.b.x.x), one for clients (a.c.x.x), etc.
>
> Do you think running WINS, etc. from the 2003 server, or running it on
> a set of replicating servers, might solve my problem?

"Michael Giorgio - MS MVP" <(E-Mail Removed)> wrote in
message news:(E-Mail Removed)...
> Replicating WINS servers is not really required e.g.,
> you could use 1 single WINS server which all clients
> point towards.

Having a single WINS Database IS REQUIRED in almost
all cases so the point of replicating them is IF one has more
than one WINS servers.

> Browsing relies on the server service to send a host name
> announcement packet to a local SMB or segment master
> browser. The SMB gathers the local browse list and passes
> it on to the DMB or domain master browser. The DMB gathers
> the entire list and passes back to all SMBs who then provide the
> list to clients who request them. The DMB will also query WINS
> in order to find other DMBs to get their domain wide browse list.

Yes, this last is the reason you need WINS if you have more
than one subnet (same subnet, DMB can broadcast for each
other.)

> Each DMB/PDC registers a domain name 1b unique name for
> domains with the WINS service. I'd start by verifying the 1b name
> for the missing domain is present in WINS. Note: This whole process
> also relies on NetBios broadcasts in order to work. Netbios should
> not be filtered.

It may be quite possible to limit most such broadcasts,
except the server announcements which if the WINS is
correct never need to leave a subnet (pass a router.)


--
Herb Martin


>
> "Jim Johnson" <(E-Mail Removed)> wrote in message news:
> > I have 3 domain controllers. Two are Windows Server 2000, the new one
> > is 2003. One of the Windows 2000 Servers is acting as WINS, DNS and
> > DHCP server (as well as being a print server). It is the same server
> > that originally had the FSMO roles, but they have been moved.
> >
> > I have one domain, with several different IP subnets, if I'm using the
> > terminology correctly. One for servers (a.a.x.x), one for IP phones
> > (a.b.x.x), one for clients (a.c.x.x), etc.
> >
> > Do you think running WINS, etc. from the 2003 server, or running it on
> > a set of replicating servers, might solve my problem?
>
>

Hi Herb,

"Herb Martin" <(E-Mail Removed)> wrote in message news
> "Michael Giorgio - MS MVP" <(E-Mail Removed)> wrote
in
> message news:> > Replicating WINS servers is not really required e.g.,
> > you could use 1 single WINS server which all clients
> > point towards.
>
> Having a single WINS Database IS REQUIRED in almost
> all cases so the point of replicating them is IF one has more
> than one WINS servers.

My point exactly.

>
> > Browsing relies on the server service to send a host name
> > announcement packet to a local SMB or segment master
> > browser. The SMB gathers the local browse list and passes
> > it on to the DMB or domain master browser. The DMB gathers
> > the entire list and passes back to all SMBs who then provide the
> > list to clients who request them. The DMB will also query WINS
> > in order to find other DMBs to get their domain wide browse list.
>
> Yes, this last is the reason you need WINS if you have more
> than one subnet (same subnet, DMB can broadcast for each
> other.)

Well not exactly. <g> You could use lmhosts which is a static
alternative
to WINS.

>
> > Each DMB/PDC registers a domain name 1b unique name for
> > domains with the WINS service. I'd start by verifying the 1b name
> > for the missing domain is present in WINS. Note: This whole process
> > also relies on NetBios broadcasts in order to work. Netbios should
> > not be filtered.
>
> It may be quite possible to limit most such broadcasts,
> except the server announcements which if the WINS is
> correct never need to leave a subnet (pass a router.)

You don't want to block Netbios Broadcasts as these
are necessary for cross subnet browsing. Rather you
want to disable any broadcast forwarding features which
may be running which will cause the host name packets
to be forwarded to a remote SMB instead of a local
SMB.

"Michael Giorgio - MS MVP" <(E-Mail Removed)> wrote in
message

> > It may be quite possible to limit most such broadcasts,
> > except the server announcements which if the WINS is
> > correct never need to leave a subnet (pass a router.)
>
> You don't want to block Netbios Broadcasts as these
> are necessary for cross subnet browsing.

No that is incorrect and backwards even.

The main point of the Domain Master Browser is to exchange
lists among Master Browsers of various subnets precisely
so that browsing works cross subnet without having to
propagate the broadcasts.

Routers create subnets by blocking (actually just ignoring)
broadcasts and that is the way it should remain.

By using the WINS server the various browse masters
can find each other and exchange lists.

Do NOT propagate the NetBIOS broadcasts across your
routers -- except perhaps in the simple case of only one
or two subnets when you cannot use WINS server(s) for
some reason.

LMhosts are a technically possible alternative but a
practical nightmare to manage for anyone who actually
needs more than one subnets (more than a few dozen
machines) except in some trivial cases such as two
locations over a WAN with only a few machines in
each location.

WINS servers are practically free -- they run on your
existing servers -- and are trivial, much easier than
LMhosts files to setup and maintain over time.

Anyone who has ever managed hosts file or lmhosts
file over as many as 100 machines will tell you how
little fun, and how impratical, that is.

For such networks WINS servers are trivial and for
large networks where WINS is somewhat difficult,
it isn't even possible to maintain such lmhosts files
over time.

--
Herb Martin

Hi Herb,

"Herb Martin" <(E-Mail Removed)> wrote in message news:
> "Michael Giorgio - MS MVP" <(E-Mail Removed)> wrote
in
> message
>
> > > It may be quite possible to limit most such broadcasts,
> > > except the server announcements which if the WINS is
> > > correct never need to leave a subnet (pass a router.)
> >
> > You don't want to block Netbios Broadcasts as these
> > are necessary for cross subnet browsing.
>
> No that is incorrect and backwards even.

I should have been more specific. <g>

Broadcast *forwarding* specifically is not recommended
and by default most routers do not *forward* NetBios
broadcasts specifically UDP 137, 138. However blocking
or disabling these ports will in effect disconnect the two
networks in a pre W2k environment and disable all browsing
in an all W2k or higher environment e.g., Netbios removed..

>
> The main point of the Domain Master Browser is to exchange
> lists among Master Browsers of various subnets precisely
> so that browsing works cross subnet without having to
> propagate the broadcasts.
>
> Routers create subnets by blocking (actually just ignoring)
> broadcasts and that is the way it should remain.
>
> By using the WINS server the various browse masters
> can find each other and exchange lists.
>
> Do NOT propagate the NetBIOS broadcasts across your
> routers -- except perhaps in the simple case of only one
> or two subnets when you cannot use WINS server(s) for
> some reason.
>


I certainly won't argue with you that WINS is a better alternative
nor did I in any way suggest it a better alternative. I simply stated
that it *can* be done without WINS and it *can*.

> > > You don't want to block Netbios Broadcasts as these
> > > are necessary for cross subnet browsing.
> >
> > No that is incorrect and backwards even.
>
> I should have been more specific. <g>
>
> Broadcast *forwarding* specifically is not recommended
> and by default most routers do not *forward* NetBios
> broadcasts specifically UDP 137, 138. However blocking
> or disabling these ports will in effect disconnect the two
> networks in a pre W2k environment and disable all browsing
> in an all W2k or higher environment e.g., Netbios removed..

Right. You were confusing BROADCASTS on those ports
with the use of the ports themselves for sending packets
addressed to particular machines/IP addresses.

Don't block the ports. DO block broadcasts (the default.)