Return to index


There are 2 ways to provide browsing between NT domains.

1) If configured to use WINS, Domain Master Browsers (always the PDC of an NT domain) will periodically query WINS for a list of all "domainname 1B" entries. Each 1B entry indicates the existence of an NT domain. For each 1B entry it finds, the DMB will add the associated domain name to its browse list.

Note. The DMB will only obtain 1B entries from WINS. It will not search for them in its lmhosts file or its NetBIOS name cache.

If multiple domains are configured to use a common WINS system (either a single WINS server or partnered servers, each DMB will register a domain 1B entry for its domain in the WINS system. When each DMB queries WINS, it will find the 1Bs for all of the other domains and add them to its browse list.

If the domains each use an independent WINS system, there is an alternative that appears to work (I haven't seen any verification of this in MS docs). On each WINS system, add a static 1B entry for the remote domain.

2) On each TCP/IP subnet, there will be a Segment Master Browser for each domain/workgroup. Segment Master Browsers periodically introduce themselves to one another via broadcasts on their local subnet. So if a given subnet contains more than one domain SMB, these SMBs will eventually become aware of one another's domain. Each SMB will pass this information along to its DMB along with the rest of the local browse list.

In this manner, the DMB becomes aware of the existence of the foreign domain. The DMB adds this information to its domain browse list and passes the full list along to the other domain SMBs.

Note. At this point, all domain machines should see the foreign domain in their browse list. However, unless you provide some form of name resolution (WINS, lmhosts, DNS, etc.), many of your clients may be unable to actually connect to any of the machines in the foreign domain.