Filter
Top Products
Configuring WAN Acceleration
1336
SonicOS 5.8.1 Administrator Guide
Step 5 Make sure the Remote Server Name and the Local Device Name (from step 4 for the data
center site) text fields match.
Step 6 Enter the information for this server, and then click Apply.
Step 7 Explore the path \\fastbox\ on the PC located at the remote site.
After the first download of files, connection speed will improve
because files are now cached
on the WXA series appliance
Note In this configuration example, you may have more than one remote server in the data center.
If Add All Shares is selected, there must be a new service principal name (SPN) Alias for
each additional server. The SonicWALL WXA series appliance attempts to create the DNS
entries automatically for each alias created. If DNS entries are not automatically created,
they need to be added manually. Add new SPN Aliases in the domain controller by issuing
setspn –A cifs/alias realname and setspn –A cifs/alias.fq.dn realname CLI commands.
See “Manually Adding SPN Hostnames in the DNS” on page 1340 for configuration details.
Note If Add All Shares is not selected, the same local device name can have each manual share
forwarded to a different server.
Configuring Custom Zones for WXA
SonicWALL recommends that the zone properties of the interface that the WXA appliance is
connected to is a LAN zone. Setting the WXA appliance to a LAN zone is recommended
because the default access rules associated with that zone allow traffic between the WXA
appliances at both locations; therefore, there is no need for additional configuration to the
access rules.
Note Access rules are necessary for the traffic coming from VPN>LAN and LAN>VPN to be open
for WXA associated traffic and the default zone properties of the LAN takes care of handling
traffic without manually adding or modifying any access rules. Both WXA appliances
deployed at each location should be able to communicate with each other without being
blocked by access rules or firewall policies.
If you need to customize a zone for WFS acceleration, make sure VPN remote users are
allowed to access the WXA appliance. If additional domain controllers and file servers are
located in any zone other than the LAN, necessary access rules must be configured to allow
traffic from and to the WXA appliance to those zones as well as from and to the SonicWALL
security appliance.
For example consider, at the data center, if the WXA appliance is deployed in the DMZ sone,
the access rules must be configured to allow traffic from VPN>DMZ and LAN>DMZ so that
traffic to the WXA appliance from the VPN and from the LAN zones are allowed to the WXA
appliance.