Cannot browse child domain computers and vice versa

I cannot browse machine in child domain except the Child
domain AD itself from any user desktop machine. Current
Network setup is Main AD(something.com) running dns and
dchp 172.20.x.x. Child domain AD(child.something.com) is
in different subnet 172.21.x.x running its own AD, dhcp
and DNS and has 2 NIC's in there one connecting to child
domain switch and the second one connecting to 172.20.x.x
switch. On the 172.20.x.x subnet a win2003 is doing
routing and on 172.21.x.x subnet the AD with 2 nic is
doing routing. I can ping by name and IP Address of any
machine from any of the two domain from any users desktop.
But I just can't browse machine through network
neighborhood. Someone know on how to fix this issue please
help me.

Thanks
Sura

The browsing list is built through broadcasts which cannot pass through
router. The easiest fix would be to install a WINS server on each subnet,
then make sure that they are set to replicate with each other.

"Sura" <(E-Mail Removed)> wrote in message
news:911a01c3eaa3$2fb9a410$(E-Mail Removed)...
> I cannot browse machine in child domain except the Child
> domain AD itself from any user desktop machine. Current
> Network setup is Main AD(something.com) running dns and
> dchp 172.20.x.x. Child domain AD(child.something.com) is
> in different subnet 172.21.x.x running its own AD, dhcp
> and DNS and has 2 NIC's in there one connecting to child
> domain switch and the second one connecting to 172.20.x.x
> switch. On the 172.20.x.x subnet a win2003 is doing
> routing and on 172.21.x.x subnet the AD with 2 nic is
> doing routing. I can ping by name and IP Address of any
> machine from any of the two domain from any users desktop.
> But I just can't browse machine through network
> neighborhood. Someone know on how to fix this issue please
> help me.
>
> Thanks
> Sura

Network Neighborhood doesn't really have much to do with AD or DNS. It
relies on the browser service, which in turn relies on broadcasts and
Netbios names.

To browse across a router, you will almost certainly need WINS, so that
your segment master browsers can find each other across the router (which
blocks broadcasts).

You will almost certainly have browser problems if you are routing
through a DC. This is a long-standing no-no! (Formerly knows as the
multihomed browser or multihomed PDC problem in NT).

So to get this working, you will need to disable Netbios over TCP/IP on
all but one interface of the multihomed DC. And you will need WINS working
network wide . This involves either one WINS server for the entire network
(with all machines registering with it), or a WINS server in each domain set
up to replicate.

"Sura" <(E-Mail Removed)> wrote in message
news:911a01c3eaa3$2fb9a410$(E-Mail Removed)...
> I cannot browse machine in child domain except the Child
> domain AD itself from any user desktop machine. Current
> Network setup is Main AD(something.com) running dns and
> dchp 172.20.x.x. Child domain AD(child.something.com) is
> in different subnet 172.21.x.x running its own AD, dhcp
> and DNS and has 2 NIC's in there one connecting to child
> domain switch and the second one connecting to 172.20.x.x
> switch. On the 172.20.x.x subnet a win2003 is doing
> routing and on 172.21.x.x subnet the AD with 2 nic is
> doing routing. I can ping by name and IP Address of any
> machine from any of the two domain from any users desktop.
> But I just can't browse machine through network
> neighborhood. Someone know on how to fix this issue please
> help me.
>
> Thanks
> Sura

Thanks a Lot. It worked !!

>-----Original Message-----
> Network Neighborhood doesn't really have much to do
with AD or DNS. It
>relies on the browser service, which in turn relies on
broadcasts and
>Netbios names.
>
> To browse across a router, you will almost certainly
need WINS, so that
>your segment master browsers can find each other across
the router (which
>blocks broadcasts).
>
> You will almost certainly have browser problems if
you are routing
>through a DC. This is a long-standing no-no! (Formerly
knows as the
>multihomed browser or multihomed PDC problem in NT).
>
> So to get this working, you will need to disable
Netbios over TCP/IP on
>all but one interface of the multihomed DC. And you will
need WINS working
>network wide . This involves either one WINS server for
the entire network
>(with all machines registering with it), or a WINS
server in each domain set
>up to replicate.
>
>"Sura" <(E-Mail Removed)> wrote in message
>news:911a01c3eaa3$2fb9a410$(E-Mail Removed)...
>> I cannot browse machine in child domain except the
Child
>> domain AD itself from any user desktop machine. Current
>> Network setup is Main AD(something.com) running dns and
>> dchp 172.20.x.x. Child domain AD(child.something.com)
is
>> in different subnet 172.21.x.x running its own AD, dhcp
>> and DNS and has 2 NIC's in there one connecting to
child
>> domain switch and the second one connecting to
172.20.x.x
>> switch. On the 172.20.x.x subnet a win2003 is doing
>> routing and on 172.21.x.x subnet the AD with 2 nic is
>> doing routing. I can ping by name and IP Address of any
>> machine from any of the two domain from any users
desktop.
>> But I just can't browse machine through network
>> neighborhood. Someone know on how to fix this issue
please
>> help me.
>>
>> Thanks
>> Sura
>
>
>.
>