The SonicWALL NSA 240 UTM Appliance does not support the Windows Home Server automatic router configuration over UPnP standards. You must manually configure Port Forwarding to your Windows Home Server.
Manufacturer: SonicWALLModel: NSA 240Firmware Version: SonicOS Enhanced 5.4.1.0
Open your browser and navigate to your SonicWALL LAN IP Address. Authenticate with the password information set during the Setup Wizard.
By default, http://192.168.168.168
In the SonicOS, an Address Object is one of four object classes (Address, User, Service and Schedule). These Address Objects allow for entities to be defined one time, and to be re-used in multiple referential instances throughout the SonicOS interface.a) Expand the Network node on the left hand side navigation menu and click on “Address Objects”.
b) Under the Address Object section, click on “Add..” and add the following Address Entry, where IP Address refers to the IP address we will assign to the Windows Home Server.
Name: HomeServerZone Assignment: LAN (The WHS is connected to the GbE switch on the LAN side)Type: HostIP Address: 10.0.0.1
a) Expand the Network node and click on “DHCP Server”.b) Under DHCP Server Lease Scopes click on “Add Static” and reserve a IP address for your Windows Home Server based on the MAC Address. The static IP Address must be the same IP address assigned to your Windows Home Server address object during step 2.
c) Save and verify these settings are in effect before proceeding to the next step. If necessary reboot your Windows Home Server to obtain the reserved IP address over DHCP.
The Network Address Translation (NAT) engine in SonicOS Enhanced allows users to define granular NAT polices for their incoming and outgoing traffic. By default, the SonicWALL NSA 240 security appliance has a preconfigured NAT policy to allow all systems connected to the X0 interface to perform Many-to-One NAT using the IP address of the X1 interface, and a policy to not performNAT when traffic crosses between the other interfaces.
a) Expand the Network node and click on “NAT Policies”.
b) Add a new NAT Policy entry for HTTP (TCP 80)
c) Add a new NAT Policy entry for HTTPS (TCP 443)
d) Create a new NAT Policy entry for RWW (TCP 4125). The RWW service is not already defined under services, select "New Service" in the Original Service drop-down menu to create the RWW service entry. Then complete the NAT Policy entry using the RWW service definition.
a) Expand the Firewall node and click on the “Acces Rules” section. In the Access Rules matrix click on from WAN to LAN.
b) Add a new firewall rule for HTTP
c) Add a new firewall rule for HTTPS
d) Add a new firewall rule for RWW
By now you have already written the policies and rules needed so that outsiders can get to the Windows Home Server using its domain name (http://example.homeserver.com) or your public WAN IP. The Windows Home Server is really running on a private side server 10.0.0.1.Now imagine that you are a person using a laptop on the private side, with IP of 10.100.0.201 (Remember the SonicWALL SonicOS separates LAN and WLAN into different networks). You want to reach the server using its public name. If you sit on the private side and request http://example.homeserver.com , loopback is what makes it possible for that to work, even though the server is actually right next to you on a local IP address.
To configure loopback you need a custom NAT policy like this:Original Source: LAN SubnetsTranslated Source: WAN Primary IPOriginal Destination: WAN Primary IPTranslated Destination: HomeServerOriginal Service: AnyTranslated Service: OriginalInbound Interface: AnyOutbound Interface: Any
All done! After you configured your SonicWALL NSA 240 UTM Appliance for Remote Access you should test the remote connectivity from within your home and from outside of your home.