Manually opening Ports / enabling Port forwarding to allow traffic from the Internet to a Server behind the SonicWall using SonicOS involves the following steps:

CREATING THE NECESSARY ADDRESS OBJECTS

1. Log into the SonicWall GUI.
2. Click Manage in the top navigation menu.
3. Click Objects | Address Objects.
4. Click the Add a new Address object button and create two Address Objects for the Server’s Public IP and the Server’s Private IP.
5. Click OK to add the Address Object to the SonicWall’s Address Object Table.
   

 CREATING THE NECESSARY SERVICE OBJECT

1. Click Manage in the top navigation menu
2. Click Objects | Service Objects.
3. Click the Add a new Service object button and create the necessary Service Objects for the Ports required.
4. Ensure that you know the correct Protocol for the Service Object (TCP, UDP, etc.). If you’re unsure of which Protocol is in use, perform a Packet Capture.
5. Click OK to add the Service Object to the SonicWall’s Service Object Table.
   

CREATING THE APPROPRIATE NAT POLICIES WHICH CAN INCLUDE INBOUND, OUTBOUND, AND LOOPBACK

A NAT Policy will allow SonicOS to translate incoming Packets destined for a Public IP Address to a Private IP Address, and/or a specific Port to another specific Port. Every Packet contains information about the Source and Destination IP Addresses and Ports and with a NAT Policy SonicOS can examine Packets and rewrite those Addresses and Ports for incoming and outgoing traffic.

1. Click Manage in the top navigation menu.
2. Click Rules | NAT Policies.
3. Click the Add a new NAT Policy button and a pop-up window will appear.
4. Click Add to add the NAT Policy to the SonicWall NAT Policy Table.

    NOTE: When creating a NAT Policy you may select the “Create a reflexive policy” checkbox. This will create an inverse Policy automatically, in the example below adding a reflexive policy for the NAT Policy on the left will also create the NAT Policy on the right. This option is not available when configuring an existing NAT Policy, only when creating a new Policy.

   
   Loopback NAT Policy
   A Loopback NAT Policy is required when Users on the Local LAN/WLAN need to access an internal Server via its Public IP/Public DNS Name. This Policy will “Loopback” the Users request for access as coming from the Public IP of the WAN and then translate down to the Private IP of the Server. Without a Loopback NAT Policy internal Users will be forced to use the Private IP of the Server to access it which will typically create problems with DNS.
   If you wish to access this server from other internal zones using the Public IP address Http://1.1.1.1 consider creating a Loopback NAT Policy:

• Original Source: Firewalled Subnets
• Translated Source: X1 IP
• Original Destination: X1 IP
• Translated Destination: Example Name Private
• Original Service: HTTPS
• Translated Service: Original
• Inbound Interface: Any
• Outbound Interface: Any
• Comment: Loopback policy
• Enable NAT Policy: Checked
• Create a reflexive policy: Unchecked
  

 CREATING THE NECESSARY FIREWALL ACCESS RULES

1. Click Manage in the top navigation menu.
2. Click Rules | Access Rules.
3. Select the View Type as Matrix and select your WAN to Appropriate Zone Access Rule. (This will be the Zone the Private IP of the Server resides on.)
4. Click the Add a new entry/Add… button and in the pop-up window create the required Access Rule by configuring the fields as shown below.
5. Click Add when finished..