Filter
Top Products
Network > NAT Policies
263
SonicOS Enhanced 4.0 Administrator Guide
Note With previous versions of firmware, it was necessary to write rules to the private IP
address. This has been changed as of SonicOS 2.0 Enhanced. If you write a rule to
the private IP address, the rule does not work.
Go to the Firewall > Access Rules page and choose the policy for the ‘WAN’ to ‘Sales’ zone
intersection (or, whatever zone you put your serves in). Click on the ‘Add…’ button to bring up
the pop-up window to create the policies. When the pop-up appears, enter the following values:
• Action: Allow
• Service: servone_public_port (or whatever you named it above)
• Source: Any
• Destination: WAN IP Address
• Users Allowed: All
• Schedule: Always on
• Logging: checked
• Comment: (enter a short description)
And:
• Action: Allow
• Service: servtwo_public_port (or whatever you named it above)
• Source: Any
• Destination: WAN IP Address
• Users Allowed: All
• Schedule: Always on
• Logging: checked
• Comment: (enter a short description)
When you’re finished, attempt to access the webservers via the SonicWALL’s WAN IP address
using a system located on the public Internet on the new custom port (example: http://
67.115.118.70:9100 and http://67.115.118.70:9200). You should be able to successfully
connect. If not, review this section, and the section before, and ensure that you have entered
in all required settings correctly.
Using NAT Load Balancing
This section contains the following subsections:
• “NAT Load Balancing Topology” on page 263
• “Prerequisites” on page 264
• “Configuring NAT Load Balancing” on page 265
• “Troubleshooting NAT Load Balancing” on page 269
NAT Load Balancing Topology
Figure 1 shows the topology for the NAT load balancing network.