How do i configure a 2003 server onto an exising 2003 SBS domain

Help!! I have a new server to install on Thursday, but I need clarification/advice on how to configure the new 2003 server.

Current setup:
Site 1: SBS 2003 server setup with DHCP, DNS, RRAS, Active Directory, and exchange
Site 2: No current server, but all PCs are joined to the SBS domain

Draytek Vigor 2800s with LAN to LAN connection between sites

Required new setup:
Installation of a new 2003 server to run Sage and act as a file and print server for site 2

I have workstations at both sites that require access to both servers and laptop users that also require access to both sites.

The question I have is.... how to setup the new 2003 server?
The customer wants to be able to run both sites, even if the Lan to Lan fails..
Should I install DHCP and DNS on the 2003 server on site 2?  
Will they conflict with the 2003 SBS server at site 1?
DO DNS and DHCP requests get answered over a LAN to LAN?

Any help/advice would be appreciated...

ctlitAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Lee W, MVPTechnology and Business Process AdvisorCommented:
There are directions for adding a second server here:
http://www.lwcomputing.com/tips/linker.asp?id=43
http://www.lwcomputing.com/tips/linker.asp?id=21

As for the second site, I would set it up as a second subnet and then use Sites and Services to define the subnets.  You can then setup DHCP on the server in the second site so that it handles it for all local workstations only.
0
PlaceboC6Commented:
If you are promoting the server as an additional Domain Controller, you don't have to do anything special.  Just DCPromo it as an additional DC for an Existing Domain.

Configure a different subnet at each site.
Create a site in Sites and Services for each site.
Create a subnet in Sites and Services for each site.
Assign the appropriate subnet to each site in Sites and Serves

Install DNS on the new server
Insthall DHCP on new server.
Have new server assign IP's in the subnet for the new site to clients
Have new server assign local server's address for DNS and the SBS server as the alternate DNS

DNS and Authenticate will work across the VPN in the event that a local DC is downed.  Creating the sites/subnets will ensure that local clients use the local DC as priority.
0
ctlitAuthor Commented:
Ok.. Great.. Thanks.. "Wicked response times""  The links to the guides seem to be spot on!! Thanks

So it seems like i need to look in to the sites and services a bit further and also subnets.

Currently site 1 is setup as 192.168.7.0 with 255.255.255.0 as the subnet.
What would you suggest i setup the subnet as, for site 2?
Briefly, how do subnets work?
Will users from site 1 still be able to access the new server at site 2 via the LAN to LAN? and visa versa?
What about the remote dial in users on their laptops? Will they just dial in as normal and be able to access resources on both sites?
0
Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

Lee W, MVPTechnology and Business Process AdvisorCommented:
Subnets separate broadcast domains.  DHCP is a broadcast protocal.  The subnet mask defines what numbers of the IP address are in the broadcast domain.

For example, a subnet mask (commonly used) of 255.255.255.0 means that all the IP Addresses in 192.168.7.x are on the same subnet.  A subnet of 255.255.0.0 would mean that all the addresses of 192.168.x.x are on the same subnet.  
0
PlaceboC6Commented:
So following what leew said,  you could make the subnet at the other site 192.168.6.x...or 192.168.5.x.....
0
ctlitAuthor Commented:
Ok.. So I should setup
Site 1 as 192.168.7.0 / 255.255.255.0
and
Site 2 as 192.168.6.0 / 255.255.255.0

Then configure DHCP and DNS on server 2003 at site 2,

Then I would then need to setup two sites in sites and services, one for both IP schemes.

This would mean that both sites would be able to operate independently of one another if the LAN to LAN went down, but also, that both sites would be able to access resources on each others sites?
Would I join all PCs on site 1 and site 2, to the same active directory domain that is running at site1?
Would I configure all site 2 users on the SBS 2003 box at site 1?

Thanks gents.. Your help is very much appreciated...


0
ryansotoCommented:
Ok.. So I should setup
Site 1 as 192.168.7.0 / 255.255.255.0  (Sure)
and
Site 2 as 192.168.6.0 / 255.255.255.0 (with new sites I like to go higger then the 'main'
site so 192.168.8.X but it doesnt matter)

Then configure DHCP and DNS on server 2003 at site 2,(Yes make sure to set the servers tcpip properties dns server to itself and in DNS set up a forwarder to your ISP DNS)

Then I would then need to setup two sites in sites and services, one for both IP schemes. (Correct)

This would mean that both sites would be able to operate independently of one another if the LAN to LAN went down, but also, that both sites would be able to access resources on each others sites?(Correct.  If LAN 1 went down though LAN 2 could not access resources on LAN 1 but would be able to operate independently if LAN 1 went down)
Would I join all PCs on site 1 and site 2, to the same active directory domain that is running at site1?(Yes since they are all going to be a part of the same domain then yes!)
Would I configure all site 2 users on the SBS 2003 box at site 1?  (After you get Active Directory running, DNS and DHCP configured on the new server then you can join the PC from site 2 if y ou wish.)

