Windows NT 4.0 Installing the AltaVista Tunnel Extranet Serverfor Windows NT
7.2.3 Installing the AltaVista Tunnel Telecommuter Client for Windows
The Telecommuter Tunnel is distributed on 3.5-inch disks and via the Internet as a .ZIP file. Once the installation files are obtained, run the setup.exe file and follow the directions as they appear. All Tunnel files will be installed to this default path: C:\AltaVista\Tunnel\Program. You will be given the option to change this path at the time of installation. When installing on Windows NT, you must first open the Networking control panel, open the Services dialog screen, and select Add. Type in the path to the directory and drive where the installation files reside, and click OK. A dialog box will appear with the AltaVista Tunnel as an installation option. Clicking on this option initiates the installation process. The following files are available in the Program folder: etunnel.exe This starts the AltaVista Telecommuter Tunnel client. krm.exe The Keyring Manager is a database of encryption keys available to the client. etunnel.hlp This is a comprehensive help file for configuring and using the Tunnel client.7.2.4 Installing the AltaVista Tunnel Telecommuter Client for MacOS
The minimum requirements for the Telecommuter Client for MacOS are as follows: a PowerPC processor, MacOS version 7.5 or later, Open Transport 1.1.1 or later, 16 MB of memory, and 1 MB of free disk space. The client is distributed either on floppy disk or via AltaVistas download site in binhex format. Once the media is decompressed, double-click on the AltaVista Tunnel Install icon. In the installation window, drag the Tunnel icon to the System Startup disk. You will be prompted to restart by the installer. 110 To start the tunnel application, simply double-click on the AltaVista Tunnel Setup icon in the AlstaVista Tunnel folder on your System Startup disk. Configuration of the AltaVista tunnel client is covered in Section 7.4 later in this chapter.7.3 Configuring the AltaVista Tunnel Extranet and Telecommuter Server
The configuration of the AltaVista Tunnel Extranet and Telecommuter servers are fairly generic across platforms. Both servers install identically. Most references in this section apply specifically to the Windows NT configuration. Any quirks in the Unix configuration are noted. The first step is to decide which physical servers or computers on the local network will be allowed tunnel traffic. Next, create a group of dynamic IP addresses. There should be twice as many IPs as tunnels to connect to the tunnel server. A pair of IP addresses will be assigned to each end of the connecting tunnel, one for the servers interface and one to the end users. Note that Windows NT versions of the ExtranetTelecommuter server are capable of connecting only a certain number of tunnels, so be sure to check the number of tunnels needed. Once these items are taken care of, the administrator must decide which tunnel groups are needed. As explained in Chapter 6 , the administrator is able to configure the tunnel server for several different groups. Each group would have different users and connection attributes. Users can belong to one or more groups, depending on their needs and duties. For example, the network administration staff should belong to all groups for testing and troubleshooting purposes.7.3.1 Adding Routes and Dynamic Addresses
These tasks make your network configuration known to the AltaVista Tunnel.7.3.1.1 Initial configuration
After the tunnel groups are planned out, youre ready to begin configuration. When you launch the Tunnel Manager for the first time, you will be prompted to enter the routed network and dynamic range for the tunnel server. First, the network available to the tunnel groups is added to the server. In Figure 7-1 , the following variables are required: Subnet This is the subnet of the network addresses on the local network that are part of the tunnel. Traffic destined for these IP addresses will use the tunnel network. Should this route contain the entire local network, a zero as the last IP address position is required. For instance: 205.196.222.0. Netmask This is the Netmask corresponding to the assigned subnet.Parts
» Virtual Private Networks 2nd 1999
» How VPNs relate to Intranets
» What Are We Protecting with Our VPN?
» Firewalls How VPNs Solve Internet Security Issues
» Authentication How VPNs Solve Internet Security Issues
» Encryption How VPNs Solve Internet Security Issues
» Tunneling How VPNs Solve Internet Security Issues
» A Note on IP Address and Domain Name Conventions Used in This Book
» Packet restriction or packet filtering routers
» Bastion host What Types of Firewalls Are There?
» DMZ or perimeter zone network
» Proxy servers What Types of Firewalls Are There?
» A Brief History of Cryptography
» Cryptography: How to Keep a Secret
» Cryptography in Network Communications
» Hash algorithms Cryptographic Algorithms
» Secret key systems Cryptographic Algorithms
» Public key cryptosystems Cryptographic Algorithms
» Use of Cryptosystems and Authentication in a VPN
» ESP Encapsulating Security Payload
» AH Authentication Header VPN Protocols
» Internet Key Exchange, ISAMKPOakley
» ISO X.509 v.3 Digital Certificates
» LDAP Lightweight Directory Access Protocol Radius
» PPTP Point-to-Point Tunneling Protocol
» Basic Firewalling Methodologies for Compromising VPNs
» Ciphertext-only attack Cryptographic Assaults
» Known plaintext attack Cryptographic Assaults
» Chosen plaintext attack Cryptographic Assaults
» Chosen ciphertext attack Cryptographic Assaults
» Brute force attacks Cryptographic Assaults
» Password guessers and dictionary attacks
» Social engineering Cryptographic Assaults
» Address spoofing Network Compromises and Attacks
» Session hijacking Network Compromises and Attacks
» Man-in-the-middle attack Network Compromises and Attacks
» Replay attack Network Compromises and Attacks
» Detection and cleanup Network Compromises and Attacks
» Patents and Legal Ramifications
» General WAN, RAS, and VPN Concepts
» Telco Small to Medium Solutions
» Security, scalability, and stability
» Hardwaresoftware Small to Medium Solutions
» Administration Small to Medium Solutions
» Hardwaresoftware Administration Security, scalability, and stability
» Differences Between PPTP, L2F, and L2TP
» Dialing into an ISP That Supports PPTP
» Dialing into an ISP That Doesnt Support PPTP
» Where PPTP Fits into Our Scenario
» The encapsulation process Dissecting a PPTP Packet
» Accept encrypted authentication RAS authentication methods
» Accept Microsoft encrypted authentication
» Accept any authentication, including clear text
» Data encryption PPTP Security
» Availability Features of PPTP
» Easy Implementation Features of PPTP
» Multiprotocol Tunneling Features of PPTP
» Ability to Use Corporate and UnregisteredIP Addresses
» Choosing the protocols to tunnel
» Choosing your authentication method
» IP address negotiation using DHCP
» Outbound authentication using PPTP filtering
» Filtering caveats PPTP Filtering
» Installing PPTP Filtering by IP Address
» Configuring Users for Dial-up Access
» Configuring PPTP for Dial-up Networking on a Windows NT Client
» Configuring PPTP for Dial-up Networking on a Windows 95 or 98 Client
» Setting up global PPTP parameters Setting up a port for PPTP
» Configuring PPTP on an Ascend MAX 4004
» Making the Calls Configuring and Testing Layer 2 Connections
» The Event Viewer Login problems
» The Dial-Up Networking Monitor
» ping and traceroute Connectivity Testing
» Fixed IP addresses How to Allow PPTP Through Firewalls
» How PPTP Can Bypass a Proxy Server
» Three-part encryption technique Security
» Support for an emerging security standard
» Support for Security Dynamics SecureID
» Accessibility Flexibility Advantages of the AltaVista Tunnel System
» Platform Limitations AltaVista Tunnel Limitations
» Extranet server System Considerations
» Telecommuter client System Considerations
» Planning How the AltaVista Tunnel Works
» AltaVista Tunnel Extranet server
» Security procedures The Guts
» AltaVista Tunnel Telecommuter Client
» Sample configuration Implementing a LAN-to-LAN Tunnel
» Tunnel server configuration Implementing a LAN-to-LAN Tunnel
» Firewall configuration Host configuration
» Sample configuration Implementing Single Connections-to-LAN Tunnels
» Tunnel server configuration Implementing Single Connections-to-LAN Tunnels
» Firewall configuration Implementing Single Connections-to-LAN Tunnels
» Local host configuration Implementing Single Connections-to-LAN Tunnels
» Remote PC configuration Implementing Single Connections-to-LAN Tunnels
» Sample configuration Implementing PC-to-WAN Tunnels
» Tunnel server configuration Implementing PC-to-WAN Tunnels
» Tracing the packets Implementing PC-to-WAN Tunnels
» Preparing to Install Installing the AltaVista Tunnel
» Windows NT 4.0 Installing the AltaVista Tunnel Extranet Serverfor Windows NT
» Installing the AltaVista Tunnel Telecommuter Client for Windows
» Installing the AltaVista Tunnel Telecommuter Client for MacOS
» Initial configuration Adding Routes and Dynamic Addresses
» Managing routes and dynamic IPs
» Group configuration Adding Tunnel Groups
» Tunnel client information Adding Tunnel Groups
» Tools for Tunnel Management Changing Port Settings
» Rekey Interval and Minimum Encryption Settings
» Configuring Unix-to-Windows NT Tunnel Connections
» Getting Busy Configuring the AltaVista Telecommuter Client
» Tunnel Server and Client Configuration Checks
» Local Network and Internet Gateway Configuration Checks
» Encryption Capabilities The SSH Software
» Useful sshd parameters for our purposes
» Understanding SSH authentication ssh
» Useful ssh parameters for our purposes
» The VPN Components Creating a VPN with PPP and SSH
» Setting up the master and slave Linux systems
» Creating a user account on the slave
» Setting up SSH authentication
» Configuring sudo on the slave
» Putting pty-redir on the master
» Setting up the slaves scripts
» Testing the Connection Creating a VPN with PPP and SSH
» A Performance Evaluation Creating a VPN with the Unix Secure Shell
» ISP Assigned Addresses Global Pool
» Hardware solution Advantages of the PIX Firewall
» Superior to Unix and other router firewalls
» Single point of controlfailure
» Dynamic address translation Advantages of the PIX Firewall
» PIX acts like a proxy server
» Ease of configuration and maintenance
» High-speed access Advantages of the PIX Firewall
» Links Advantages of the PIX Firewall
» Hardware solution Limitations of the PIX Firewall
» Dynamic address use Limitations of the PIX Firewall
» Budgetary considerations Limitations of the PIX Firewall
» Maintenance Limitations of the PIX Firewall
» A Sample Configuration Configuring the PIX as a Gateway
» Firewall Configuration on the PIX
» debug xlate Testing, Tracing, and Debugging
» arp Testing, Tracing, and Debugging
» show interface Testing, Tracing, and Debugging
» Offering Services to the Internet Through Conduits and the static Command
» Tunneling with the link Directive
» Choosing an ISP Managing and Maintaining Your VPN
» Connectivity Problems Solving VPN Problems
» Authentication Errors Solving VPN Problems
» Routing Problems Dealing with an ISP
» Compatibility with Other Products
» Delivering Quality of Service
» Restrict What VPN Users Can Get To
» Avoid Public DNS Information for VPN Servers and Routers
» Keeping Yourself Up-to-Date Managing and Maintaining Your VPN
» Network Connections Hardware and Operating System VPN Package
» Connection Hardware and Operating System VPN Package
» Connection Hardware and Operating System
» VPN Package Remote Access Users
Show more