To get rid of the above mentioned logs please follow the below steps. Log Settings. In the category go to firewall settings, click on triangle button. Go to Multicast and disable the alert, If you dont wants to disable the alert then change the Priority to something else from the debug.
Currently I've used a wizard to create a port forward from external IP to service SSH.
Now this rule is setup 100% correct as it's not only automated with the wizard but at the same time I know what I'm doing.
![Firewall Firewall](http://help.sonicwall.com/help/sw/eng/9600/26/2/3/content/images/packet%20capture%20full.png)
So the rule is setup correctly but I cannot connect on port 22 what would be the problem?
![Sonicwall firewall forward packets consume generate free Sonicwall firewall forward packets consume generate free](https://images.g2crowd.com/uploads/product/image/large_detail/large_detail_a91c790d4dcb23f5394f7d7ba650ea65/sonicwall.png)
The internal server has port 22 open and I can connect internally.
The priority of the SSH rule I created is numero uno. I've done some packet monitoring and I've seen multiple dropped flags with numerous error codes. None of which helped or even gave any specific information.
My guess is there is some check box some where that is selected that is making this happen, so if anyone has any ideas please feel free to let me know. My brain is currently out of service as I've been working on this issue for close to 8 hours.
Thanks.
IntelliComp Technologies is an IT service provider.
Ok, at this point we're going to start going into iffy territory. The world of packet capturing is complex and fun :)
Keep in mind we want to capture specific traffic so that we know exactly what's going on. This means that on the TZ105 we want to capture traffic coming FROM 25.0 going TO 6.0. On the NSA220 side we want to capture traffic coming FROM 6.0 going TO 25.0. Depending on what happens with the packets then we'll know where to go next.
Every SonicWALL has a packet monitor under System (three down from the bottom) open that up on the TZ105 and lets configure it as follows (where X is the machine you're pinging from and Y is the machine you're pinging to)
Let's focus on the TZ105 for right now, once you have this configured, start the capture and ping from 192.168.25.x to 192.168.6.y. Refresh the page on the capture to see if traffic is coming through. You should see it being Forwarded or Consumed.