Thanks gents.. Your help is very much appreciated...
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ctlitAuthor Commented:
Getting there, thanks... But a bit more information would help...

On the 2003 server, do i dcpromo this server and create a new domain? or do i just make the server a member of the domain? If i just make it a member of the domain, how do i get the avtive directory installed?
At the moment, i do not have active directory installed on the 2003 server so i cannot configure sites and services. How do i proceed to get the active directory installed on the 2003 server?
0
PlaceboC6Commented:
Make sure you configure DNS client on new server to point to SBS server for dns resolution.

Do the DCPROMO on the new server and make it a new DC for an EXISTING domain.  It will ask which domain you are going to be joining and type in the domain name that SBS is on.  Example:   mydomain.local

It will ask for credentials and you will provide a domain admin account from the sbs domain.

Then the server should replicate and reboot.

When it is done,  it will be a DC in the sbs domain.
0
ryansotoCommented:
Why point it to the sbs out of curiosity?
0
ctlitAuthor Commented:
So..
Can i confirm....
The two servers will work independently of each other if the Lan to Lan goes down?
The replication will work over the Lan to Lan? Is there any ports that need to be opened on the firewalls to allow this to work?
Both servers will have DNS DHCP, RRAS, Active Directory, and this is the information that will be replicated between the two servers?

Who do i point the DNS to on server 2003? SBS? Itself? or the ISP DNS?


0
ryansotoCommented:
DNS on the SBS needs to be set to itself in the TCPIP properties then in DNS you set a forward to the ISP's DNS
0
ctlitAuthor Commented:
and on the server 2003 that i am joining to the domain?

Thanks Ryansoto
0
ryansotoCommented:
Per Placebo set its TCP IP settings to the SBS box for DNS.
I dont know if SBS is different in that respect but normally you set each DNS box to point to itself in TCP IP then create a forwarder in DNS console for each machine.

Thats why I asked placebo why set the 2003 box to look at the SBS box for DNS
0
ryansotoCommented:
I didnt get an explnation why not to set the 2003 box DNS up to itself but that it definately should be as Placebo says.  It needs to point to the SBS box

http://download.microsoft.com/download/d/6/d/d6d6391a-eb33-4491-8818-b4422cd373c8/SBSaddmultsrv.doc
Around page 13 or so
0
ctlitAuthor Commented:
Thanks again.. I have more than enough information to instal lthis tomorrow.. Thanks to all of you for your guidance.. Will update you on friday with the results of my adventure in to the unknown!!!

Not sure how this point system works so i am going to accept mutliple solutions from Ryansoto, Placebo and LeeW as you have all contributed.. Cheers....
0
PlaceboC6Commented:
"Why point it to the sbs out of curiosity?"

Because if he is promoting the DC,  he has to be pointing to a DNS server in the domain he is becoming a domain controller for.  Otherwise it will not be able to locate a DC to attach to and replicate with.
0
PlaceboC6Commented:
To follow along with what Ryan was saying:   Never point a domain attached client or server to an ISP for dns resolution.  As Ryan said,  you will configure the forwarders tab on the DNS console of the DNS server itself to point to the ISP....but that is it.
0
ctlitAuthor Commented:
Great...
Thanks for the further updates and explanantions..


0
ctlitAuthor Commented:
all is going well... So far!!!! but i have a few things i need to sort out..

I have joined the 2003 server to the SBS domain after running adprep..
The active directory installed ok and the replication has taken place.

I am unclear about the site and sevrices area.
I have created two sites and two subnets but the servers are currently in the default-first-site-name "site.

Do I move the server object to its new site container?

I have installed DNS and DHCP but cant work out how the local clients pick up an IP address from the local server only

I have linked the subnets to the sites but that is it.. Am i missing something?
0
ryansotoCommented:
0
PlaceboC6Commented:
I assume the new server is configured in the subnet you have set up?

Yes move it into the new site contained with the new subnet.
Configure the DHCP scope to hand out IP addresses in the new subnet only
Configure the DHCP server to hand out the addess of the local dns server as the preferred DNS server.
0
ctlitAuthor Commented:
The new server is configured, up and running and DNS and DHCP are installed..

I have joined some PC's to the domain at the new site and all appears to be working ok...


I have moved the two servers in to their own "new" sites within sites and services, but that is all i have done..
How do i configure the DHCP scope to hand out IP addresses in the new subnet only? and how do I configure the DHCP server to hand out the address of the local dns server as the preferred DNS server?

I have configured the DHCP scope with the correct details for DNS and gateway, within the scope options and the clients are actually getting the correct ip settings, but i have not configured the DHCP scope as detailed above, to give out IP addresses to local PC's only... How is this done?
0
ryansotoCommented:
When you create the scope just set the range for the new subnet.  When the client boots it will broadcast and since its on the new subnet the dhcp will know that it needs to hand out an address from that new subnet range
0
ctlitAuthor Commented:
Your help/quick responses were very much appreciated.. I would not have got through todya without your help..

Thanks again
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows Server 2003

From novice to tech pro — start learning today.