WatchGuard DNSWatch reduces malware infections by detecting and blocking malicious DNS requests, improving your ability to protect employees from phishing attacks. Learn more about our newest service included in Total Security Suite today!
Configuring Server 2008 Domain Controllers for future VPN Use
We are setting up a new network that is actually two locations joined by two VPN routers that provide a constant tunnel. All of the servers are at location 1.
My question is should I configured location 2 servers while they are at location 1? If so, what are the key things that need to happen for success? We are planning to have a DFS setup between both locations, and to allow both sides of the network preform user login/authentication to the same domain.
Theoretically we would like it if one location went down (servers only, not internet/vpn) that the other could then preform the network authentication/login. Obviously it would be very slow, but still something that would be nice.
If I should not configure all the servers at location 1, I'm not seeing the picture perfectly as to how I could join server B to the domain hosted by server A. Since DNS doesn't work automatically over the VPN conneciton.
Location 1 - 10.8.44.x
Location 2 - 10.8.45.x
From either location I can ping by IP Address of a system/server on the other side but not by FQDN currently.
My question is should I configured location 2 servers while they are at location 1? If so, what are the key things that need to happen for success? We are planning to have a DFS setup between both locations, and to allow both sides of the network preform user login/authentication to the same domain.
Theoretically we would like it if one location went down (servers only, not internet/vpn) that the other could then preform the network authentication/login. Obviously it would be very slow, but still something that would be nice.
If I should not configure all the servers at location 1, I'm not seeing the picture perfectly as to how I could join server B to the domain hosted by server A. Since DNS doesn't work automatically over the VPN conneciton.
Location 1 - 10.8.44.x
Location 2 - 10.8.45.x
From either location I can ping by IP Address of a system/server on the other side but not by FQDN currently.
Asked:
3-
3
-
2
1 Solution
First DNS: Since our servers provide DNS, is it not possible to use windows server dns to configure VPN DNS?
Secondly: Say VPN DNS was working fine, I could setup all the servers get everything working fine all at location 1 then change ip addresses and send to location 2. And that wouldn't screw up DFS or Active Directory.
I didn't think you could just "change" a servers IP Address easily without it breaking everything.
Secondly: Say VPN DNS was working fine, I could setup all the servers get everything working fine all at location 1 then change ip addresses and send to location 2. And that wouldn't screw up DFS or Active Directory.
I didn't think you could just "change" a servers IP Address easily without it breaking everything.
ne3,
It's pretty inexpensive (e.g., < $125) to set up a test bench for this.
I'll make the following assumptions:
Current configuration:
Internet
|
ISP Router1
|
Firewall Router
|
Inside Switch
| |
DC1 DC2
To create the test environment, buy a cheap switch and a cheap VPN router. For the latter, something like a Netgear FVS318 or one of the Linksys routers with a V in the model (e.g., WRV54G or BEFVP).
Build the new environment like this:
Internet
|
ISP Router1
|
New cheap switch
| |
VPNRouter Firewall router
| |
DC2 DC1
Using this configuration, you can model a new site config, set up replication rules, etc. without screwing up your existing network and having to drive across the city/state/country to your other location.
It's pretty inexpensive (e.g., < $125) to set up a test bench for this.
I'll make the following assumptions:
Current configuration:
Internet
|
ISP Router1
|
Firewall Router
|
Inside Switch
| |
DC1 DC2
To create the test environment, buy a cheap switch and a cheap VPN router. For the latter, something like a Netgear FVS318 or one of the Linksys routers with a V in the model (e.g., WRV54G or BEFVP).
Build the new environment like this:
Internet
|
ISP Router1
|
New cheap switch
| |
VPNRouter Firewall router
| |
DC2 DC1
Using this configuration, you can model a new site config, set up replication rules, etc. without screwing up your existing network and having to drive across the city/state/country to your other location.
Maybe not relevant for you, and you may have encountered this before, but you might confirm that your clients are configured to use TCP instead of UDP for Kerberos authentication communication. It's a quick registry or GP fix.
See this article:
http://support.microsoft.com/kb/244474
See this article:
http://support.microsoft.com/kb/244474
Yes you must have Windows DNS to run a domain. I'm not understanding why you can't use if you are running through VPN.
DNS across the VPN was not working because there was no Windows DNS server on the other side of the network, as we had not made it to that stage yet.
I've started configuring the servers that will go to Location 2 now, and everything looks like it will work fine. Thanks letting me knock info/ideas out of you.
I've started configuring the servers that will go to Location 2 now, and everything looks like it will work fine. Thanks letting me knock info/ideas out of you.
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
Join & Write a Comment Already a member? Login.
Featured Post
If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.
Tackle projects and never again get stuck behind a technical roadblock.
Join Now
You can create the Domain Controllers at HQ then send to remote location or you can create the DCs at the remote location either way will work. If you create at HQ you would need to change the IP scheme when they got on site.