COMPREHENSIVE INTERNET SECURITY SonicWALL Internet Security Appliances SonicWALL SSL VPN 4000 Getting Started Guide
SonicWALL SSL VPN 4000 Appliance Getting Started Guide This Getting Started Guide contains installation procedures and configuration guidelines for deploying a SonicWALL SSL VPN 4000 appliance into an existing or new network. This document addresses the most common use-case scenarios and network topologies in which the SonicWALL SSL VPN 4000 appliance can be deployed.
Before You Begin Check Package Contents • • • • • • • • Any Items Missing? One SonicWALL SSL VPN 4000 If any items are missing from your package, appliance contact: SonicWALL Support One SonicWALL SSL VPN 4000 Web: http://www.sonicwall.com/us/Support.html Getting Started Guide Email: customer_service@sonicwall.
Network Configuration Information Collect the following information about your current network configuration: Primary DNS: Secondary DNS (optional): DNS Domain: WINS server(s) (optional): Other Information These are the default settings for accessing your SonicWALL SSL VPN management interface: User Name: Password: admin (default: password) SonicWALL SSL VPN 4000 Getting Started Guide Page 3
Selecting a SonicWALL Recommended Deployment Scenario The deployment scenarios described in this section are based on actual customer deployments and are SonicWALL-recommended deployment best practices. This section describes three common deployments of the SonicWALL SSL VPN 4000. In Table 1, select the scenario that most closely matches your deployment.
2 Applying Power to the SonicWALL SSL VPN 4000 1. Plug the power cord into the SonicWALL SSL VPN 4000 and into an appropriate power outlet. 2. Turn on the power switch on the rear of the appliance next to the power cord. Console Port: Provides access to the command line interface. (for future use) Power LED Test LED Alarm LED Exhaust fans X1 - X5: 10/100 Ethernet X0: Default management port. Provides connectivity between the SSL VPN and your gateway.
Accessing the Management Interface To access the Web-based management interface of the SonicWALL SSL VPN 4000: 1. Connect one end of a crossover cable into the X0 port of your SonicWALL SSL VPN 4000. Connect the other end of the cable into the computer you are using to manage the SonicWALL SSL VPN 4000. SonicWALL SSL-VPN 4000 X0 Management Station 2. Set the computer you use to manage the SonicWALL SSL VPN 4000 to have a static IP address in the 192.168.200.x/24 subnet, such as 192.168.200.20.
5. The SonicWALL SSL VPN management interface displays and prompts you to enter your user name and password. Enter “admin” in the User Name field, “password” in the Password field, select LocalDomain from the Domain drop-down list and click the Login button.
4 Configuring Your SonicWALL SSL VPN 4000 Once your SonicWALL SSL VPN 4000 is connected to a computer through the management port (X0), it can be configured through the Web-based management interface.
Setting Your Administrator Password 1. Select the Users > Local Users page 2. Click the Configure button corresponding to the “admin” account. Note: Changing your password from the factory default is optional but strongly recommended. If you do change your password, be sure to keep it in a safe place. If you lose your password, you will have to reset the SonicWALL SSL VPN 4000 to factory settings, losing your configuration. 3. Enter a password for the “admin” account in the Password field.
6. Select User from the User Type drop-down menu. 7. Click the Add button. Setting Time Zone 1. Select the System > Time page. 2. Select the appropriate time zone from the drop-down menu. 3. Click the Accept button. Note: Setting the time correctly is essential to many of the operations of the SonicWALL SSL VPN 4000. Be sure to set the time zone correctly. Automatic synchronization with an NTP server (default setting) is encouraged to ensure accuracy.
3. Enter your primary DNS server information in the Primary DNS Server field. 4. (Optional) Enter a secondary DNS server in the Secondary DNS Server field. 5. (Optional) Enter your DNS Domain in the DNS Domain Field. 6. (Optional) Enter your WINS servers in the Primary WINS Server and Secondary WINS Server fields. 7. Click the Accept button.
C - SSL VPN on the LAN IP Address: An unused address within your LAN subnet, for example: 192.168.168.200 Subnet Mask: Must match your LAN subnet mask When you click OK, you will lose your connection to the SSL VPN. 4. Reset the computer you use to manage the SonicWALL SSL VPN 4000 to have a static IP address in the range you just set for the X0 interface, for example, 10.1.1.20 or 192.168.200.20.
Configuring a Default Route Refer to the following table to correctly configure your default route. If you do not know your scenario, refer to “Selecting a SonicWALL Recommended Deployment Scenario” on page 4. If you are using scenario: Your upstream gateway device will be: A - SSL VPN on a New DMZ The DMZ you will create (for example, 192.168.200.2). B - SSL VPN on an Existing DMZ Your existing DMZ interface. C - SSL VPN on the LAN Your LAN gateway. 1. Select the Network > Routes page. 2.
Route 1 Destination Network: 0.0.0.0 Subnet Mask: 128.0.0.0 Route 2 Destination Network: 128.0.0.0 Subnet Mask: 128.0.0.0 4. Enter your subnet mask in the Subnet Mask field. 5. Click the Add button to add this client route. Setting your NetExtender Address Range The NetExtender IP range defines the IP address pool from which addresses will be assigned to remote users during NetExtender sessions.
Scenario C Select a range that falls within your existing LAN subnet. For example, if your LAN uses the 192.168.168.0/24 subnet, and you want to support up to 10 concurrent NetExtender sessions, you could use 192.168.168.240 to 192.168.168.249, providing they are not already in use. To set your NetExtender address range, perform the following steps: 1. Select the NetExtender > Client Settings page. 2.
For example, if your current Transparent range is 67.115.118.75 through 67.115.118.80, and you wish to support 50 concurrent NetExtender clients, configure your SSL VPN X0 interface with an available IP address in the Transparent range, such as 67.115.118.80, and configure your NetExtender range as 192.168.10.100 to 192.168.10.200. Then, on your gateway device, configure a static route to 192.168.10.0/255.255.255.0 using 67.115.118.80.
Connecting the SonicWALL SSL VPN 4000 Before continuing, reference the diagrams on the following pages to connect the SonicWALL SSL VPN 4000 to your network. Refer to the table in “Selecting a SonicWALL Recommended Deployment Scenario” on page 4 to determine the proper scenario for your network configuration.
Scenario B: Configuring Your Network Interface Configure your SonicWALL SSL VPN 4000 to connect with your SonicWALL UTM appliance under network configurations given in Scenario B. On your SonicWALL SSL VPN 4000: 1. Select the Network > Interfaces page. 2. Click the Configure button for the X0 port. 3. If configuring with Scenario B, enter an unused IP address in your DMZ subnet in the IP Address field. 4. Enter your subnet mask in the Subnet Mask field. 5. Click the OK button to apply changes.
Scenario B: Connecting the SonicWALL SSL VPN 4000 To connect the SonicWALL SSL VPN 4000 using Scenario B, perform the following steps: 1. Connect one end of an Ethernet cable to an unused port on your DMZ, either directly to the OPT or X2 on your existing SonicWALL UTM appliance or to a hub or switch on your DMZ.
4. Enter your subnet mask in the Subnet Mask field. 5. Click the OK button to apply changes. Scenario C: Connecting the SonicWALL SSL VPN 4000 To connect the SonicWALL SSL VPN 4000 using Scenario C, perform the following steps: 1. Connect one end of a crossover cable to an unused port on your LAN hub or switch. Scenario C: SSL VPN on the LAN Gateway Device Switch/ Hub LAN port Internet connection SonicWALL SSL-VPN 4000 X0 Network Nodes Remote Users Internet Zone LAN 2.
Configuring Your Gateway Device Now that you have set up your SonicWALL SSL VPN 4000, you need to configure your gateway device to work with the SonicWALL SSL VPN 4000. Refer to the table in “Selecting a SonicWALL Recommended Deployment Scenario” on page 4 to determine the proper scenario for your network configuration.
Scenario A: Configuring a DMZ or OPT Port in SonicOS Standard 1. Select the Network > Settings page. 2. Click Configure button for the DMZ or OPT interface. Select the DMZ in NAT Mode radio button. 3. Enter 192.168.200.2 in the DMZ Private Address field. 4. Enter 255.255.255.0 in the DMZ Subnet Mask field. 5. Click the OK button.
4. In the Step 1: Access Rule Type page, select Public Server Rule and click Next. 5. In the Step 2: Public Server page, perform the following selections: Service HTTPS Server IP Address The X0 IP address of the SonicWALL SSL VPN appliance, 192.168.200.1 by default Destination Interface DMZ Click Next. 6. In the Congratulations page, click Apply to create the rules and allow access from the WAN to the SonicWALL SSL VPN appliance on the DMZ.
If you are allowing HTTP access to the SonicWALL SSL VPN appliance, create a public server access rule for HTTP: 1. 2. 3. 4. In the Firewall > Access Rules page, click . In the Welcome to the Network Access Rules Wizard page, click Next. In the Step 1: Access Rule Type page, select Public Server Rule. Click Next. In the Step 2: Public Server page, perform the following selections and click Next: Service Web (HTTP) Server IP Address The X0 IP address of the SonicWALL SSL VPN appliance, 192.168.200.
6. In the Step 4: Access Rule Source Interface and Address page, perform the following selections and click Next: Interface DMZ IP Address Begin The X0 IP address of the SonicWALL SSL VPN appliance, 192.168.200.1 by default IP Address End The X0 IP address of the SonicWALL SSL VPN appliance, 192.168.200.
7. In the Step 5: Access Rule Destination Interface and Address page, perform the following selections and click Next: Interface LAN IP Address Begin * IP Address End Leave blank 8. In the Step 6: Access Rule Time page, leave Time Active set to Always Active unless you want to limit when you want SSL VPN clients to have access to the LAN. 9. In the Congratulations page, click Apply to create the access rule.
Create access to the LAN for NetExtender: 1. 2. 3. 4. In the Firewall > Access Rules page, click . In the Welcome to the SonicWALL Network Access Rules page, click Next. In the Step 1: Access Rule Type page, select General Rule. Click Next. In the Step 2: Access Rule Service page, select Any. Click Next. 5. In the Step 3: Access Rule Action page, configure: Select Action for this Rule Allow TCP Connection Inactivity TImeout 30 minutes Click Next. 6.
Scenario A: Adding a New SSL VPN Custom Zone in SonicOS Enhanced 1. Select the Network > Interfaces page. 2. Click Configure button for the X2 interface (or any other available interface). 3. Select Create New Zone in Zone field. The Add Zone window opens. 4. 5. 6. 7. 8. 9. 10. 11. 12. Page 28 Enter SSL VPN in the Name field. Select Public from the Security Type drop-down menu. Un-check the Allow Interface Trust checkbox. Check the Gateway AV, Intrusion Prevention Service and Anti-Spyware checkboxes.
Scenario A: Allowing WAN -> SSL VPN Connection in SonicOS Enhanced Follow this procedure if you are connecting your SonicWALL SSL VPN 4000 to a SonicWALL UTM appliance running SonicOS Enhanced. If your SonicWALL UTM appliance is running SonicOS Standard, refer to “Scenario A: Allowing WAN -> DMZ Connection in SonicOS Standard” on page 22. Create a public server access rule for HTTP and HTTPS traffic: 1. Select the Firewall > Access Rules page. 2. Click . 3.
5. In the Add Service Group dialog box, create a service group for HTTP and HTTPS: • Enter a name for the service. • Select both HTTP and HTTPS and click . • Click OK when both HTTP and HTTPS are in the right column. 6. In the Step 2: Server Private Network Configuration page, enter: Server Name A name for your SonicWALL SSL VPN 4000 Server Private IP Address The X0 IP address of the SonicWALL SSL VPN appliance, 192.168.200.1 by default Server Comment A brief description of the server Click Next.
7. In the Step 3: Server Public Information page, either accept the default IP address or enter an IP address in your allowed public IP range. Note: The default IP address is the WAN IP address of your SonicWALL UTM appliance. If you accept this default, all HTTP and HTTPS traffic to this IP address will be routed to your SonicWALL SSL VPN 4000. Click Next. 8. The Step 4: Public Server Configuration Summary page displays all the configuration actions that will be performed to create the public server.
Scenario A: Allowing SSL VPN -> LAN Connection in SonicOS Enhanced When users have connected to the SSL VPN, they need to be able to connect to resources on the LAN. 1. In the administration interface, navigate to the Network > Address Objects page. 2. At the bottom of the page, below the Address Objects table, click 3.
Click OK to create the object. 6. In the middle of the Network > Address Objects page, below the Address Groups table, click . 7. In the Add Address Object Group dialog box, create a group for the X0 interface IP address of your SonicWALL SSL VPN 4000 and the NetExtender IP range: • • Enter a name for the group. In the left column, select the two groups you created in steps 1 through 5, and click the arrow button . • Click OK when both objects are in the right column to create the group. 8.
10. In the Add Rule window, create a rule to allow the address group you just created access to the LAN: Action Allow From Zone SSL VPN To Zone LAN Service Any Source The address group you just created, such as SonicWALL_SSL VPN_Group Destination Any Users Allowed All Schedule Always on Enable Logging Selected Allow Fragmented Packets Selected Click Add to create the rule.
Scenario B: SSL VPN on Existing DMZ This section provides procedures to configure your gateway appliance based on Scenario B.
4. In the Step 1: Access Rule Type page, select Public Server Rule and click Next. 5. In the Step 2: Public Server page, perform the following selections: Service HTTPS Server IP Address The X0 IP address of the SonicWALL SSL VPN appliance within your DMZ range, for example 10.1.1.200. Destination Interface DMZ Click Next. 6. In the Congratulations page, click Apply to create the rules and allow access from the WAN to the SonicWALL SSL VPN appliance on the DMZ.
If you are allowing HTTP access to the SonicWALL SSL VPN appliance, create a public server access rule for HTTP: 1. 2. 3. 4. In the Firewall > Access Rules page, click . In the Welcome to the Network Access Rules Wizard page, click Next. In the Step 1: Access Rule Type page, select Public Server Rule. Click Next.
6. In the Step 4: Access Rule Source Interface and Address page, perform the following selections and click Next: Page 38 Interface DMZ IP Address Begin The X0 IP address of the SonicWALL SSL VPN appliance within your DMZ range, for example 10.1.1.200. IP Address End The X0 IP address of the SonicWALL SSL VPN appliance, the same as above, for example 10.1.1.200.
7. In the Step 5: Access Rule Destination Interface and Address page, perform the following selections and click Next: Interface LAN IP Address Begin * IP Address End Leave blank 8. In the Step 6: Access Rule Time page, leave Time Active set to Always Active unless you want to limit when you want SSL VPN clients to have access to the LAN. 9. In the Congratulations page, click Apply to create the access rule.
Create access to the LAN for NetExtender: 1. 2. 3. 4. In the Firewall > Access Rules page, click . In the Welcome to the SonicWALL Network Access Rules page, click Next. In the Step 1: Access Rule Type page, select General Rule. Click Next. In the Step 2: Access Rule Service page, select Any. Click Next. 5. In the Step 3: Access Rule Action page, configure: Select Action for this Rule Allow TCP Connection Inactivity Timeout 30 minutes Click Next. 6.
Scenario B: Allowing WAN -> DMZ Connection in SonicOS Enhanced Follow this procedure if you are connecting your SonicWALL SSL VPN 4000 to a SonicWALL UTM appliance running SonicOS Enhanced. If your SonicWALL UTM appliance is running SonicOS Standard, refer to “Scenario A: Allowing WAN -> DMZ Connection in SonicOS Standard” on page 22.
5. In the Add Service Group dialog box, create a service group for HTTP and HTTPS: • Enter a name for the service. • Select both HTTP and HTTPS and click . • Click OK when both HTTP and HTTPS are in the right column. 6. In the Step 2: Server Private Network Configuration page, enter: Server Name A name for your SonicWALL SSL VPN 4000 Server Private IP Address The X0 IP address of the SonicWALL SSL VPN appliance within your DMZ range, for example, 10.1.1.
7. In the Step 3: Server Public Information page, either accept the default IP address or enter an IP address in your allowed public IP range. Note: The default IP address is the WAN IP address of your SonicWALL UTM appliance. If you accept this default, all HTTP and HTTPS traffic to this IP address will be routed to your SonicWALL SSL VPN 4000. Click Next. 8. The Step 4: Public Server Configuration Summary page displays all the configuration actions that will be performed to create the public server.
Scenario B: Allowing DMZ -> LAN Connection in SonicOS Enhanced When users have connected to the SSL VPN, they need to be able to connect to resources on the LAN. 1. In the administration interface, navigate to the Network > Address Objects page. 2. At the bottom of the page, below the Address Objects table, click 3.
Click OK to create the object. 6. In the middle of the Network > Address Objects page, below the Address Groups table, click . 7. In the Add Address Object Group dialog box, create a group for the X0 interface IP address of your SonicWALL SSL VPN 4000 and the NetExtender IP range: • • Enter a name for the group. In the left column, select the two groups you created in steps 1 through 5, and click the arrow button . • Click OK when both objects are in the right column to create the group. 8.
10. In the Add Rule window, create a rule to allow the address group you just created access to the LAN: Action Allow From Zone DMZ To Zone LAN Service Any Source The address group you just created, such as SonicWALL_SSL VPN_Group Destination Any Users Allowed All Schedule Always on Enable Logging Selected Allow Fragmented Packets Selected Click OK to create the rule.
Scenario C: SSL VPN on the LAN This section provides procedures to configure your gateway appliance based on Scenario C.
Scenario C: Setting Public Server Access in SonicOS Standard 1. 2. 3. 4. Select Wizards in the left navigation bar. Click the Network Access Rules Wizard option and press the Next button. Select Public Server Rule. Enter a comment, such as “WAN to SSL VPN” to describe your connection. 5. Click the Next button to continue the Wizard. 6. Select HTTPS from the Service drop-down list. 7. Enter 192.168.168.
Scenario C: Setting Public Server Access in SonicOS Enhanced 1. 2. 3. 4. Select Wizards in the left navigation bar. Click the Public Server Wizard option and press the Next button. Select Web Server from the Server Type drop-down menu. Select HTTP and HTTPS checkboxes. 5. Click the Next button to continue the Wizard. 6. Enter SSL VPN in the Server Name field. 7. Enter 192.168.168.
Testing Your SSL VPN Connection Now you have configured your SonicWALL UTM appliance and SonicWALL SSL VPN 4000 for secure SSL VPN remote access.This section provides instructions to verify your SSL VPN connection using a remote client on the WAN. Verifying a User Connection from the Internet 1.
4. Select NetExtender from the left navigation bar. This will start the NetExtender client installation. 5. Click the NetExtender button and complete the client installation. When complete, the following message is displayed: 6. Ping a host on your corporate LAN to verify your SSL VPN remote connection. Congratulations! You have successfully set up your SonicWALL SSL VPN 4000.
Registering Your SonicWALL SSL VPN 4000 Before You Register Verify that the time, DNS, and default route settings on your SonicWALL SSL VPN are correct before you register your appliance. To verify or configure the time settings, navigate to the System > Time page. To verify or configure the DNS setting, navigate to the Network > DNS page. To verify or configure the default route, navigate to the Network > Routes page. You need a mySonicWALL.com account to register the SonicWALL SSL VPN 4000.
3. On the System > Licenses page, click Activate, Upgrade, or Renew services. The License Management page is displayed. 4. If you have a mySonicWALL.com account, enter your mySonicWALL.com user name and password into the fields and then click Submit. The display changes.
5. Enter a descriptive name for your SonicWALL SSL VPN in the Friendly Name field. 6. Under Product Survey, fill in the requested information and then click Submit. The display changes to inform you that your SonicWALL SSL VPN 4000 is registered. 7. Click Continue. 8. In the License Management page, your latest license information is displayed. Congratulations Your SonicWALL SSL VPN 4000 is now fully operational.
Configuring Dynamic DNS To begin using Dynamic DNS, you must first set up an account with one of the 4 free service providers listed below: • • • • DynDNS.org changeip.com No-IP.com yi.org It is possible to use multiple providers simultaneously. The registration process normally involves a confirmation email from the provider, with a final acknowledgment performed by visiting a unique URL embedded in the confirmation email.
To configure Dynamic DNS on the SonicWALL UTM appliance, perform these steps: 1. On the Network > Dynamic DNS page, click the Add button. The Add DDNS Profile window is displayed. 2. If Enable this DDNS Profile is selected, the profile is administratively enabled, and the SonicWALL UTM appliance takes the actions defined in the Online Settings section on the Advanced tab. 3. If Use Online Settings is selected, the profile is administratively online. 4.
7. Enter the fully qualified domain name (FQDN) of the hostname you registered with dyndns.org. Make sure you provide the same hostname and domain as you configured. 8. You may optionally select Enable Wildcard and/or configure an MX entry in the Mail Exchanger field. 9. Click the Advanced tab. You can typically leave the default settings on this page. 10. The On-line Settings section provides control over what address is registered with the dynamic DNS provider.
Configuring a Static IP Address If you did not enable the SonicWALL UTM appliance DHCP server, you must configure each computer with a static IP address from your LAN or WLAN IP address range. After the SonicWALL SSL VPN 4000 has restarted, follow the steps below for configuring your network clients running any of the following Microsoft Windows operating systems on your LAN/WLAN: Windows XP 1. Open the Local Area Connection Properties window. 2.
Windows NT 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. From the Start menu, highlight Settings and then select Control Panel. Open Network. Double-click TCP/IP in the TCP/IP Properties window. Select Specify an IP Address. Type an IP address from your LAN IP range in the IP Address field. Type the appropriate subnet mask (for example, 255.255.255.0) in the Subnet Mask field. Type the SonicWALL SSL VPN 4000 LAN IP Address in the Default Gateway field. Click DNS at the top of the window.
Mounting Guidelines The SonicWALL SSL VPN 4000 is designed to be mounted in a standard 19-inch rack mount cabinet. The following conditions are required for proper installation: • • • • • • • • • Page 60 Use the mounting hardware recommended by the rack manufacturer and ensure that the rack is adequate for the application. SonicWALL includes a rack mounting kit with the SonicWALL SSL VPN appliance that is compatible with most computer equipment racks.
Glossary of Networking Terms ActiveX - A technology that allows the sharing of applications and data across the Web. For example, Active X allows you to view Microsoft Word and Adobe Acrobat documents within the Internet Explorer Web browser without downloading the files and launching the appropriate application. The SonicWALL SSL VPN network client, NetExtender, uses an ActiveX control when launched or installed from Internet Explorer on Windows. With Firefox, XPCOM is used, which is similar to ActiveX.
SSL VPN - Secure Socket Layer Virtual Private Networking. A secured private communications network usually used within a company, or by several different companies or organizations, communicating over a public network. SSL technology is used either for tunneling the entire network stack, or for securing what is essentially a Web proxy. Subnet - A portion of a network. Each subnet within a network shares a common network address and is uniquely identified by a subnetwork number.
SonicWALL SSL VPN 4000 Appliance Regulatory Statement and Safety Instructions Regulatory Model/Type Product Name 1RK09-032 SonicWALL SSL VPN 4000 Detailed regulatory information can be found in the electronic file, “SonicWALL_SSL-VPN_Regulatory_Statement.pdf,” located on the SonicWALL Resource CD provided with the unit or on the SonicWALL Web site: . Lithium Battery Warning The Lithium Battery used in the SonicWALL Internet security appliance may not be replaced by the user.
Copyright Notice © 2008 SonicWALL, Inc. All rights reserved. Under the copyright laws, this manual or the software described within, can not be copied, in whole or part, without the written consent of the manufacturer, except in the normal use of the software to make a backup copy. The same proprietary and copyright notices must be affixed to any permitted copies as were affixed to the original.
Notes SonicWALL SSL VPN 4000 Getting Started Guide Page 65
Notes Page 66
SonicWALL, Inc. 1143 Borregas Avenue T +1 408.745.9600 Sunnyvale CA 94089-1306 F +1 408.745.9300 www.sonicwall.com PN: 232-001459-00 Rev A 5/08 ©2008 SonicWALL, Inc. is a registered trademark of SonicWALL, Inc. Other product names mentioned herein may be trademarks and/or registered trademarks of their respective companies. Specifications and descriptions subject to change without notice.
