Server User Manual
Table Of Contents
- SDS/SCS/STS/MDC User’s Guide
- Table of Contents
- Preface
- Introduction
- Hardware and Connectivity
- Configuration Methods
- Getting Started
- Using DeviceManager and WebManager
- Network Settings
- Configuring Serial Ports
- Introduction
- Serial Ports
- Serial Port Profiles
- Common Tabs
- Console Management Profile
- TruePort Profile
- TCP Sockets Profile
- UDP Sockets Profile
- Terminal Profile
- User Service Settings
- Printer Profile
- Serial Tunneling Profile
- Virtual Modem Profile
- Control Signal I/O Profile
- Modbus Gateway Profile
- Power Management Profile
- Remote Access (PPP) Profile
- Remote Access (SLIP) Profile
- Custom Application Profile
- Port Buffering
- Advanced
- Configuring Users
- Configuring Security
- Configuring I/O Interfaces
- Configuring Clustering
- Configuring the Option Card
- Configuring the System
- Controlling the RPS, I/O Channels, and IPsec Tunnels
- System Administration
- Introduction
- Managing Configuration Files
- Downloading IOLAN Firmware
- Calibrating I/O
- Setting the IOLAN’s Date and Time
- Rebooting the IOLAN
- Resetting the IOLAN to Factory Defaults
- Resetting the SecurID Node Secret
- Language Support
- Downloading Terminal Definitions
- Resetting Configuration Parameters
- Lost Admin Password
- Applications
- RADIUS and TACACS+
- SSL/TLS Ciphers
- Virtual Modem AT Commands
- Pinouts and Cabling Diagrams
- Setting Jumpers
- I/O Wiring Diagrams
- Utilities
- Accessories
- Troubleshooting
- Introduction
- Hardware Troubleshooting
- Communication Issues
- DeviceManager Problems
- Host Problems
- RADIUS Authentication Problems
- Login Problems
- Problems with Terminals
- Unknown IP Address
- DHCP/BOOTP Problems
- Callback Problems
- Language Problems
- Modem Problems
- PPP Problems
- Printing Problems
- Long Reboot Cycle
- SSL/TLS
- I/O Models
- IPv6 Issues
- Contacting Technical Support
- Glossary
- Index
237
VPN
L2TP/IPsec
Many operating systems support L2TP/IPsec VPN tunnels, however, Windows XP requires this VPN
tunnel protocol. When L2TP/IPsec is enabled, the IOLAN will listen for L2TP/IPsec VPN tunnel
requests.
When you enable L2TP/IPsec, you are requiring that all access to the IOLAN go through the
L2TP/IPsec tunnel, so you must configure any exceptions first (see
Exceptions on page 238 for more
information on exceptions) or you will not be able to access the IOLAN through the network unless
you are configured to go through the L2TP/IPsec tunnel (you can still access the IOLAN through the
Console port).
Field Descriptions
Configure the following parameters:
Allow L2TP/IPsec
connections
When enabled, the IOLAN listens for L2TP/IPsec VPN tunnel connections.
Note: to allow non-VPN tunnel connections to the IOLAN, you must create
entries in the VPN Exceptions list.
Default: Disabled
Local IP Address The IPv4 address that the IOLAN will listen on for L2TP/IPsec connections. If
the default value (0.0.0.0) is kept, the IOLAN will use the
Default Gateway
value (if no
Default Gateway is specified, L2TP/IPsec VPN connections will
not be established).
Default: 0.0.0.0
Authentication
Method
Specify the authentication method that will be used between VPN peers to
authenticate the VPN tunnel.
Data Options:
z Shared Secret—A text-based secret that is used to authenticate the IPsec
tunnel (case sensitive).
z X.509 Certificate—X.509 certificates are used to authenticate the IPsec
tunnel. When using this authentication method, you must include the
signing authority’s certificate information in the SSL/TLS CA list and
download it to the IOLAN.
Default: Shared Secret