Windows Forum

Ask something
Discussion Locked

Net neiborghood - browsing domains

0 helpful
5 replies

by ticoloco

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

We have a pdc and bdc hosted at site A, and a number of identical NT servers, PDCs at our branches; each of these remote LANs have their own domain and no BDC; also they have their own shares and user databases which is a pain for administration. These branches are connected via Frame Relay

What I want to accomplish is to be able to browse (network neighborhood) those remote domains from site's A domain and make available some shares to the branches and of course include security to them.
How do I need to setup the TCP/IP for each server?
What are the steps to do this? where can I find them?

This is what I have:
Site A domain: domainA
remote branch domain: domainR_xx (xx being a #)

Elliott

5 replies

by timwalsh

You need to set up a series of Trust relationships between your domains.

First, types of trusts:
1. One-way Trust - Domain A trusts Domain B. If a user success in Domain B successfully logs on and authenticates, Domain A will also accept that the user is successfully authenticated. However, the opposite is not true. Domain B does not accept users from Domain A as being properly authenticated.
2. Two-way Trust ? Domain A trusts Domain B; Domain B trusts Domain A. Each domain will accept users from the other domain as being properly authenticated.

Trust relationships in NT are not transitive. This means that if Domain A trusts Domain B, and Domain B trusts Domain C, Domain A does not automatically trust Domain C. Explicit Trusts must be set up between any pair of domains.

Security: once a trust relationship between domains is established, this does not automatically give users in domain access to shared resources in another with one exception. Any resource that has the ?Everyone? access permission enabled is automatically available to users in any domain that is trusted. Other than that exception, the domain administrator must explicitly set access permissions for users in trusted domains. Also an administrator in one domain cannot exercise admin privileges in another domain unless explicitly allowed by the administrator in that domain.

TCP/IP is not really an issue other than making sure that DNS is properly functioning in the various domains.

Fora step-by step, look at the following TechNet article:

http://www.microsoft.com/technet/treeview/default.asp?url=/TechNet/prodtechnol/winntas/proddocs/
concept/xcp01.asp

(Remove any spaces from the above URL)

Scroll down to the section titled ?Administering Trust Relationships.?

Good Luck.

by david.funnell

Tim's answer near enough gives you the answer any security problems, except that windows browsing is performed via WINS and not DNS.

This discussion is closed to new replies.