Solved

VPN: ASA to SonicWall

Posted on 2013-12-23
6
541 Views
Last Modified: 2014-01-06
Hey EE,

Having an issue with pinging internal LAN machines behind a Sonicwall firewall from a server behind the ASA.   I have a site to site Cisco ASA 5505 to a Sonicwall at the other end.   VPN is up and passing traffic, but on the server I can not ping the internal behind the Sonicwall.  I can ping the Sonicwall Gateway 192.168.1.1, but after that nothing on LAN side behind Sonicwall is pinging.  

ASA side:
Can ping Sonicwall gateway 192.168.1.1
But can not ping anything behind the Sonicwall.  

Any clue?
0
Comment
Question by:ilivegolive
  • 4
  • 2
6 Comments
 

Author Comment

by:ilivegolive
ID: 39736683
Inside the Sonicwall firewall I see VPN to LAN, and LAN to VPN access allowed.  The ASA is receiving and transmitting and on the firewall, VPN is active.
0
 
LVL 10

Expert Comment

by:convergint
ID: 39736714
So clients from the Sonicwall side can ping the server and other clients on the ASA side?
0
 

Author Comment

by:ilivegolive
ID: 39736726
Hey convergint, - forgot to mention that.  No client behind the Sonicwall can ping the server behind the ASA.  But.....the Sonicwall can ping the server.   So from the Sonicwall GUI interface tool, the server is pingable, but the LAN PCs are not able to.  The LAN PCs are plugged into a switch.  They get internet access just cant ping the server or the subnet the server lives on.
0
Don't miss ATEN at NAB Show April 24-27!

Visit ATEN at NAB Show to learn how our "Seamlessly Entertaining" solutions deliver fast, precise video streaming without delays for the broadcasting and media environment. ATEN will showcase its 16x16 Modular Matrix Switch (VM1600) and KVM Over IP Solution (KE6900 series).

 
LVL 10

Accepted Solution

by:
convergint earned 500 total points
ID: 39736733
It sounds like the NAT routing is not setup properly on the ASA.  The Sonicwalls will automatically add a route to the VPN connections but the ASA's do not.
0
 

Author Comment

by:ilivegolive
ID: 39738456
Hey convergint -

The current ACL is

access-list CUSTOMER extended permit ip 10.15.213.87 255.255.255.224 192.168.1.0 255.255.255.0

Traffic is being received and sent.  I was figuring it could be something up with the Sonicwall as the ASA can ping the Sonicwall and the Sonicwall can ping the ASA.

10.15.213.87 is where the server lives behind the ASA.  192.168.1.0 the LAN behind the Sonciwall with .1 being the gateway.
0
 

Author Comment

by:ilivegolive
ID: 39759429
This has been resolved.  Rebuilt the tunnel on the ASA.  Traffic is passing through to the LAN behind the Sonicwall now.  Not sure to sure what happened.  Before I rebuilt the tunnel, i saw traffic passing just fine.  But the interesting part is, the traffic that was passing was very small.  But after I rebuilt the tunnel, the traffic received and sent was very large.  Thanks convergint, i feel it could have been something goofed with the Access List / NAT
0

Featured Post

Flexible connectivity for any environment

The KE6900 series can extend and deploy computers with high definition displays across multiple stations in a variety of applications that suit any environment. Expand computer use to stations across multiple rooms with dynamic access.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I've attached the XLSM Excel spreadsheet I used in the video and also text files containing the macros used below. https://filedb.experts-exchange.com/incoming/2017/03_w12/1151775/Permutations.txt https://filedb.experts-exchange.com/incoming/201…

679 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question