Copyleft
asked on
Windows Server 2003 - IP ranges
I'm preparing a bunch of new Windows Server 2003 machines.
Three willl go in at our main branch and the fourth will be at another property.
A LAN to LAN VPN joins the two.
Currently we have 10.0.10.3 as our main server (primary login point with Exchange and AD).
File and application servers are 10.0.10.4 and 10.0.10.5 respectively.
On our old setup the other server in building 2 was on 10.0.0.2
For some reason my head is saying go up in the current servers range, to the tune of 10.0.11.xxx
Does it make a difference ?
I'm looking for the easiest and most efficient way to join servers on different ranges and at different locations so that those logged in at our smaller building can see shares on the main network.
Should I join the standalone server as a DC on the current LAN and then take it to its new home or try and join the domain over VPN ?
The only time Ive done this before was with Windows Server 2000 and I used 10.0.10.1 (for the sake of example) for the primary network with 10.0.11.1 for the satellite server.
Detail would be appreciated here, both on the best IP solution and the most effective way to join the servers.
Thanks in advance.
Three willl go in at our main branch and the fourth will be at another property.
A LAN to LAN VPN joins the two.
Currently we have 10.0.10.3 as our main server (primary login point with Exchange and AD).
File and application servers are 10.0.10.4 and 10.0.10.5 respectively.
On our old setup the other server in building 2 was on 10.0.0.2
For some reason my head is saying go up in the current servers range, to the tune of 10.0.11.xxx
Does it make a difference ?
I'm looking for the easiest and most efficient way to join servers on different ranges and at different locations so that those logged in at our smaller building can see shares on the main network.
Should I join the standalone server as a DC on the current LAN and then take it to its new home or try and join the domain over VPN ?
The only time Ive done this before was with Windows Server 2000 and I used 10.0.10.1 (for the sake of example) for the primary network with 10.0.11.1 for the satellite server.
Detail would be appreciated here, both on the best IP solution and the most effective way to join the servers.
Thanks in advance.
Every location should have a different subnet. Then you can establish a site to site VPN. I would create child domains at each location if the pipe between sites is at lest a t1. If not, I would create a separate forest at each site and create a trust.
As long as your subnet is correct, you can use the third octet to specify building location. 10.0.10.X = building one, 10.0.11.X = building two and so on. As long as your subnet mask is setup to include all the ranges that you will be using then you'll be ok. Use an online subnet calc to determine what the best subnet mask for your network will be to make your network traffic run efficiently.
Cheers,
Shoota
Cheers,
Shoota
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
The subnet thing has me a lttle confused.
Currently we use 10.0.10.3 / 255.255.255.0 for our main server at the main building. The others are 10.0.10.4 and 10.0.10.5 and are both obviously also on 255.255.255.0
Building 2 is on 10.0.0.2 / 255.255.255.0
It all works well and has for some years now.
Are you saying I need to change the subnet mask as well as the IP range ?
Currently we use 10.0.10.3 / 255.255.255.0 for our main server at the main building. The others are 10.0.10.4 and 10.0.10.5 and are both obviously also on 255.255.255.0
Building 2 is on 10.0.0.2 / 255.255.255.0
It all works well and has for some years now.
Are you saying I need to change the subnet mask as well as the IP range ?
ASKER
Despite the other helpful replies I'm giving the points to brakk0 for a more rounded answer that worked perfectly in this case.
Thanks for all the input
Thanks for all the input
The subnets you have set up now are fine until you get over 150 - 200 workstations at either location.
Subnets in a nutshell:
255.255.255.0 is a subnet mask
10.0.10.0 through 10.0.10.255 is a subnet (a group of hosts that can talk directly with each other)
10.0.0.0 though 10.0.0.255 is another subnet
The subnet mask is used by each host when establishing connections to other hosts. It tells them whether the destination is on the same subnet (local lan) or a different subnet (remote lan). If it is local, packets are addressed directly to the destination. If it is remote, packets are sent to the default router to be directed to their destination.
http://en.wikipedia.org/wiki/Subnetwork
http://www.google.com/search?q=subnetting
Subnets in a nutshell:
255.255.255.0 is a subnet mask
10.0.10.0 through 10.0.10.255 is a subnet (a group of hosts that can talk directly with each other)
10.0.0.0 though 10.0.0.255 is another subnet
The subnet mask is used by each host when establishing connections to other hosts. It tells them whether the destination is on the same subnet (local lan) or a different subnet (remote lan). If it is local, packets are addressed directly to the destination. If it is remote, packets are sent to the default router to be directed to their destination.
http://en.wikipedia.org/wiki/Subnetwork
http://www.google.com/search?q=subnetting