throbber
Aventail AutoSOCKS
`
`... ADMINISTRATION
`&
`SER'S GUIDE
`
`Petitioner Apple - Ex. 1021, p. 1
`
`

`

`Aventail AutoSOCKS v2.1 Administration and User’s Guide
`Copyright © 1996-1997 Aventail Corporation. All rights reserved.
`117 South Main Street
`4th Floor
`Seattle, WA 98104-2540
`USA
`Printed in the United States of America.
`
`Trademarks and Copyrights
`Aventail, AutoSOCKS, Internet Policy Manager, Aventail VPN, Mobile VPN, and Partner
`VPN are trademarks of Aventail Corporation.
`Socks5Toolkit is a trademark of NEC Corporation. MD4 Message-Digest Algorithm and
`MD5 Message-Digest Algorithm are trademarks of RSA Data Security, Inc. Microsoft, MS,
`Windows, Windows 95, and Windows NT are either registered trademarks or trademarks of
`Microsoft Corporation. RealAudio is a trademark of Progressive Networks.
`Other product names mentioned in this manual may be trademarks or registered trademarks of
`their respective companies and are the sole property of their respective manufacturers.
`Copyright © 1995-1996 NEC Corporation. All rights reserved.
`Copyright ! 1990-1992, RSA Data Security, Inc. All rights reserved.
`Copyright ! 1991-1992, RSA Data Security, Inc. All rights reserved.
`
`Petitioner Apple - Ex. 1021, p. 2
`
`

`

`Table of Contents
`
`Introduction............................................................................................................................. 1
`About This Document .................................................................................................................................1
`Document Organization.................................................................................................2
`Document Conventions .................................................................................................2
`Technical Support..........................................................................................................................................3
`About Aventail Corporation ......................................................................................................................4
`AutoSOCKS v2.1 Administration and User’s Guide............................................................. 5
`Getting Started...............................................................................................................................................5
`Network Security in a Nutshell....................................................................................5
`What is AutoSOCKS?.....................................................................................................6
`TCP/IP Communications ..............................................................................................6
`WinSock Connection to A Remote Host ...............................................................6
`What Does AutoSOCKS Do?......................................................................................7
`AutoSOCKS Platform Requirements..........................................................................9
`Windows 95 and Windows NT 4.0 ..........................................................................9
`System Requirements .........................................................................................9
`Interface Features................................................................................................9
`Windows 3.1, Windows for Workgroups 3.11, and
`Windows NT 3.51 .......................................................................................................10
`System Requirements .......................................................................................10
`Interface Features..............................................................................................10
`Installation Source Media .............................................................................................10
`Installing AutoSOCKS ................................................................................................................................11
`Configuration Files.........................................................................................................11
`Individual Installation .....................................................................................................11
`Network Installation......................................................................................................13
`Networked Configuration File Setup......................................................................14
`Administrator-Maintained Shared Configuration Files ............................14
`Shared Configuration File Distribution ..................................................................14
`Setup Command Line Options .................................................................................15
`Configuring AutoSOCKS ..........................................................................................................................16
`Define a SOCKS Server ...............................................................................................18
`Define a Destination......................................................................................................20
`
`Table of Contents• i
`
`Petitioner Apple - Ex. 1021, p. 3
`
`

`

`Enter Redirection Rules................................................................................................23
`Define Local Name Resolution.................................................................................26
`Managing Authentication Modules.............................................................................27
`Example Network Configurations ..........................................................................................................35
`Configuration Using Aventail Internet Policy Manager........................................36
`Configuration Using Aventail VPN Server ..............................................................37
`AutoSOCKS Utilities Reference Guide ............................................................................... 42
`System Menu Commands..........................................................................................................................42
`Close..................................................................................................................................43
`Hide Icon ..........................................................................................................................43
`Help....................................................................................................................................43
`About.................................................................................................................................43
`Credentials.......................................................................................................................43
`Configuration File...........................................................................................................44
`Config Tool......................................................................................................................45
`Logging Tool ....................................................................................................................46
`S5 Ping ...............................................................................................................................51
`AutoSOCKS User Supplement............................................................................................. 55
`How to Start and Close AutoSOCKS...................................................................................................55
`How to Enter Authentication Credentials ...........................................................................................56
`Username/Password and CHAP Authentication ...................................................57
`SSL Authentication.........................................................................................................58
`Appendix 1: Troubleshooting...........................................................................................................................61
`AutoSOCKS Installation Problems .........................................................................................................61
`Network Connectivity Problems ............................................................................................................62
`AutoSOCKS Configuration Problems ...................................................................................................62
`Application and TCP/IP Stack Interoperability Problems .................................................................64
`AutoSOCKS Trace Logging......................................................................................................................64
`Reporting AutoSOCKS Problems...........................................................................................................68
`Glossary..................................................................................................................................................................70
`Index........................................................................................................................................................................72
`
`ii • AutoSOCKS v2.1 Administration and User’s Guide
`
`Petitioner Apple - Ex. 1021, p. 4
`
`

`

