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

Sonicwall, PRO3060, VPN traffic going only one way

I have a VPN tunnel going from a TZ170 to a PRO 3060 and eveything seems okay at first. The tunnel is coming up green on both ends and I can ping from the TZ170 to the 3060. However, if I try to ping the other way it fails.
When I go into the diagnostics on the 3060 if I do a packet trace going from my computer behind the 3060 to the LAN address of the TZ170, it shows it as being successful. The logs on the 3060 are showing the ping as:
source: TZ170
destination: PRO3060
destination unreachable.

So it's like the ping is going out successfully but then on the return it's getting blocked by the 3060. I've tried making a rule to allow all communication from the TZ170, but it still fails.

I've also lowered the MTU and adjusted it to match on both sides, deleted and recreated the rule for the SA, etc, etc.
Can anyone tell me why the ping would fail but packet trace is showing successful? I need the tunnel to work both ways.. :)
0
wlandymore
Asked:
wlandymore
  • 2
1 Solution
 
budchawlaCommented:
Have you got authentication required for the tunnel on the TZ170?
0
 
wlandymoreAuthor Commented:
Nice.

I added authentication to the list of exempted services on both sides and it started coming up for ping, etc.

Thanks...I never would have thought of that.
0
 
budchawlaCommented:
Glad to help :-)
0
 
humancapCommented:


(Quote)I added authentication to the list of exempted services on both sides and it started coming up for ping, etc.

Thanks...I never would have thought of that(Quote)

Sorry to bother you but could you tell me how you added authentication to the list of exempted service?
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.

Join & Write a Comment

Featured Post

Simple Misconfiguration =Network Vulnerability

In this technical webinar, AlgoSec will present several examples of common misconfigurations; including a basic device change, business application connectivity changes, and data center migrations. Learn best practices to protect your business from attack.

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