holcomb_frank
asked on
two domains on the same flat network
We have an office with an sbs 2003 domain controller, we will call this domain1 and the server name is server01. We are closing another office but want to move it's server, another domain controller for that office to our current location. This is an SBS2011 box and the server name is server01. This is domain2.
So can we have the two domain controllers for our two different domains run on the same network. Domain1 is the SBS2003 box, server01.local.domain1 and it's ip address is 192.168.1.2. We add Domain2, SBS20011 box, server01.local.domain2 to our existing network and make it's ip 192.168.1.5. Of course different workstations are members of each domain.
Will we have any issues as a result of running two different domain controllers over the same network? Will the server names cause a problem since they both are server01 but specific to their own domains? We don't need the two to talk to each other, just use the same infrastructure.
So can we have the two domain controllers for our two different domains run on the same network. Domain1 is the SBS2003 box, server01.local.domain1 and it's ip address is 192.168.1.2. We add Domain2, SBS20011 box, server01.local.domain2 to our existing network and make it's ip 192.168.1.5. Of course different workstations are members of each domain.
Will we have any issues as a result of running two different domain controllers over the same network? Will the server names cause a problem since they both are server01 but specific to their own domains? We don't need the two to talk to each other, just use the same infrastructure.
Even then, I could see issues occuring in all sorts of ways. I am hoping that they are NOT both called server01and that this is just the names given by the asker as examples within the question.
ASKER
CrisHana,
The goal would be to have both staffs working in the same building.......and yes be able to share the internet connection. As you know I can't rename the DC....... seperated by routers??
The goal would be to have both staffs working in the same building.......and yes be able to share the internet connection. As you know I can't rename the DC....... seperated by routers??
ASKER
yes both servers are named server01 with different domain names due to the two orginal office locations that are not being combined?
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.
ASKER
Ok... we got the other server in house now and it's different then we were told. Actually the original dc is named server01.domain01.local. The other server, which we have not set up yet is actually named server03.domain.local. " Domain" is the same on both servers so the distinction is domain vs. domain01.
Given that..... do you still see the same issues now. The servers actually have two different names. They would just be using similar ip schemes. 10.1.x.x for both.
Again the main goal here is to share the internet connection between both domains. There is no port issues that i can see....all connections to this network are through a VPN.
Could this work without messing up either server.??
Given that..... do you still see the same issues now. The servers actually have two different names. They would just be using similar ip schemes. 10.1.x.x for both.
Again the main goal here is to share the internet connection between both domains. There is no port issues that i can see....all connections to this network are through a VPN.
Could this work without messing up either server.??
so both domains share the same domain.local domainname? I understand that they are actually unique domains but if they have the same domainname...DNS is going to be the problem as well DHCP...The only way they get pointed to the correct location is static DNS addresses for each client.
You still haven't indicated how you're going to deal with mail inbound with 1 external IP
You still haven't indicated how you're going to deal with mail inbound with 1 external IP
ASKER
Chris,
Mail is not an issue for this location...it's not hosted in house. It's all webemail.
The dc's are server01.bob.local and server03.bob01.local......
What do you think...?? I can turn off dhcp on the original dc, everything is static on that box.....and the only reason for internet on that box would be updates.
Mail is not an issue for this location...it's not hosted in house. It's all webemail.
The dc's are server01.bob.local and server03.bob01.local......
What do you think...?? I can turn off dhcp on the original dc, everything is static on that box.....and the only reason for internet on that box would be updates.
I think you can make this work for the short term, but the long term goal here should be one network with one domain.
ASKER
Chris,
The only thing I can see happening right now is a limited amount of IP addresses due to the same 10.1.1.x segment will be shared by both servers.
Dc old 10.1.1.2 and Dc new 10.1.1.5....... there is going to be about 25 workstations total so I'm not to concerned about the IP's but that was my biggest question now.
It would seem that the DC names are different enough that it shouldn't be an issue....each workstation will go to it's appropriate dc by it's membership right??
I agree....long term planning is to combine these two sites if it stays this way.
The only thing I can see happening right now is a limited amount of IP addresses due to the same 10.1.1.x segment will be shared by both servers.
Dc old 10.1.1.2 and Dc new 10.1.1.5....... there is going to be about 25 workstations total so I'm not to concerned about the IP's but that was my biggest question now.
It would seem that the DC names are different enough that it shouldn't be an issue....each workstation will go to it's appropriate dc by it's membership right??
I agree....long term planning is to combine these two sites if it stays this way.
Maybe I am just too old now to look long-term at workarounds but I guess you are not in a position to be overly choosy at the moment.
I think you will have some some strange issues to overcome with naming and services etc but as you don't seem to have many choices........
I think you will have some some strange issues to overcome with naming and services etc but as you don't seem to have many choices........
Personally I'd put them on different IP ranges...really easy to do with SBS 2011
Absolutely
ASKER
Chris,
And still use the same gateway ??
And still use the same gateway ??
You'd have to change the subnet to 255.255.0.0 and should be able to get to the gateway
ASKER
Sorry for the delay....busy, busy...
Ok...what i did was log into the existing SBS2003 box and i turned off dhcp all together. Then I selected a range of Ip's that would give this group everything they needed including their printers and everyone is now on a static ip address with in this specific range. All the stations are running fine and not having any issues at this point. Then we brought in the SBS2011 box and set it up with Dhcp and set up the scope to exclude the specific range that the other network is using and of course reserved the ips of each server and their router so there would be no issues there. Each server is still running it's own DNS and Wins for that matter.
Both servers are up and working on the same network. At this point all the workstations are still on the original SBS2003 box, but as we set up the SBS2011 network all the workstations are connecting without any issues. So far so good and this was Tuesday of last week.
I can remote back and fourth within in the two servers from one to another or from a workstation to either server with the correct credentials.
No one is complaining of network issues or speeds....so this is good for us.
Both servers have access to the network printers and gateway. Since email is all web based at this time, and no one uses RWW or anything like that. Port forwarding has not been an issue. We connect to our office location using a VPN and then remote directly to the server. I can do this on both servers right now as well.
Keeping my fingers crossed....so far this is working good for me.
Ok...what i did was log into the existing SBS2003 box and i turned off dhcp all together. Then I selected a range of Ip's that would give this group everything they needed including their printers and everyone is now on a static ip address with in this specific range. All the stations are running fine and not having any issues at this point. Then we brought in the SBS2011 box and set it up with Dhcp and set up the scope to exclude the specific range that the other network is using and of course reserved the ips of each server and their router so there would be no issues there. Each server is still running it's own DNS and Wins for that matter.
Both servers are up and working on the same network. At this point all the workstations are still on the original SBS2003 box, but as we set up the SBS2011 network all the workstations are connecting without any issues. So far so good and this was Tuesday of last week.
I can remote back and fourth within in the two servers from one to another or from a workstation to either server with the correct credentials.
No one is complaining of network issues or speeds....so this is good for us.
Both servers have access to the network printers and gateway. Since email is all web based at this time, and no one uses RWW or anything like that. Port forwarding has not been an issue. We connect to our office location using a VPN and then remote directly to the server. I can do this on both servers right now as well.
Keeping my fingers crossed....so far this is working good for me.
ASKER
Thanks for everyone for feedback.... so far so good.
At a minimum, these networks need to be separated by routers