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

Sonicwall NSA 3500 - public server wizard results in dropped packets

I have a sonicwall NSA 3500 sitting at a collocation center.
x0, Lan,, sits on lan vlan
x1, Wan,, sits on wan vlan
x2, Dmz, bridged x1, sits on dmz vlan (works fine)

I have a private server, that I want to redirect port 80, 443 requests to.  I've used the public server wizard and it only results in Drop Code 32 Module Id 26 in packet monitor.  I cannot for the life of me get these requests to be accepted and translated.

I have a similar configuration that I used public server to setup for> and it works great.  Just this new public + private IP do not work.  The private server is accepting requests on both ports.

I have an email server with a public IP on the DMZ vlan that works fine too, although it isn't using public server wizard settings, just firewall rules to allow the traffic through.
  • 3
2 Solutions
What is the SonicOS version.

You have /24 address for WAN, wow.
Don't use the wizard and try to do it manually, first create network objects for servers external and internal addresses, then create a 1-to-1 nat policy for incoming traffic, then create an access rule for incoming top 80 and 443 traffic.

Check the link below for how to

The meaning of SonicWall Dropcode and Module ID varies with firmware version. On SonicOS Enhanced, Drop Code 32 means "Invalid connection cache", Module Id 26 means Network.

"Drop Code 32 Module Id 26" relates to dropped SSH/HTTPS session.

For more information on Drop Code and Module ID on SonicOS - Here

Sonicwall support documentation on port forwarding - Here
kzsigoAuthor Commented:
I tried deleting all of the wizard rules, address objects, and setting them up manually but it did not take, same result.  

I saw the names behind the codes document, but I don't know how to solve the connection cache issue.  It's not the standard firewall blocked rule.  

I changed my DMZ X2 to Transparent mode, and my public servers all of a sudden work; I don't get the drop code, and the packets are forwarded/natted, even load balanced.  

However, now the server that is on the DMZ cannot communicate out X1 (originating from X2).   I'll ask a new question for that.  Thanks.
Please inform the SonicOS firmware version with your question.
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

Train for your Pen Testing Engineer Certification

Enroll today in this bundle of courses to gain experience in the logistics of pen testing, Linux fundamentals, vulnerability assessments, detecting live systems, and more! This series, valued at $3,000, is free for Premium members, Team Accounts, and Qualified Experts.

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