NetBIOS browsing across subnets not working

When I look under My Network Places/Entire Network/Microsoft Winblows Network I do not see all my domains and cannot browse some subnets. I have 5 subnets and 6 domains. Each domain is completely contained within it's subnet except for 1 subnet which has 2 domains. If I take a computer from my site and join it to a domain at a remote site I then I start to see that domain under Network Places on all computers at my site. I have WINS set up at each site and in each domain with Push/Pull replication set up. I have a couple of applications that work through NetBIOS and I need to be able to see the remote domains. Can anyone help?

Windows 2000 AD
WINS at each site (push/pull repl)
DHCP at each site/domain
XP/2000 clients at each site


Bradley Fox
Sr. Network Administrator
MCSE - W2K

sounds like master browser issue. any errors in event viewer?

--
For more and other information, go to http://www.ChicagoTech.net

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Robert Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.

"Brad Fox" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
When I look under My Network Places/Entire Network/Microsoft Winblows
Network I do not see all my domains and cannot browse some subnets. I have
5 subnets and 6 domains. Each domain is completely contained within it's
subnet except for 1 subnet which has 2 domains. If I take a computer from
my site and join it to a domain at a remote site I then I start to see that
domain under Network Places on all computers at my site. I have WINS set up
at each site and in each domain with Push/Pull replication set up. I have a
couple of applications that work through NetBIOS and I need to be able to
see the remote domains. Can anyone help?

Windows 2000 AD
WINS at each site (push/pull repl)
DHCP at each site/domain
XP/2000 clients at each site


Bradley Fox
Sr. Network Administrator
MCSE - W2K



--------------------------------------------------------------------------------


When I look under My Network Places/Entire Network/Microsoft Winblows
Network I do not see all my domains and cannot browse some subnets. I have
5 subnets and 6 domains. Each domain is completely contained within it's
subnet except for 1 subnet which has 2 domains. If I take a computer from
my site and join it to a domain at a remote site I then I start to see that
domain under Network Places on all computers at my site. I have WINS set up
at each site and in each domain with Push/Pull replication set up. I have a
couple of applications that work through NetBIOS and I need to be able to
see the remote domains. Can anyone help?

Windows 2000 AD
WINS at each site (push/pull repl)
DHCP at each site/domain
XP/2000 clients at each site


Bradley Fox
Sr. Network Administrator
MCSE - W2K

Hi Brad,

Could be any number of reasons but without a few more
details it would be hard to advise.. If you open My Network
Places (MNP) in the problem subnets what exactly do you
see? Open the WINS server on your subnet and verify the
domain name 1b mappings pertaining to the problem domains
are present. The PDC of your subnet will query the 1b entries
in WINS to find other domain master browsers in order to get
their domain browse lists.


"Brad Fox" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
When I look under My Network Places/Entire Network/Microsoft Winblows
Network I do not see all my domains and cannot browse some subnets. I
have 5 subnets and 6 domains. Each domain is completely contained
within it's subnet except for 1 subnet which has 2 domains. If I take
a computer from my site and join it to a domain at a remote site I then
I start to see that domain under Network Places on all computers at my
site. I have WINS set up at each site and in each domain with Push/Pull
replication set up. I have a couple of applications that work through
NetBIOS and I need to be able to see the remote domains. Can anyone
help?

Windows 2000 AD
WINS at each site (push/pull repl)
DHCP at each site/domain
XP/2000 clients at each site


Bradley Fox
Sr. Network Administrator
MCSE - W2K

From my site I queried all 1b records from all WINS owners at all sites. What I found was that the sites that do not show in my MNP do not have any 1b records. If I remote to a computer at one of the sites with no 1b records I cannot see any other domains.

Bradley Fox
Sr. Network Administrator
MCSE - W2K

>>> Michael Giorgio - MS MVP<(E-Mail Removed)> 07/28/04 11:00AM >>>
Hi Brad,

Could be any number of reasons but without a few more
details it would be hard to advise.. If you open My Network
Places (MNP) in the problem subnets what exactly do you
see? Open the WINS server on your subnet and verify the
domain name 1b mappings pertaining to the problem domains
are present. The PDC of your subnet will query the 1b entries
in WINS to find other domain master browsers in order to get
their domain browse lists.


"Brad Fox" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
When I look under My Network Places/Entire Network/Microsoft Winblows
Network I do not see all my domains and cannot browse some subnets. I
have 5 subnets and 6 domains. Each domain is completely contained
within it's subnet except for 1 subnet which has 2 domains. If I take
a computer from my site and join it to a domain at a remote site I then
I start to see that domain under Network Places on all computers at my
site. I have WINS set up at each site and in each domain with Push/Pull
replication set up. I have a couple of applications that work through
NetBIOS and I need to be able to see the remote domains. Can anyone
help?

Windows 2000 AD
WINS at each site (push/pull repl)
DHCP at each site/domain
XP/2000 clients at each site


Bradley Fox
Sr. Network Administrator
MCSE - W2K

