Subnets & Domains

[C M]

Hi,

I have two Domains one is using Fixed IP Addresses and the other is using DHCP.

Can i the two domains to see & talk to each other as if they were on the same IP Range.

Thanx.

CM,

[Adriweb]

Sure! I does depend though.
Are the systems on static IP's all on the same network? Are the static and DHCP domains connected through a Router?

If they are on the same collision domain and the static systems are all on the same network, you can give the other systems DHCP addresses on that domain (configure the DHCP server this way).

If the 2 networks are connected are connected through a Router, just configure the Router.

[C M]

All the systems are on the same Network....they will use the same router to connect to the internet..

Thanx for your fast reply.

CM

[Pakrat]

Are these NT Domains or Internet Domain Names?

With NT Domains you can create a Trust between the two domains that will allow you to use the other as if it were on your domain.

Internet Domain Name, If you install NetBEUI, then you can file and print share very easily. But, you should be able to use NetBIOS over TCP/IP without any problems. Except that you will not be able to use My Network Places/Network Neighborhood. Well, you may be able to if you configure a WINS Server or LMHOSTS.

[C M]

They are both to be Windows 2000 Active Directory Domains.

One Domain will run fixed IP Addresses and the other will use DHCP Addresses.

This is due to Network expansion so we are creating a second domain using DHCP to free Fixed IP Addresses up.

They run on the same wiring,everything will run the same.

With the Domains running Different Subnets & IP Addresses will it be able to create a Trust Relationship?

Thanx

CM

[Pakrat]

"With the Domains running Different Subnets & IP Addresses will it be able to create a Trust Relationship? "

As long as there is a router connecting both subnets the domains should be able to talk to each other and trust each other just fine. I don't know how easily this is done, and I don't know if the primary domain controller(s) can act as a router. But I think it is more than possible.

[C M]

We have a Router that goes out to the Internet for our Leased line connection...would this be the one i would need to configure?

Or would it require a seperate new Router.

Thanx.

CM.

[RingoSaturn]

You may be able to use the current router. Does it have more than one "port" on it. If you had, say, two ethernet ports on the router, you could segregate the two networks by putting all the computers from one network one one hub, then all the computers from the other network on a different hub, then plug each of the hubs into a seperate ethernet port on the router.
Then, you could configure the router with static routes to route the packets from one port to the other as needed (or, you could keep them from speaking together completely, if you wanted that.

[Silicon Scream]

If you have two domains, one with static IP's and one with dynamic you need to do the following in an Active Directory network...


Configure

1)Your router obviously needs to have its settings in place

2)Use Active Directory Sites and Services to setup replication among your domains (ie domain controllers). Remember, replication in a site among multiple domain controllers is replicated based on changes, but replication between sites is done on a schedule basis. By setting up sites, this allows your clients have a clue as to what server to use when logging on. Also, after creating your sites, subnets, and linking them in Active Directory Sites and Services, MAKE SURE TO SPECIFY A GLOBAL CATALOG SERVER IN EACH SITE. Otherwise you'll have clients still logging on with a server in another site. At home this is no big deal, but in an office where one site is in Australia and one is in Boston, you'll take upwards of 4 or 5 minutes to login.

Active Directory Sites and Services not only does replication, but ties your network together so clients know where network resources are.

3)DNS zones. Just right click your DNS server in each domain (you should probably run at least two in a network for fault tolerance) using the DNS management console and choose properties and then specify the DNS server to use Active Directory. I'm not sure how you're setup now, but if you're using two domains, it's probably easier to simply 'Delegate' another server in another domain as a DNS server rather than trying to link two domains as two forests together. Your namespace will then appear as follows:

Where your first DNS Server is... example.com
Where your 2nd DNS Server is...second.example.com

4)Name resolution. If you're not using down-level clients (Win9x/ME or heaven forbid WFWG) you could eliminate WINS, but not w/o some additional configuring. It would probably be easier to setup a WINS box in each site and set them up as 'Push/Pull' partners. DNS will already be setup, so no need to go into that.

5)Clients. If you want to use DynamicDNS, setup your DHCP server on the site (subnet) that it's on to register clients in DNS rather than having your 2K clients do it. This accomplishes two things here:
a) You add some security to your network by allowing only your 'authorized DHCP server to register clients in DNS.
b) You have no need to configure clients to do this other than setting them up to use DHCP which is already setup by default.


Don't worry about

1)Trust relationships. In an Active Directory network, all trusts are created two-way 'transitive' BY DEFAULT. This means that each domain trusts one another. Windows NT4 this wasn't the case.

2)DNS replication. Again, since you're running Active Directory Integrated, DNS information is replicated as an object in Active Directory. Separate DNS replication is not needed.