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

Join domain over Pix vpn tunnel

Hello all,

Having an issue here.  I am setting up a second domain controller in Canada to our Win2003 domain in the US.
I have setup a  Pix site to site VPN tunnel and it seems to be working fine.  I can ping both networks from either side by IP.
The DC in the US is running AD and DNS.  The DC in Canada cannot join the domain to configure AD and replication yet.
I have pointed the Canada DNS to itself as primary and to the DC in the US as secondary.  I have setup forwarders to their ISPs DNS for internet and added a DNS suffix for the domain name.  Nothing should be blocking traffice on the Pixes because it's my understanding that all ESP traffic from the tunnel is allowed both ways.  What am I doing wrong?  
1 Solution
you may want to verify with your ISP, because some don't allow tunneling. I had that issue as well...

I have had same problem with Windows 2003 AD servers and wanting to join a other location to the AD thrue a VPN. I use SonicWall TZ170 Firewall's in both locations and Netbios traffic was blokked on the VPN tunnel. After allowing this traffic I was able to connect to the remote AD and join it. So you can temporarily allow NetBios traffic on the VPN tunnel.  When this traffic is allowed it's more likely you can join the domain in the other location. After the join process is finished you can disable Netbios traffic again of you want.
rick_me27Author Commented:
hmm...  anyone know how to enable netbios traffic on a Pix?   Worth a shot.  
The Firewall Audit Checklist

Preparing for a firewall audit today is almost impossible.
AlgoSec, together with some of the largest global organizations and auditors, has created a checklist to follow when preparing for your firewall audit. Simplify risk mitigation while staying compliant all of the time!

Netbios broadcasts cannot be propogated across the VPN tunnel through the PIX.
If you can ping both ways, you have a simple netbios name resolution issue. With AD, you should be able to join the domain if you point the Ca DC to the US DC as primary DNS....
Some helpful links:
Windows 2000 DNS - Diagnosing Name Resolution Problems
FQDN = Fully Qualified Domain Name

Windows 2000 DNS - Solving other common DNS problems

rick_me27Author Commented:
jeez, I hope it's that simple.  I'm gonna test that and try it right now.
rick_me27Author Commented:
Yessssssssssssss.   that worked.  Beating my head for two days on cisco and it's as simple as that.  I should have known.
Thanks lrmoore
Glad to help!

- Cheers!
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

Featured Post

Get 10% Off Your First Squarespace Website

Ready to showcase your work, publish content or promote your business online? With Squarespace’s award-winning templates and 24/7 customer service, getting started is simple. Head to Squarespace.com and use offer code ‘EXPERTS’ to get 10% off your first purchase.

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