`Introduction
`
`Welcome to the AutoSOCKS! v2.1 secure Windows client for 16- and 32-bit Windows
`applications. AutoSOCKS v2.1 is the first commercial application to incorporate the SOCKS
`v5 security protocol standard, simplifying SOCKS deployment for end users and network
`managers.
`AutoSOCKS transparently intercepts WinSock communication requests issued by TCP/IP
`applications and processes them based upon a set of routing directives (rules) assigned when
`AutoSOCKS is configured. (For more information about WinSock, TCP/IP, and general
`network communications, see “Getting Started.”)
`On larger networks, AutoSOCKS can address multiple SOCKS v5 servers based on end
`destination and type of service. This feature enables network administrators to effectively
`monitor and direct network traffic.
`Features of AutoSOCKS v2.1:
`Supports both SOCKS v4 and SOCKS v5 standards
`•
`Supports RFC1928 and RFC1929 SOCKS v5 standards
`•
`• Network-based setup provides a single configuration point with a simple user interface
`• Transparently route connections from Windows applications to external networks through
`any SOCKS-based firewall system
`• Logging utility to troubleshoot problems with network connections
`• Enables internal network connections to pass through without interference
`• Enables network redirection through multiple SOCKS servers
`Supports multiple authentication methods including SOCKS v4 Identification,
`•
`username/password, CHAP, and SSL 3.0. Other authentication modules can be added
`Supports 16-bit WinSock 1.1 applications under Windows 3.1 and Windows for
`Workgroups 3.11
`Supports both 16- and 32-bit applications under Windows 95, Windows NT 3.51, and
`Windows NT 4.0
`Provides automated installation and uninstallation
`•
`• WinSock interoperability tested at Stardust WinSock Labs
`
`•
`
`•
`
`About This Document
`The AutoSOCKS v2.1 Administration and User’s Guide provides basic information about
`AutoSOCKS v2.1. It is designed to include entry-level data for non-technical users as well as
`more advanced installation, setup, and configuration information for network administrators.
`
`Petitioner Apple - Ex. 1021, p. 5
`
`

`

`This information is also available via online AutoSOCKS Help and the Aventail web site at
`http://www.aventail.com/.
`
`Document Organization
`This document is divided into two primary sections: the Administrator’s Guide and the
`AutoSOCKS Utilities Reference Guide. The Administrator’s Guide describes procedures for
`setting up, installing, and configuring AutoSOCKS for individual and multiple networked
`workstations.
`The AutoSOCKS Utilities Reference Guide describes the AutoSOCKS system menu
`commands and utility programs. It contains detailed information about using Ping and
`Traceroute utilities and documents the authentication/encryption modules and settings.
`In addition to the AutoSOCKS v2.1 Administration and User’s Guide and the AutoSOCKS
`Utilities and Reference Guide, this document includes a removable AutoSOCKS User’s
`Supplement which describes screen displays and features that end-users may encounter while
`running AutoSOCKS in their client workstations. The document concludes with Appendix 1:
`Troubleshooting and a Glossary.
`Check the Quick Start Card, a short document designed to help you install AutoSOCKS to an
`individual workstation.
`
`Document Conventions
`The following typographic conventions are used in this document. Exceptions may be made
`for online material; for instance, italics may be difficult to read online.
`
`2 • AutoSOCKS v2.1 Administration and User’s Guide
`
`Petitioner Apple - Ex. 1021, p. 6
`
`

