Want to join server to domain across VPN tunnel

Greetings.

Here's my scenario:
- The domain controller, a Windows 2003 server, is server1.domain.location1
- The domain controller is dual-homed, with an IP on the router side of 192.168.1.100, and an IP on the LAN side of 192.168.8.12. It is the Internet gateway and performs NAT for the network at location1
- The VPN router at location1 has an IP address of 192.168.1.1.
- I also promoted the remote server, also a Windows 2003 server, to a DC, because it didn't seem that DNS ran correctly until I did so. The remote server is server2.domain.location2.
- The remote server has an IP of 10.0.1.150. It is not dual homed. The gateway is the VPN router at location2, with an IP of 10.0.1.1.
- All clients at location2 as well as the server (anything on the 10.0.1.x subnet) can see anything on the 192.168.1.x subnet at location1.

I'd like to join server2.domain.location2 to the domain.location1 domain. Iid also like for clients at location2 to be able to resolve server names for any servers on the 192.168.1.x subnet at location1. If possible, I'd even like them to be able to see the 192.168.8.x subnet at location1.

Thanks in advance for any help.

Joe
dekroonAsked:
Who is Participating?
 
Computer101Connect With a Mentor Commented:
PAQed with points refunded (500)

Computer101
Community Support Moderator
0
 
weareitCommented:
Try using this document to get you off on the right foot:

http://support.microsoft.com/kb/816514

-saige-
0
 
weareitCommented:
This article explains branch deployments using only dual homed 2003 servers (not what you were asking about but a good read):

http://technet2.microsoft.com/windowsserver/en/library/90a91d65-9448-4114-971e-654fa398269d1033.mspx?mfr=true

-saige-
0
Improved Protection from Phishing Attacks

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!

 
dekroonAuthor Commented:
k - thx, saige

In my time crunch i was hoping for something specific to my scenario, but I'll read for lack of any other suggestions
0
 
weareitCommented:
I have no comments to make...  The user never made a follow-up comment after saying that he would read the materials provided...

-saige-
0
 
dekroonAuthor Commented:
I read them, and neither one of those articles applied to my scenario, saige. The VPN tunnel is already built.

Joe
0
 
weareitCommented:
Is your VPN tunnel endpoint to endpoint (router to router) or server to server/router?

-saige-
0
 
dekroonAuthor Commented:
It's router to router.
0
 
dekroonAuthor Commented:
Turns out that the problem is my dual-homed architecture at the main branch. I'm double natting, so that's making the IP routing impossible. I will be changing this network architecture and that should do the trick.
0
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.

All Courses

From novice to tech pro — start learning today.