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.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
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
It doesn't matter if your remote sites use a lower IP range as your main site. Just as long as it is a different subnet. (I'm assuming you're using a 255.255.255.0 subnet mask)
Unless your planning on expanding very fast (more than 500 - 1000 workstations) I wouldn't worry to much about your IP ranges. What you have now is fine.
I would NOT create separate domains for each site. You can establish separate sites in AD to control replication and separate OUs to divide users. Again, unless your network is going to get very big, there is no reason to create a separate domain or forest.
As far as adding the remote DC to the domain, If you have decent bandwidth, I would install it at the remote site and add it there. Sometimes it can create headaches when you try to change the IP address of a DC.
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 ?
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/wi
http://www.google.com/sear
Business Accounts
Answer for Membership
by: bhnmiPosted on 2008-02-01 at 07:09:05ID: 20797095
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.