`

`Convention
`ALL CAPITALS
`
`Bold
`
`Italic
`“To Do” Procedures
`
`Usage
`Filenames and extensions, directory names, keynames, and
`pathnames.
`
`Anything the user types, including command-line commands,
`addresses or URLs, options, and portions of syntax that must
`be typed exactly as shown. Dialog box controls
`(Destination field), e-mail addresses
`(support@aventail.com), URLs
`(http://www.aventail.com/), and IP addresses
`(165.121.6.26) are also bold.
`Placeholders that represent information the user must insert.
`Underlined To Do headings indicate procedures and step-by-
`step directions. Multi-step procedures are numbered; single-
`step procedures are bulleted.
`
`Technical Support
`If you experience problems installing, configuring, or running AutoSOCKS refer to any of the
`following:
`• The Aventail web site, http://www.aventail.com/, for the latest list of known problems.
`• The README.TXT documentation for additional information not contained in the
`manual.
`If necessary, report problems to Aventail using the Bug Report form at the Aventail web site.
`Aventail Technical Support:
`http://www.aventail.com/
`Web site:
`support@aventail.com
`E-mail:
`Phone:
`206.777.5640
`Fax:
`206.777.5656
`
`Petitioner Apple - Ex. 1021, p. 7
`
`

`

`About Aventail Corporation
`Aventail Corporation is the leading vendor of next-generation Internet security systems. Its
`software allows organizations to secure their networks, manage their employees’ access to the
`Internet and build Virtual Private Networks (VPNs). Creating a VPN gives organizations the
`ability to dynamically create a private communication or data channel over the Internet.
`Aventail’s adherence to open security standards simplifies VPN deployment, enables
`interoperability, and leverages corporations’ existing network investments. Its VPN solutions
`allow companies to extend the reach of their corporate Intranets to customers, partners, remote
`offices, and worldwide employees.
`Aventail Corporation
`117 South Main Street
`4th Floor
`Seattle, WA 98104-2540
`Phone:
`206.777.5600
`Fax:
`206.777.5656
`http://www.aventail.com/
`info@aventail.com
`
`4 • AutoSOCKS v2.1 Administration and User’s Guide
`
`Petitioner Apple - Ex. 1021, p. 8
`
`

`

`AutoSOCKS v2.1
`Administration and
`User’s Guide
`
`This section includes procedural and background information on installing AutoSOCKS to
`both single and networked workstations. It includes:
`• Getting Started with brief explanations of network security and communications
`• Definitions of SOCKS and AutoSOCKS
`• AutoSOCKS platform and installation requirements
`Installing AutoSOCKS, including network diagrams of Aventail VPN, Aventail Internet
`•
`Policy Manager, and SOCKS v4-based server configurations
`• Creating and editing configuration files
`Note:
`Aventail understands the importance of a flexible, easy-to-use installation
`process. If you have feedback regarding the AutoSOCKS installation
`procedures, or if there are additional features you wish to see implemented,
`please e-mail comments to support@aventail.com. Your input is
`appreciated.
`
`Getting Started
`If you're new to AutoSOCKS technology, the following section will help you understand what
`AutoSOCKS is and does, as well as its relationship to network security in general.
`
`Network Security in a Nutshell
`Escalating threats of computer viruses and increased potential for unwelcome hackers are
`forcing companies to seek ways to safeguard their corporate networks and the information they
`exchange. The first response to these concerns has been the development of security
`firewalls—software barriers that control the flow of information. But firewalls can’t easily be
`configured to handle complex security issues such as monitoring network usage, providing
`private communication over public networks, and enabling remote users to gain secure access
`to internal network resources.
`Enter SOCKS v5, an Internet Engineering Task Force (IETF)-approved security protocol
`targeted at securely traversing corporate firewalls. It was originally developed in 1990, and is
`now maintained by NEC. SOCKS acts as a circuit-level proxy mechanism that manages the
`flow and security of data traffic to and from your local area network or intranet. A workstation
`whose traffic is proxied by SOCKS is considered “socksified.” SOCKS is more than a
`standard security firewall. It also features:
`
`Petitioner Apple - Ex. 1021, p. 9
`
`

