Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 916
  • Last Modified:

How to setup an VPN on a TZ170 to an NSA3500

Site A - Primary Office has an NSA 3500 SonicOS Enhanced 5.6.0.5-46o
NSA has a full DNS resolve & public IP

Site B - Remote Office has a TZ170 SonicOS Standard 3.1.5.0-2s

I want to connect workstations from Site B to Site A's netowrk & serve remote office Site A IPs via the Site A DHCP.

I can connect workstations via the SSLVPN SonicWall Netestender Client but I've never setup a VPN & I can't figure out what gateway goes where & what the networks are.

On both the TZ170 & NSA 3500 I have the IPSec Primary Gateway Name or Address: <Site A NSA IP & Site A "destination" network>

On the NSA Network Tab my LAN is "Firewalled Subnets" & the remote netowrk is the Site B's NSA Network Address Object with the Site B's IP address in that object.

On both "Advanced" Tab both have Enable Keep Alive & Enable Win Networking (NetBIOS) Broadcast.

I'm stuck - help

0
spongebobzach
Asked:
spongebobzach
  • 2
1 Solution
 
carlmdCommented:
Use the wizard on the Sonicwall (upper right hand corner of pages), select other and then site to site tunnel. This will walk you through it.
0
 
digitapCommented:
also, looking at the logs of the sonicwall appliances, you should get some feedback as to where it's failing in negotiating the tunnel. phase 1 or phase 2. can you post that information?
0
 
spongebobzachAuthor Commented:
Yes I checked the logs & it revealed the issue & I spoke with SonicWall & they explained the gateways have be each have the other's IP and their own local network. But I started in the logs so thanks.
0
 
digitapCommented:
you're welcome. thanks for the points!
0

Featured Post

 The Evil-ution of Network Security Threats

What are the hacks that forever changed the security industry? To answer that question, we created an exciting new eBook that takes you on a trip through hacking history. It explores the top hacks from the 80s to 2010s, why they mattered, and how the security industry responded.

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