• NetExtender for Secure Mobile Access 10.2
• NetExtender Overview
  • What is NetExtender
  • NetExtender Concepts
    • Stand-Alone Client
    • NetExtender Supports Network logon (PreLogon)
    • NetExtender Supports Always On VPN (AOV)
    • Multiple Ranges and Routes
    • IP Address User Segmentation
    • Client Routes
    • Tunnel All Mode
    • Proxy Configuration
  • Supported Platforms
    • NetExtender Client Versions
    • Supported Clients
    • Supported SonicWall Appliances
  • What's New in NetExtender
  • Feature Support in NetExtender
  • Deprecated Feature
• Configuring NetExtender for Windows Client
  • Prerequisites
  • Support Enhancement
  • Installing NetExtender on Windows
  • Enabling Network Logon (PreLogon) Feature on NetExtender
  • Enabling Always-On VPN Connection
  • Installing NetExtender through Microsoft Installer
  • Auto-Run NetExtender
• Configuring NetExtender for Linux Client
  • Prerequisites
  • Installing NetExtender on Linux
• Using NetExtender
  • Adding Connection Profile Management
  • Editing Connection Profile Management
  • Connect with Connection Profile
  • Connect with Specific Protocol
  • Multiple Factor Authentication
    • TOTP Authentication
    • Client Certificate Authentication
    • Smart Card Authentication
    • DUO Security Authentication Support for NetExtender
      • DUO Security Authentication with NetExtender Windows
      • DUO Security Authentication with NetExtender Linux
  • Configuring NetExtender Properties
    • NetExtender Properties for Windows Client
      • Configuring Settings
      • Configuring Connection Settings
      • Configuring Connection Script
      • Configuring Proxy
      • Configuring Packet Capture
    • NetExtender Properties for Linux Client
      • Configuring Proxy
      • Configuring Certificate Settings
      • Configuring Settings
  • Viewing the NetExtender Log
  • Disconnecting NetExtender
  • Upgrading NetExtender
  • Uninstalling NetExtender
• Using the NetExtender Command Line Interface
  • Launching the NetExtender CLI for Windows
  • Launching the NetExtender CLI for Linux
• NetExtender Troubleshooting
• NetExtender FAQ
• Use Case
  • Adding Connection Profile
  • Editing Connection Profile
  • OTP Authentication
  • Certificate Authentication
  • Authentication with Smart Card
• SonicWall Support
  • About This Document

Proxy Configuration

SMA appliances support NetExtender sessions using proxy configurations. Currently, only HTTPS proxy is supported. When launching NetExtender from the Web portal, if your browser is already configured for proxy access, NetExtender automatically inherits the proxy settings. The user can also manually configure the proxy settings in the NetExtender client preferences. NetExtender can automatically detect proxy settings for proxy servers that support the Web Proxy Auto-Discovery (WPAD) Protocol.

NetExtender provides three options for configuring proxy settings:

• Automatically detect settings - To use this setting, the proxy server must support Web Proxy Auto-Discovery Protocol (WPAD) that can push the proxy settings script to the client automatically.

• Use automatic configuration script - If you know the location of the proxy settings script, you can select this option and provide the script's URL.

• Use proxy server - You can use this option to specify the IP address and port of the proxy server. Optionally, you can enter an IP address or domain in the BypassProxy field to allow direct connections to those addresses and bypass the proxy server. You can enter a username and password for the proxy server if required. If the proxy server requires a username and password, but you do not specify them, a NetExtender pop-up window prompts you to enter them when you first connect.

When NetExtender connects using proxy settings, it establishes an HTTPS connection to the proxy server instead of connecting to the SMA server directly. The proxy server then forwards traffic to the SMA server. SSL encrypts all traffic with the certificate negotiated by NetExtender, of which the proxy server has no knowledge. The connecting process is identical for proxy and non-proxy users.