That is kind of what I figured. <g>
Now to find out why. If the WINS
servers are PDCs make sure they
are configured to point towards
themselves as primary and secondary
in their tcp/ip properties \ WINS. Next
you could open a dos prompt from any
server and run nbtstat -A against the
tcp/ip address of the problem PDCs
which will open the local name table
and verify the 1b name is not in conflict.
Also make sure none of the PDCs are
configured as a router between the subnets.
Those are just a couple off the top of my
head.

"Brad Fox" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
From my site I queried all 1b records from all WINS owners at all sites.
What I found was that the sites that do not show in my MNP do not have
any 1b records. If I remote to a computer at one of the sites with no
1b records I cannot see any other domains.

The WINS server in question is a DHCP and DC (im guessing that's what you mean by PDC since this is 2k AD there is no actual PDC) for a very small remote office. It's WINS address does point back at itself. When I nbtstat -A on it's IP i get no 1b records at all, however there are no other names listed except the domain name and the NetBIOS name. I've tried from itself and a couple of other servers and my XP laptop. I appreciate your help so far.



Bradley Fox
Sr. Network Administrator
MCSE - W2K

>>> Michael Giorgio - MS MVP<(E-Mail Removed)> 07/28/04 04:39PM >>>
That is kind of what I figured. <g>
Now to find out why. If the WINS
servers are PDCs make sure they
are configured to point towards
themselves as primary and secondary
in their tcp/ip properties \ WINS. Next
you could open a dos prompt from any
server and run nbtstat -A against the
tcp/ip address of the problem PDCs
which will open the local name table
and verify the 1b name is not in conflict.
Also make sure none of the PDCs are
configured as a router between the subnets.
Those are just a couple off the top of my
head.

"Brad Fox" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
From my site I queried all 1b records from all WINS owners at all sites.
What I found was that the sites that do not show in my MNP do not have
any 1b records. If I remote to a computer at one of the sites with no
1b records I cannot see any other domains.

Hi Brad,
automatically preload all required records for network browsing across subnets using LMHOSTS file. In LMHOSTS file place following records for all domains and DCs. Record 1b must have domain name 15 chars long (for example "domaina" and 8 spaces ended by \0x1b) ! Copy the same file on every DC in your network.

Sample:

10.0.1.1 "DOMAINA \0x1b" #PRE
10.0.1.1 ADC1 #PRE #DOMOMAINA
10.0.1.2 ADC2 #PRE #DOMOMAINA

10.0.2.1 "DOMAINB \0x1b" #PRE
10.0.2.1 BDC1 #PRE #DOMOMAINB
10.0.2.2 BDC2 #PRE #DOMOMAINB

Ros


"Brad Fox" <(E-Mail Removed)> wrote in message news:%(E-Mail Removed)...
The WINS server in question is a DHCP and DC (im guessing that's what you mean by PDC since this is 2k AD there is no actual PDC) for a very small remote office. It's WINS address does point back at itself. When I nbtstat -A on it's IP i get no 1b records at all, however there are no other names listed except the domain name and the NetBIOS name. I've tried from itself and a couple of other servers and my XP laptop. I appreciate your help so far.



Bradley Fox
Sr. Network Administrator
MCSE - W2K

>>> Michael Giorgio - MS MVP<(E-Mail Removed)> 07/28/04 04:39PM >>>
That is kind of what I figured. <g>
Now to find out why. If the WINS
servers are PDCs make sure they
are configured to point towards
themselves as primary and secondary
in their tcp/ip properties \ WINS. Next
you could open a dos prompt from any
server and run nbtstat -A against the
tcp/ip address of the problem PDCs
which will open the local name table
and verify the 1b name is not in conflict.
Also make sure none of the PDCs are
configured as a router between the subnets.
Those are just a couple off the top of my
head.

"Brad Fox" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
From my site I queried all 1b records from all WINS owners at all sites.
What I found was that the sites that do not show in my MNP do not have
any 1b records. If I remote to a computer at one of the sites with no
1b records I cannot see any other domains.

Certainly the PDC thing isn't important in AD. But browsing is an NT
legacy service and it certainly matters to it. The first/only DC in a domain
is the PDC emulator and will become the domain master browser, and should
register the <domainname 1b> entry in WINS.

"Brad Fox" <(E-Mail Removed)> wrote in message
news:#(E-Mail Removed)...
The WINS server in question is a DHCP and DC (im guessing that's what you
mean by PDC since this is 2k AD there is no actual PDC) for a very small
remote office. It's WINS address does point back at itself. When I
nbtstat -A on it's IP i get no 1b records at all, however there are no other
names listed except the domain name and the NetBIOS name. I've tried from
itself and a couple of other servers and my XP laptop. I appreciate your
help so far.



Bradley Fox
Sr. Network Administrator
MCSE - W2K

>>> Michael Giorgio - MS MVP<(E-Mail Removed)> 07/28/04
04:39PM >>>
That is kind of what I figured. <g>
Now to find out why. If the WINS
servers are PDCs make sure they
are configured to point towards
themselves as primary and secondary
in their tcp/ip properties \ WINS. Next
you could open a dos prompt from any
server and run nbtstat -A against the
tcp/ip address of the problem PDCs
which will open the local name table
and verify the 1b name is not in conflict.
Also make sure none of the PDCs are
configured as a router between the subnets.
Those are just a couple off the top of my
head.

"Brad Fox" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
From my site I queried all 1b records from all WINS owners at all sites.
What I found was that the sites that do not show in my MNP do not have
any 1b records. If I remote to a computer at one of the sites with no
1b records I cannot see any other domains.



----------------------------------------------------------------------------
----


The WINS server in question is a DHCP and DC (im guessing that's what you
mean by PDC since this is 2k AD there is no actual PDC) for a very small
remote office. It's WINS address does point back at itself. When I
nbtstat -A on it's IP i get no 1b records at all, however there are no other
names listed except the domain name and the NetBIOS name. I've tried from
itself and a couple of other servers and my XP laptop. I appreciate your
help so far.



Bradley Fox
Sr. Network Administrator
MCSE - W2K

>>> Michael Giorgio - MS MVP<(E-Mail Removed)> 07/28/04
04:39PM >>>
That is kind of what I figured. <g>
Now to find out why. If the WINS
servers are PDCs make sure they
are configured to point towards
themselves as primary and secondary
in their tcp/ip properties \ WINS. Next
you could open a dos prompt from any
server and run nbtstat -A against the
tcp/ip address of the problem PDCs
which will open the local name table
and verify the 1b name is not in conflict.
Also make sure none of the PDCs are
configured as a router between the subnets.
Those are just a couple off the top of my
head.

"Brad Fox" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
From my site I queried all 1b records from all WINS owners at all sites.
What I found was that the sites that do not show in my MNP do not have
any 1b records. If I remote to a computer at one of the sites with no
1b records I cannot see any other domains.

In W2k or higher the first DC is usually the PDC FSMO
role holder but it's possible to transfer this role to other DCs.
The PDC emulator registers the domain name 1b unique
name locally.

You could locate the PDC emulator and in each
domain and see if something maybe blocking NBT.

How to Find the FSMO Role Owners Using ADSI and WSH
http://support.microsoft.com/default...b;en-us;235617

MS recommends the WINS server point towards itself for it's
primary and secondary WINS servers in the tcp/ip properties.


"Brad Fox" <(E-Mail Removed)> wrote in message news:
The WINS server in question is a DHCP and DC (im guessing that's what
you mean by PDC since this is 2k AD there is no actual PDC) for a very
small remote office. It's WINS address does point back at itself. When
I nbtstat -A on it's IP i get no 1b records at all, however there are no
other names listed except the domain name and the NetBIOS name. I've
tried from itself and a couple of other servers and my XP laptop. I
appreciate your help so far.

Thanks Ros, and Michael! I used the sample from below (actually first line only) to create 1b records for all PDC emulator in the forest and imported it into my wins server and forced replication. This seems to have fixed the issue. Thanks again guys!!

Bradley Fox
Sr. Network Administrator
MCSE - W2K

>>> Ros<(E-Mail Removed)> 07/28/04 09:20PM >>>

Hi Brad,
automatically preload all required records for network browsing across subnets using LMHOSTS file. In LMHOSTS file place following records for all domains and DCs. Record 1b must have domain name 15 chars long (for example "domaina" and 8 spaces ended by \0x1b) ! Copy the same file on every DC in your network.

Sample:

10.0.1.1 "DOMAINA \0x1b" #PRE
10.0.1.1 ADC1 #PRE #DOMOMAINA
10.0.1.2 ADC2 #PRE #DOMOMAINA

10.0.2.1 "DOMAINB \0x1b" #PRE
10.0.2.1 BDC1 #PRE #DOMOMAINB
10.0.2.2 BDC2 #PRE #DOMOMAINB

Ros


"Brad Fox" <(E-Mail Removed)> wrote in message news:%(E-Mail Removed)...
The WINS server in question is a DHCP and DC (im guessing that's what you mean by PDC since this is 2k AD there is no actual PDC) for a very small remote office. It's WINS address does point back at itself. When I nbtstat -A on it's IP i get no 1b records at all, however there are no other names listed except the domain name and the NetBIOS name. I've tried from itself and a couple of other servers and my XP laptop. I appreciate your help so far.



Bradley Fox
Sr. Network Administrator
MCSE - W2K

>>> Michael Giorgio - MS MVP<(E-Mail Removed)> 07/28/04 04:39PM >>>
That is kind of what I figured. <g>
Now to find out why. If the WINS
servers are PDCs make sure they
are configured to point towards
themselves as primary and secondary
in their tcp/ip properties \ WINS. Next
you could open a dos prompt from any
server and run nbtstat -A against the
tcp/ip address of the problem PDCs
which will open the local name table
and verify the 1b name is not in conflict.
Also make sure none of the PDCs are
configured as a router between the subnets.
Those are just a couple off the top of my
head.

"Brad Fox" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
From my site I queried all 1b records from all WINS owners at all sites.
What I found was that the sites that do not show in my MNP do not have
any 1b records. If I remote to a computer at one of the sites with no
1b records I cannot see any other domains.