`

`• Client Authentication: (SOCKS v5 only) Authentication allows network managers to
`provide selected access to internal and external areas of a network.
`• Traffic Encryption: (SOCKS v5 only) Encryption ensures that network traffic is private
`and secure.
`• UDP Support: (SOCKS v5 only) User Datagram Protocol (UDP) has traditionally been
`difficult to proxy with the exception of SOCKS v5.
`• Cross-Platform Support: Unlike most UNIX security solutions, SOCKS code can easily
`be ported to platforms such as Windows NT, Windows 95, and Macintosh systems.
`
`What is AutoSOCKS?
`AutoSOCKS automates the “socksification” of client applications, making it simple for
`workstations to take advantage of the SOCKS v5 protocol. When you run AutoSOCKS on
`your system, it automatically routes appropriate network traffic from a WinSock application to
`the SOCKS server. (WinSock is a Windows component that connects a Windows PC to the
`Internet using Transmission Control Protocol/Internet Protocol—TCP/IP.) The SOCKS server
`then sends the traffic to the Internet or the external network. Your network administrator
`defines sets of rules by which this traffic is to be routed.
`AutoSOCKS is designed to run transparently on each workstation. In most cases, you’ll
`interact with AutoSOCKS only when it prompts you to enter authentication information for a
`connection to a secure SOCKS server. You may also occasionally need to start and exit
`AutoSOCKS, although network administrators often configure it to run automatically at
`startup.
`To understand AutoSOCKS, you first need to understand a few basics of TCP/IP
`communications.
`
`TCP/IP Communications
`Windows TCP/IP networking applications such as e-mail or ftp use WinSock to gain access to
`the network or the Internet. WinSock (Windows Sockets) is the core component of TCP/IP
`under Windows. (TCP/IP is a suite of protocols that the Internet uses to provide for services
`such as e-mail, ftp, and telnet.)
`
`WinSock Connection to A Remote Host
`Via WinSock, an application goes through the following steps to connect to a remote host on
`the Internet or corporate intranet:
`1. The application executes a Domain Name System (DNS) lookup to convert the hostname
`into an Internet Protocol (IP) address. If the application already knows the IP address, this
`step is skipped.
`2. The application requests a connection to the specified remote host. This causes the
`underlying stack to begin the TCP handshake. (The TCP handshake is the process by
`which two computers initiate communication with each other.) When the handshake is
`
`6 • AutoSOCKS v2.1 Administration and User’s Guide
`
`Petitioner Apple - Ex. 1021, p. 10
`
`

`

`complete, the application is notified that the connection is established, and that data may
`now be transmitted and received.
`3. The application sends and receives data.
`
`What Does AutoSOCKS Do?
`AutoSOCKS slips in between the Windows TCP/IP application and the single access point—
`WinSock. In simple terms, AutoSOCKS redirects WinSock calls (both parameters and data)
`and reroutes them through a SOCKS-based server when required. The routing is determined
`by the rules described in the configuration file created when AutoSOCKS is installed. (See
`“Configuring AutoSOCKS.”)
`Because AutoSOCKS intercepts calls to WinSock, AutoSOCKS must duplicate WinSock
`functionality. Since AutoSOCKS also makes calls directly into WinSock, it must behave as a
`typical WinSock application as well. (See Figure 1.)
`
`Figure 1. Network application calls intercepted by AutoSOCKS
`With AutoSOCKS running, an application executes additional steps in order to connect to a
`remote host through WinSock. These steps must be transparent to the application so that it
`cannot differentiate between when AutoSOCKS is running and when it is not. The following
`three steps are identical to standard WinSock communications steps described above;
`however, nested inside them are additional actions and options introduced by AutoSOCKS.
`
`Petitioner Apple - Ex. 1021, p. 11
`
`

`

`•
`
`•
`
`1. The application does a DNS lookup to convert the hostname to an IP address. However, if
`the application already knows the IP address, this entire step is skipped. Otherwise,
`AutoSOCKS does the following:
`If the hostname matches a local domain string or does not match a redirection rule,
`•
`AutoSOCKS passes the name resolution query through to the TCP/IP stack on the
`local workstation. The TCP/IP stack then performs the lookup as if AutoSOCKS is
`not running.
`If the DNS proxy option is disabled, AutoSOCKS allows the request to go through
`unchanged.
`If the destination hostname matches a redirection rule domain name (i.e. the host is
`part of a domain we are proxying traffic to) then AutoSOCKS creates a false DNS
`entry (HOSTENT) that it can recognize during the connection request. AutoSOCKS
`will forward the hostname to the SOCKS server in step 2 and the SOCKS server
`performs the hostname resolution.
`If the DNS proxy option is enabled and the domain cannot be looked up directly,
`AutoSOCKS creates a fake DNS entry that it can recognize later, and returns this to
`the calling application. The false entry tells AutoSOCKS that the DNS lookup
`should be proxied, and that it should send the fully qualified hostname to the SOCKS
`server with the SOCKS connection request.
`2. The application requests a connection to the remote host. This causes the underlying stack
`to begin the TCP handshake. When the handshake is complete, the application is notified
`that the connection is established and that data may now be transmitted and received.
`AutoSOCKS does the following:
`a. AutoSOCKS checks the connection request.
`If the request contains a false DNS entry (from step 1) it will be proxied.
`•
`If the request contains a real IP address and the rules in the configuration file
`•
`say it should be proxied, AutoSOCKS calls WinSock to begin the TCP
`handshake with the server designated in the config file.
`If the request contains a real IP address and the configuration file rules says that
`it should not be proxied, the request is passed to WinSock and processing jumps
`to step 3 as if AutoSOCKS is not running.
`b. When the connection is completed, AutoSOCKS begins the SOCKS negotiation.
`It sends the list of authentication methods enabled in the configuration file.
`•
`• Once the server chooses an authentication method, AutoSOCKS executes the
`specified authentication processing.
`It then sends the proxy request to the SOCKS server. This includes either the IP
`address provided by the application or the DNS entry (hostname) provided in
`step 1.
`
`•
`
`•
`
`•
`
`8 • AutoSOCKS v2.1 Administration and User’s Guide
`
`Petitioner Apple - Ex. 1021, p. 12
`
`

`

`c. When the SOCKS negotiation is completed, AutoSOCKS notifies the application.
`From the application’s point of view, the entire SOCKS negotiation including the
`authentication negotiation, is merely the TCP handshaking.
`3. The application transmits and receives data.
`If an encryption module is enabled and selected by the SOCKS server, AutoSOCKS encrypts
`the data on its way to the server on behalf of the application. If data is being returned,
`AutoSOCKS decrypts it so that the application sees clear text data.
`
`AutoSOCKS Platform Requirements
`AutoSOCKS runs under Windows 3.1, Windows for Workgroups 3.11, Windows 95, and
`Windows NT 3.51 and 4.0. These five platforms can be divided into two groups. Operating
`requirements and interface features unique to each group are described below.
`
`Windows 95 and Windows NT 4.0
`Windows 95 and Windows NT 4.0 have virtually identical interfaces. AutoSOCKS commands
`are accessed in the Programs list located on the Start menu and from the minimized
`AutoSOCKS icon on Taskbar tray.
`
`System Requirements
`AutoSOCKS system requirements for Windows 95 and Windows NT 4.0 include the
`following:
`Pentium-based personal computer
`•
`• Windows 95 or Windows NT 4.0
`16 MB application RAM (8 MB on Windows 95)
`•
`3.5 MB hard disk space
`•
`16- or 32-bit WinSock-based TCP/IP application(s)
`•
`• Network-accessible SOCKS v4 or SOCKS v5 compliant server
`• A WinSock compatible TCP/IP stack needs to be installed and configured prior to
`running AutoSOCKS. This can be the Microsoft-provided TCP/IP stack or a third-party
`TCP/IP stack.
`
`Interface Features
`• The AutoSOCKS program icon can be accessed via the Start menu, Programs option, and
`Aventail AutoSOCKS menu command.
`• When AutoSOCKS is running in the background, the AutoSOCKS icon is visible in the
`system tray (unless the Hide Icon command is enabled).
`• The AutoSOCKS system menu can be displayed by right-clicking the AutoSOCKS icon
`located in the Taskbar tray.
`• AutoSOCKS can be uninstalled via the Start menu by using the Add/Remove Programs
`icon in the Control Panel folder.
`
`Petitioner Apple - Ex. 1021, p. 13
`
`

`

`Windows 3.1, Windows for Workgroups 3.11, and Windows NT 3.51
`Windows 3.1, Windows for Workgroups 3.11, and Windows NT 3.51 have similar interfaces.
`AutoSOCKS commands are accessible from the Aventail AutoSOCKS program group and
`from the minimized icon’s System menu when AutoSOCKS is running.
`
`System Requirements
`AutoSOCKS system requirements for Windows 3.1, Windows for Workgroups 3.11, and
`Windows NT 3.51 include the following:
`486-based personal computer
`•
`4 MB application RAM for Windows 3.1 and Windows for Workgroups 3.11; 16 MB for
`•
`Windows NT
`3.5 MB hard disk space
`•
`16- or 32-bit WinSock-based TCP/IP application(s)
`•
`• Network-accessible SOCKS v4 or SOCKS v5 compliant server
`• A WinSock compatible TCP/IP stack needs to be installed and configured prior to
`running AutoSOCKS. This can be the Microsoft-provided TCP/IP stack or a third-party
`TCP/IP stack.
`
`Interface Features
`• The AutoSOCKS program icon is accessed via the AutoSOCKS program group window
`in Program Manager.
`• The AutoSOCKS system menu is displayed by clicking the AutoSOCKS icon located in
`the AutoSOCKS program group.
`• AutoSOCKS can be uninstalled using the Uninstall icon in the AutoSOCKS program
`group window.
`• When AutoSOCKS is running in the background, the AutoSOCKS icon is minimized on
`the desktop (unless the Hide Icon command is enabled)
`
`Installation Source Media
`Regardless of platform, AutoSOCKS can be delivered on CD; in a network-delivered, self-
`extracting archive file; or on diskette.
`This runs SETUP.EXE and installs AutoSOCKS. You can specify an installation directory, or
`AutoSOCKS will install in the default AutoSOCKS directory.
`• CD: The CD contains the AutoSOCKS installation program, SETUP.EXE. It also
`contains in the \DOCS directory the AutoSOCKS v2.1 Administration and User’s Guide
`formatted for Acrobat Reader.
`
`10 • AutoSOCKS v2.1 Administration and User’s Guide
`
`Petitioner Apple - Ex. 1021, p. 14
`
`

`

`• Network Delivered Source Media: The network-delivered source media is a self-
`extracting archive containing the required disk/directory structure within the archive file.
`The archive filename will be similar to AS21ED.EXE.
`• Diskette Based Source Media. The diskette based source media is composed of two
`separate disks (labeled Disk 1 and Disk 2) that contain all of the AutoSOCKS installation
`files.
`
`Installing AutoSOCKS
`AutoSOCKS can be installed to a single workstation or to multiple networked workstations. In
`either case, you must perform an initial installation of the software and create one or more
`configuration files. This procedure is described under "Individual Installation." Once the initial
`installation is complete, you can then install to a series of networked computers using the
`instructions and information described under “Network Installation.”
`Note: Check the Quick Start Card for an easy-to-follow guide to individual
`workstation installation.
`
`Configuration Files
`Integral to the initial installation of AutoSOCKS is deciding how SOCKS traffic should be
`redirected through the network. Network redirection rules (used to determine if and how
`SOCKS redirection should occur) are defined in the AutoSOCKS configuration file.
`Configuration files are initially created at the end of the installation process; however; they can
`be added, edited, and removed at any time using the Config Tool (in Windows 3.1, Windows
`for Workgroups 3.11, or Windows NT 3.51 via the System menu in the Aventail Program
`Group; in Windows 95 or Windows NT 4.0 via the Aventail icon in the Taskbar tray). The
`process of creating one or more configuration files is described under “Configuring
`AutoSOCKS.”
`If you are installing AutoSOCKS on multiple networked workstations, refer to “Network
`Installation” to determine the best method for maintaining and distributing configuration files.
`You can then proceed through the initial installation. An Installation Wizard will guide you
`through the steps, culminating with the option to create a configuration file.
`
`Individual Installation
`
`To install AutoSOCKS
`Before running Setup, it is advisable to close all open Windows applications.
`1.
`Installation procedures vary slightly, depending on which media source you use:
`If you are installing directly from CD-ROM, run SETUP.EXE from the AutoSOCKS
`•
`directory (\AS_v21).
`If you are installing directly from diskette, run SETUP.EXE on disk 1.
`
`•
`
`Petitioner Apple - Ex. 1021, p. 15
`
`

`

`•
`
`If you are installing from a network-delivered self-extracting archive, simply run the
`archive file. This will extract the installation files and automatically launch the setup
`program.
`The AutoSOCKS Installation Wizard then guides you through the process of installing
`the AutoSOCKS application.
`2. At the end of the Setup Program you can click the Yes, I want to view the README
`file box in the Setup Complete dialog box. This opens the README file for the latest
`information on AutoSOCKS.
`-OR-
`Simply click the Finish button to complete the Setup Program.
`
`12 • AutoSOCKS v2.1 Administration and User’s Guide
`
`Petitioner Apple - Ex. 1021, p. 16
`
`

`

`3. The setup program will then ask you if you want to restart now or later.
`
`4. After restarting your PC, start AutoSOCKS for the first time.
`5. AutoSOCKS will ask you if you want to run the Configuration Wizard.
`If you select Yes, then the Configuration Wizard will launch to help you create a new
`configuration file.
`If you select No, then AutoSOCKS will ask you to select a configuration file to use.
`6. After creating or selecting a configuration file, AutoSOCKS will now be finished
`installing.
`
`To uninstall AutoSOCKS
`The procedure to uninstall (remove) AutoSOCKS varies depending on whether you are
`running a 16- or 32-bit Windows operating system.
`! To uninstall AutoSOCKS from Windows 95 and Windows NT 4.0, double-click Add/Remove Programs
`in the Control Panel window, select AutoSOCKS from the list of programs on the Install/Uninstall tab, and
`click the Add/Remove button.
`! To uninstall AutoSOCKS on Windows 3.1, Windows for Workgroups 3.11, and Windows NT 3.51, use the
`Uninstall icon in the AutoSOCKS program group.
`
`Network Installation
`In general, the process of installing AutoSOCKS to multiple networked workstations involves
`selection of a file server to use, creation of a staging area for the AutoSOCKS software, and
`copying the AutoSOCKS files to a shared network directory from the source media. Additional
`
`Petitioner Apple - Ex. 1021, p. 17
`
`

`

`options include adding a default configuration file, and creating a universal batch/script file
`that specifies required default command line options when executed by the end user or
`installati

This document is available on Docket Alarm but you must sign up to view it.


Or .

Accessing this document will incur an additional charge of $.

After purchase, you can access this document again without charge.

Accept $ Charge
throbber

Still Working On It

This document is taking longer than usual to download. This can happen if we need to contact the court directly to obtain the document and their servers are running slowly.

Give it another minute or two to complete, and then try the refresh button.

throbber

A few More Minutes ... Still Working

It can take up to 5 minutes for us to download a document if the court servers are running slowly.

Thank you for your continued patience.

This document could not be displayed.

We could not find this document within its docket. Please go back to the docket page and check the link. If that does not work, go back to the docket and refresh it to pull the newest information.

Your account does not support viewing this document.

You need a Paid Account to view this document. Click here to change your account type.

Your account does not support viewing this document.

Set your membership status to view this document.

With a Docket Alarm membership, you'll get a whole lot more, including:

  • Up-to-date information for this case.
  • Email alerts whenever there is an update.
  • Full text search for other cases.
  • Get email alerts whenever a new case matches your search.

Become a Member

One Moment Please

The filing “” is large (MB) and is being downloaded.

Please refresh this page in a few minutes to see if the filing has been downloaded. The filing will also be emailed to you when the download completes.

Your document is on its way!

If you do not receive the document in five minutes, contact support at support@docketalarm.com.

Sealed Document

We are unable to display this document, it may be under a court ordered seal.

If you have proper credentials to access the file, you may proceed directly to the court's system using your government issued username and password.


Access Government Site

We are redirecting you
to a mobile optimized page.





Document Unreadable or Corrupt

Refresh this Document
Go to the Docket

We are unable to display this document.

Refresh this Document
Go to the Docket