NetBIOS network places not all the pc's are there???

Here is what I got. One Domain, 2 dc’s, 6-8 member servers, 50-75
workstations, xp & 2000 sp4. I am using Symantec 10.00, trying to push to an
update to each client pc. I thought there must be more PC's then I am
seeing. I use the Symantec tool "find computer" "audit network� there it
shows PC's that have NOT gotten the update from 8.00 to version 10.00. I do
a print screen and then go to "client remote install� it uses the "my network
places" from the windows OS. I don’t see these PC's with (by NetBIOS name)
in the list of PC's under my Domain. There are PC's there just NOT the ones
I am looking for. I go start, run, \\pcname, I see it's shares. I look in
DNS I see the name and IP, \\xxx.xxx.xxx.xxx I see the shares. I look in AD,
the computers are there, they are not in the default OU "computer" BUT others
are in other “OU�‘s that I can see in “my network places� so, that can’t be
it. WHY AREN'T THESE PCS IN MY NETWORK PLACES? They all use the same DHCP
server getting the same info...
Please help!!! If I can't push the updates remotely, then I have to go out
and TRY to find each PC and run the updates.
Thanks!

The computer browser service does not use DNS or AD. It is an NT legacy
app and uses Netbios names.

The browser service is described in KB188001 and there is a troubleshooter
in KB188305 .

mathew dalton wrote:
> Here is what I got. One Domain, 2 dc's, 6-8 member servers, 50-75
> workstations, xp & 2000 sp4. I am using Symantec 10.00, trying to
> push to an update to each client pc. I thought there must be more
> PC's then I am seeing. I use the Symantec tool "find computer"
> "audit network" there it shows PC's that have NOT gotten the update
> from 8.00 to version 10.00. I do a print screen and then go to
> "client remote install" it uses the "my network places" from the
> windows OS. I don't see these PC's with (by NetBIOS name) in the
> list of PC's under my Domain. There are PC's there just NOT the ones
> I am looking for. I go start, run, \\pcname, I see it's shares. I
> look in DNS I see the name and IP, \\xxx.xxx.xxx.xxx I see the
> shares. I look in AD, the computers are there, they are not in the
> default OU "computer" BUT others are in other "OU"'s that I can see
> in "my network places" so, that can't be it. WHY AREN'T THESE PCS IN
> MY NETWORK PLACES? They all use the same DHCP server getting the
> same info...
> Please help!!! If I can't push the updates remotely, then I have to
> go out and TRY to find each PC and run the updates.
> Thanks!

Can I assume machines are on the same subnet? If not, then without WINS
or lmhosts you won't have a complete list. Browsing relies on NetBIOS so
if you have NetBIOS disabled on any machine it won't show up in the list.
If
you have windows personal firewall enabled or any other personal firewall
enabled, or router blocking NetBIOS the list will be incomplete.

"mathew dalton" <(E-Mail Removed)> wrote in message
news:
> Here is what I got. One Domain, 2 dc's, 6-8 member servers, 50-75
> workstations, xp & 2000 sp4. I am using Symantec 10.00, trying to push to
> an
> update to each client pc. I thought there must be more PC's then I am
> seeing. I use the Symantec tool "find computer" "audit network" there it
> shows PC's that have NOT gotten the update from 8.00 to version 10.00. I
> do
> a print screen and then go to "client remote install" it uses the "my
> network
> places" from the windows OS. I don't see these PC's with (by NetBIOS
> name)
> in the list of PC's under my Domain. There are PC's there just NOT the
> ones
> I am looking for. I go start, run, \\pcname, I see it's shares. I look
> in
> DNS I see the name and IP, \\xxx.xxx.xxx.xxx I see the shares. I look in
> AD,
> the computers are there, they are not in the default OU "computer" BUT
> others
> are in other "OU"'s that I can see in "my network places" so, that can't
> be
> it. WHY AREN'T THESE PCS IN MY NETWORK PLACES? They all use the same
> DHCP
> server getting the same info...
> Please help!!! If I can't push the updates remotely, then I have to go
> out
> and TRY to find each PC and run the updates.
> Thanks!
>

