14.1.2.11.4 Connection with L2TP Client
298
For certificate based authentication the SX-GATE VPN server
certificate must have been issued with the "Subject alternativ
names" set to the IP or DNS name which has been configured
as server name in the MacOS client.
Compatibility for old Windows clients
If the builtin client of Windows 2000 or Windows XP before Servicepack 2 is in use,
you will either have to update them with Microsoft update Q818043 or enable this
compatibility switch. The switch will set the port of the tunnel's local end to 0.
Ignore WinXP nat-oa bug
Windows XP clients which are situated behind a NAT router don't provide their internal
IP address as expected. SX-GATE includes a workaround for this bug.
You can disable the workaround with this switch. SX-GATE then treats the XP client
as if it were directly connected to the Internet (without NAT router), using a valid IP
address. This was the behaviour of SX-GATE up to and including version 5.1.
Disable the workaround, if the same internal IP address was
assigned to multiple XP clients by their respective NAT router.
All of them will then be able to connect simultaneously.
Always negotiate NAT Traversal
Enable this option for clients using NAT Traversal even when not situated behind a
NAT router.
When enabled, both SX-GATE and the client seem to be behind
NAT.
Routing gateway
For proper setup of the routing table you have to provide the gateway. If SX-GATE and
the peer are members of the same network segment, please select the corresponding
option.
14.1.2.11.4-E
Commands
Action
This control allows you to manually change the connection state.