3.6.3B is recommended, no problem there. The release notes were sent to the CCO people at the same time as the client software, but for some reason they went missing, we're working on getting them re-posted. For the time being, here's what they contain:
The following bugs have been resolved in Release 3.6.3.B
Revision: Release 3.6.3.B
CSCdy50212 - Routing problems when using Non-English version of Windows 2000
CSCdz41646 - Req: Show DN of certificate being used during connection establishment
CSCdw61796 - Certificate Validation failure events need more detail
CSCdv43347 - Client should display error on Connection Status if cert not found
CSCdz23365 - MSGINA.DLL not used as incompatiblegina when specified
CSCdz61884 - tunnel indicator in W2k registry not reset when tunnel terminated
CSCdy81064 - Adapter IP changed event needs to identify IP addresses
CSCdz56951 - Mobile GPRS dial-up...VPN wait time before tunnel establishment
CSCdx54679 - Client should notify Novell (if installed) after connection
CSCdz62411 - VPN client does not show disconnected after 3000 initiated disconnect
CSCdz72657 - XAuth process takes too long to create
CSCdz26371 - Client NAT-T payloads makes concentrator think its behind a NAT box
New Feature: VPN Client XAuth with Radius SDI (EDCS-253192)
Connection Entry profiles now can have a flag "RadiusSDI" to enable better handling of Radius SDI XAuth requests. If the flag is zero, then everything works the same as before. If the flag is one, then the client assumes Radius SDI is being used for XAuth. The default value is zero. Refer to EDCS-253192 for more information, including descriptions of some new vpnclient.ini parameters.
In addition, a connection entry profile can also have a flag "SDIUseHardwareToken" to instruct the client to ignore the presence of RSA SoftID software. If this flag is zero, then everything works the same as always. If the flag is one, then the client will ignore RSA SoftID software installed on the machine. The default value is zero.
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...