Joining two Windows domain into one subnet.
We're merging with another company. Two companies will share offices, but for a while, we're going to maintain two separate domains in one network. The hosting company says they won't create VLAN, so we put domain controllers,servers and workstations all together to single subnet which I doubt it will work.
Two companies have their own Windows Active Directory forest and domain. What is the things that I have to prepare?
Our domain spec:
Windows 2003 Forest and domain level.
2 DCs, Windows 2003
1 DC runs DHCP, DNS
Hosting domain spec:
Not sure, probably Windows 2008 or 2012 forest and domain level.
2 DCs, Windows 2012
Sonicwall router runs DHCP
First, DHCP.
The hosting company says, I have to get rid of our DHCP server when we all move in. They have DHCP running in their router (Sonicwall) and we run DHCP in one of domain controllers and has the DNS option 006 setup. They want us to get IPs from their Sonicwall DHCP.
Is there any problem using one DHCP server for two domains and the DHCP server is Sonicwall DHCP server?
Second, DNS
It brings up the issue with DNS server.
In Sonicwall DHCP server, it can have upto 3 DNS servers. How do clients on both domain know what DNS servers are for their domain? Maybe we can use their DNS server, but how two AD integrated domains can be configured on a server which is also the hosting company's DC?
Third, DC log in
If DNS server problem can be solved by setting up two domains in one Widnwos DNS server, then it comes to Domain controllers for workstations to log in. How clients find their correct DC to login?
Fourth, Exchange server.
Is it possible for one 2010 exchange server to host two AD domains?
Two companies have their own Windows Active Directory forest and domain. What is the things that I have to prepare?
Our domain spec:
Windows 2003 Forest and domain level.
2 DCs, Windows 2003
1 DC runs DHCP, DNS
Hosting domain spec:
Not sure, probably Windows 2008 or 2012 forest and domain level.
2 DCs, Windows 2012
Sonicwall router runs DHCP
First, DHCP.
The hosting company says, I have to get rid of our DHCP server when we all move in. They have DHCP running in their router (Sonicwall) and we run DHCP in one of domain controllers and has the DNS option 006 setup. They want us to get IPs from their Sonicwall DHCP.
Is there any problem using one DHCP server for two domains and the DHCP server is Sonicwall DHCP server?
Second, DNS
It brings up the issue with DNS server.
In Sonicwall DHCP server, it can have upto 3 DNS servers. How do clients on both domain know what DNS servers are for their domain? Maybe we can use their DNS server, but how two AD integrated domains can be configured on a server which is also the hosting company's DC?
Third, DC log in
If DNS server problem can be solved by setting up two domains in one Widnwos DNS server, then it comes to Domain controllers for workstations to log in. How clients find their correct DC to login?
Fourth, Exchange server.
Is it possible for one 2010 exchange server to host two AD domains?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
as you are sharing a signle subnet, the clients will have to share DNS servers, if you point to the DNS of domain A, domain B clients can't login and vice versa...
hence the suggestion for an interim DNS server (e.g. Linux bind) with conditional forwarders to both domains.
Now I do not know how to migrate SQL to a newer version, for Exchange you will have to follow an elaborate upgrade path. Are tehse all on separate servers? or are you using an all-in-one SBS?
Re-iping will be a bitch....
hence the suggestion for an interim DNS server (e.g. Linux bind) with conditional forwarders to both domains.
Now I do not know how to migrate SQL to a newer version, for Exchange you will have to follow an elaborate upgrade path. Are tehse all on separate servers? or are you using an all-in-one SBS?
Re-iping will be a bitch....
ASKER
Spoor,
Why do I need 3rd DNS server, can I just set conditional forwarding on the domain A and domain B?
We'll retire our current SQL server and Exchange server eventually, also our domain as well. We'll move our users in Domain B to Domain A in 4-6 months.
Why do I need 3rd DNS server, can I just set conditional forwarding on the domain A and domain B?
We'll retire our current SQL server and Exchange server eventually, also our domain as well. We'll move our users in Domain B to Domain A in 4-6 months.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
how many users are there in Domain B?
perhaps easier to "move" the users already to domain B. Setup a trust between domain A& B for file share access etc, and have the Exchange for Domain B also accept email for Domain A?
just thinking out loud
perhaps easier to "move" the users already to domain B. Setup a trust between domain A& B for file share access etc, and have the Exchange for Domain B also accept email for Domain A?
just thinking out loud
ASKER
Domain A is the hosting company and Domain B is us moving into the office.
Only 80 users in domain B. The hosting company won't start the migration for next 3 months for some business matters.
That's another thing I have to, trusting domains between and B to share printers and files.
For emails, Domain B will continue using its Exchange Server 2003 until migration is finished. Once it's done around April or June next year, Domain A will have new AD users and mailboxes in the Exchange 2010 in Domain A.
Only 80 users in domain B. The hosting company won't start the migration for next 3 months for some business matters.
That's another thing I have to, trusting domains between and B to share printers and files.
For emails, Domain B will continue using its Exchange Server 2003 until migration is finished. Once it's done around April or June next year, Domain A will have new AD users and mailboxes in the Exchange 2010 in Domain A.
ok. then I guess you are stuck with Domain A being the primary touch for DNS and all you would need is DNS forwarders configured.
That and the hosting company to setup one-to-one NAT for your own Exchange server.
Although more ideal would be if they just use a separate VLAN for Domain B....
That and the hosting company to setup one-to-one NAT for your own Exchange server.
Although more ideal would be if they just use a separate VLAN for Domain B....
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Anyway, so for the interim period, in order to run my domain in their subnet, will conditional forwarding in DNS is necessary.
Is that all anyone can think of?
More comments appreciated.
Basically our domain is a very simple single forest and domain in Windows 2003.
1 Exchange serer 2003
2 SQL 2008
2 Windows member servers (Custom built Hyper-V hosting server)
5 Windows member servers (file server, backup server, phone server, etc). 2 DCs, DHCP, DNS hosting