They are all on the same subnet, we are using WINS and it is listed in DHCP.
I looked in my WIN database and don’t see the PCs I am looking for there
either. So I will now go to a PC and see it is a XP firewall causing my
issue. How would you disable NetBIOS for a windows PC? I am not aware of a
service to disable. I dont believe that there any enties in my "LMhost"
file.
Thanks!


"Michael Giorgio - MS MVP" wrote:

> Can I assume machines are on the same subnet? If not, then without WINS
> or lmhosts you won't have a complete list. Browsing relies on NetBIOS so
> if you have NetBIOS disabled on any machine it won't show up in the list.
> If
> you have windows personal firewall enabled or any other personal firewall
> enabled, or router blocking NetBIOS the list will be incomplete.
>
> "mathew dalton" <(E-Mail Removed)> wrote in message
> news:
> > Here is what I got. One Domain, 2 dc's, 6-8 member servers, 50-75
> > workstations, xp & 2000 sp4. I am using Symantec 10.00, trying to push to
> > an
> > update to each client pc. I thought there must be more PC's then I am
> > seeing. I use the Symantec tool "find computer" "audit network" there it
> > shows PC's that have NOT gotten the update from 8.00 to version 10.00. I
> > do
> > a print screen and then go to "client remote install" it uses the "my
> > network
> > places" from the windows OS. I don't see these PC's with (by NetBIOS
> > name)
> > in the list of PC's under my Domain. There are PC's there just NOT the
> > ones
> > I am looking for. I go start, run, \\pcname, I see it's shares. I look
> > in
> > DNS I see the name and IP, \\xxx.xxx.xxx.xxx I see the shares. I look in
> > AD,
> > the computers are there, they are not in the default OU "computer" BUT
> > others
> > are in other "OU"'s that I can see in "my network places" so, that can't
> > be
> > it. WHY AREN'T THESE PCS IN MY NETWORK PLACES? They all use the same
> > DHCP
> > server getting the same info...
> > Please help!!! If I can't push the updates remotely, then I have to go
> > out
> > and TRY to find each PC and run the updates.
> > Thanks!
> >
>
>
>

Go into tcp/ip properties / advanced / WINS and you'll
see the NetBIOS over tcp/ip setting.

"mathew dalton" <(E-Mail Removed)> wrote in message
news:
> They are all on the same subnet, we are using WINS and it is listed in
> DHCP.
> I looked in my WIN database and don't see the PCs I am looking for there
> either. So I will now go to a PC and see it is a XP firewall causing my
> issue. How would you disable NetBIOS for a windows PC? I am not aware of
> a
> service to disable. I dont believe that there any enties in my "LMhost"
> file.

Thanks! I went to two of the PCs on my list; both W2Kstations and both have
the same error when tiring to browse the network "cant access list of
servers". But lucky for me I am the "Server Guy" and the "PC Guy" will work
on these issues I just need to create a report on which PC's are not updating
from the Primary Symantec server.

"Michael Giorgio - MS MVP" wrote:

> Go into tcp/ip properties / advanced / WINS and you'll
> see the NetBIOS over tcp/ip setting.
>
> "mathew dalton" <(E-Mail Removed)> wrote in message
> news:
> > They are all on the same subnet, we are using WINS and it is listed in
> > DHCP.
> > I looked in my WIN database and don't see the PCs I am looking for there
> > either. So I will now go to a PC and see it is a XP firewall causing my
> > issue. How would you disable NetBIOS for a windows PC? I am not aware of
> > a
> > service to disable. I dont believe that there any enties in my "LMhost"
> > file.
>
>
>
>

Well good luck and let us know what the problem was if you
remember.

"mathew dalton" <(E-Mail Removed)> wrote in message
news:
> Thanks! I went to two of the PCs on my list; both W2Kstations and both
> have
> the same error when tiring to browse the network "cant access list of
> servers". But lucky for me I am the "Server Guy" and the "PC Guy" will
> work
> on these issues I just need to create a report on which PC's are not
> updating
> from the Primary Symantec server.
>