Browsing Computers in Trusted Domains

Here's a question my colleagues and I have been tinkering with for a bit.

We recently set up a Trust Relation between our offices in Houston, TX
(Windows Server 2003) and Kendal, England (Windows NT4 Server). The
main issue we run into is the fact that we cannot browse each other's
domain. In fact, they don't even show up in our Network Neighborhood/My
Network Place's Entire Network.

We can manually get to computers via \\ComputerName via the Run prompt,
but if we try going back up a level to see the domain, we get an error
telling us it could not be browsed. Of course, we can browse our own
respective domains, but we cannot browse the other's domain.

Our respective Domain Admins group has been added to each other's domain
to ensure we can access each other's resources okay.

Can any shed some light on this subject? Thank you.

If you make your wins servers replication partners with each other or use
lmhosts files you should be able to browse each other's networks then. The
browse service [My Network Places] used netbios over tcp/ip and is broadcast
based unless wins is used. Broadcasts usually do not go across routers. The
browse masters for each network [typically domain controllers - pdc in
particular] need to be able to find each other to combine browse lists. The
links below should help. The first one shows how the browser service
orks. --- Steve

http://www.microsoft.com/resources/d...i_brs_oynw.asp

http://support.microsoft.com/?kbid=150800
http://support.microsoft.com/?kbid=188001


"Travis Tubbs" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Here's a question my colleagues and I have been tinkering with for a bit.
>
> We recently set up a Trust Relation between our offices in Houston, TX
> (Windows Server 2003) and Kendal, England (Windows NT4 Server). The main
> issue we run into is the fact that we cannot browse each other's domain.
> In fact, they don't even show up in our Network Neighborhood/My Network
> Place's Entire Network.
>
> We can manually get to computers via \\ComputerName via the Run prompt,
> but if we try going back up a level to see the domain, we get an error
> telling us it could not be browsed. Of course, we can browse our own
> respective domains, but we cannot browse the other's domain.
>
> Our respective Domain Admins group has been added to each other's domain
> to ensure we can access each other's resources okay.
>
> Can any shed some light on this subject? Thank you.