• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 230
  • Last Modified:

Should my 2003 SBServer (DC) be the DHCP / DNS server when I plan to config endpoint VPN RV016 tunnels?

Hi all
I'm preparing to install a new 2003SBServer at our main office with a Linksys RV016 router.   I intend to configure VPN endpoint tunnes from several (3 for now) remote job sites that will have RV042 routers.  My question is who should be the DHCP / DNS server for the LANS.  It would seem logical to allow the routers to be the DHCP and DNS server, and not the server...I'm thinking in case the tunnel goes down, or is slow, etc.  I should mention our remote sites are all wireless laptops, and will need to RD a terminal server that will be joined to the new domain.  They will also receive pop3 email / internet outside of the tunnel.  I have a static IP at the main office, but not at the remote sites.

Any advice on this project would be greatly appreciated...any tips from someone who has set this up on the RV series routers.
Thanks
0
JDCTECH
Asked:
JDCTECH
  • 2
  • 2
1 Solution
 
NoodlesWIUCommented:
This is really a matter of oppinion for most.  But having DHCP on the server I generally chose.  An example would be if the router was down for whatever reason, now your DHCP is down as well because you were using it via the router, this could cause issues for the clients in the office then.  Where as if you have it on the SBS server, well, if the servers down you have bigger problems than to worry about DHCP.

I think most would agree this is just a matter of preference though.
0
 
QBRadCommented:
i agree with noodles, go with the server option.  you should also put a smaller less powerful DC at the remote sites, this could be a cheap desktop supplying DHCP, DNS, and DC functions such as authentication at teh remote site so if the line is down its not that big of a deal and it will save bandwidth on the line since this traffic is local to the office.

2 good thiings for one cheap desktop DC.  easily justified.  
0
 
QBRadCommented:
Also if 1 DC dies you rebuild and dcpromo and done.  you dont have to start from scratch or reload from tape.

3 good things
0
 
JDCTECHAuthor Commented:
My understanding is that you want to have a different 3rd octet at each remote office such as:
Main Office 192.168.1.x
1st Remote Office 192.168.2.x
2nd Remote Office 192.168.3.x
etc...
So shouldn't I configure the server at the main office to DHCP that office an then use the routers dhcp at the remote offices?  This is the first time I've confingured VPN router endpoints, though I've set up software (windows) VPN many times to connect to a server directly.
Thanks
0
 
NoodlesWIUCommented:
Thats correct.  If you use the same IP scheme your VPN is going to choke.  So do as you stated, one office with 192.168.1.x, the other with 192.168.2.x, etc.

Your right on target, the remote offices you can use the VPN router for DHCP if you desire.  But nothing is stopping you if you have a server at your other offices to use DHCP with the scheme you mentioned above.  Again, just preference, and what is ever easier for you.

Good Luck!
0

Featured Post

NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

  • 2
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now