Menu

Join the Conversation

To sign in, use your existing MySonicWall account. To create a free MySonicWall account click "Register".

Sign In Register

NSA3600 to AWS

gsittongsitton Newbie ✭
in Mid Range Firewalls

Hey there,

Not getting help on the AWS side so seeing if my issue is on the Sonicwall side.

I have my NSA3600 connected to AWS using the AWS features on it. Everything connected fine except.

Our location has multiple buildings with different subnets. AWS can ping only on and from my location AWS can only be pinged if you are on that one subnet. All other subnets are unreachable.

I have the routes on the AWS side and everything looks good. Just don't know if I'm missing something simple.


Thanks.

Category: Mid Range Firewalls
Reply

Answers

  • MustafaAMustafaA SonicWall Employee

    Hi @gsitton

    Since you are mentioning about static route policies, I am assuming you are using Tunnel Interfaces with AWS. Do you have the route policy in place for those subnets that you cannot reach? The best path to troubleshoot this would be to trace the packet flow with the Packet Monitor tool.

  • gsittongsitton Newbie ✭

    I am. They do have a policy for all routes I need.

    I'll try that, did a tracert and it does show it's going where it shouldn't but not sure why.

Sign In or Register to comment.