As Michael said, browsing has nothing to do with domain trusts. You can
see the domain browse list even if you are not on the domain (eg workgroup
members can see the domain browse list and vice versa).
The browse list depends on Netbios names and LAN broadcasts. To browse
across routers or WAN links which block broadcasts you need WINS or LMHOSTS
and at least one domain controller. Browsing is independent of domain (or
any other) credentials, so domain trusts don't come into it at all. It only
depends on the Netbios name of the machine and of the workgroup/domain.
Zer0byte wrote:
> Hi,
>
> If they were DCs? doesnt they need a trust relationship in order they
> can communicate, also doesnt the browsing using lmhosts file needs a
> trust relation. in case if they were DCs?
>
> "Michael Giorgio - MS MVP" wrote:
>
>> You'll need WINS or lmhosts. Have a look at the following
>> MS KB article which explains the browsing process:
>>
>> Domain Browsing with TCP/IP and LMHOSTS Files
>> http://support.microsoft.com/default...b;en-us;150800
>>
>> "Gary" <(E-Mail Removed)> wrote in message news:
>>> I have two domains (1 Windows 2003 and 1 NT4) - no trust
>>> between them. I need to be able to browse machines on both
>>> domains. How can this be setup? There is a firewall/NAT
>>> device between them and I have permitted tcp/udp ports 137-
>>> 139 and 445. Is there anything else required?