https://www.netmax.com/order/support/support.cgi

If you have a VPN license number registered, you'll be able to click on VIEW PRODUCTS, click on the product ID (NOT THE USER ID) next to the VPN Product, and download the current version of the SafeNet IRE client.

This is not an upgrade, but is the full program of the latest version. This is where we will be posting the latest versions as they come out so you will always be able to download the most current version from this area.

The first version released on CD with the VPN Server Suite was version 5.1.1 Build 2.

Update: NetMAX no longer has an OEM partnership with IRE/SafeNet and is no longer offering their VPN client software with its VPN Server Suite or seperately. We are also unable to offer further upgrades. If you wish to purchase the current version of the software, now called SoftRemote, please visit SafeNet's web site at www.safenet-inc.com.

Issues addressed in 5.1.3 Build 4:

Changing a policy selection from "secure" to "block" defaults to "IP Address".

Description: If a policy entry has IP Range or IP subnet as the ID Type set to secure, changing this to Block changes the ID Type to IP Address. Changing back to Secure leaves the entry at IP Address.

Changing policy entry from Block to Secure changes ID type.

Description: If a policy entry has IP Range or IP subnet as the ID Type set to Block, changing this to Secure changes the ID Type to Domain Name. Changing back to Block changes the entry to IP Address.

Connection Monitor data is incorrect when Secure Other Connections SA is established.

Description: When the Other Connections entry is set to Secure and an SA is established on that connection, the data presented for that SA in Connection Monitor is incorrect.

Soft-PK does not work with the Windows Me (Millennium Edition) Dial-up Adaptor.

Description: Hardware profile (Dial-Up only). Connect to the ISP, SPDedit shows the correct ISP address assigned to the PPP adapter, but no secure sessions are even attempted. "Winipcfg" shows the ISP's ip address assigned to the PPP adapter; but "ipconfig" shows the ISP's ip address assigned to Ethernet adapter 1, and Ethernet adapter 0 has no ip address.

L2TP adapter reports Error 10049 when attempting to add default route to LNS.

Description: When L2TP connection configured to use default gateway on remote network, the default route is not added. See message below. Interface added: 172.23.11.21/255.255.0.0 on L2TP "SafeNet_VPN". 08:08:13.622 Error sending to interface address: 10049.

Elements of distinguished name were limited to 50 characters.

Description: When entering the value for each element of the peer's distinguished name (e.g. Name=, Department=, etc.), the entry field was limited to 50 characters. This was found to be too short for some customers. Each field has been increased to 256 characters.

Adding default route to L2TP LNS fails when client is using DHCP.

Description: Adding default route to L2TP LNS fails when client is using DHCP. This makes L2TP useless if the "use remote default gateway" option is checked for the dial-up / l2tp connection. In the log viewer you see the message "unable to determine default gateway". Also when you first open the log viewer, the "interface added ..." line has an IP address but not a subnet mask.

Retrieved CA cert with SCEP properties should overwrite existing CA cert with no SCEP properties.

IPSEC sessions do not initiate over L2TP connection on WinMe.

Description: Client configuration is FIXED IP address on NIC with L2TP over Ethernet. L2TP interface gets added and route gets added when IREIKE dated 11/10/00 (NT 10049 fix) is used. IPSEC traffic does not initiate over the L2TP adapter.

L2TP interface lost logged in viewlog even though interface is still present.

Description: This problem only seems to occur against the Springtide L2TP gateway. Interface lost message is immediately logged after interface added even though the interface is there. ifaces, ifacelist and winipcfg show the address present. If Use DGW is checked as soon as interface is logged as being lost then route is removed. If L2TP over dial-up is being performed, then view log continuously logs interface added messages for bogus addresses (i.e. 0.0.0.38/0.0.0.0 on LAN, 129.97.174.204/0.0.0.0 on LAN even though I am using a hardware profile with Ethernet card disabled.).

Blue screen when attempting a new connection after an L2TP session.

Description: After a successful L2TP session an attempt to create an L2TP session results in Break Due to KeBugCheckEx (Unhandled kernel mode exception) Error A (IRQL_NOT_LESS_OR_EQUAL).

Dialup networking fails to respond if you disconnect an active L2TP session on WinNT and the system hangs on shut down.

Description: Dialup networking fails to respond if you disconnect an active L2TP session on WinNT and the system hangs on shut down.

IREIKE.EXE crash on Win95 o or Win95a.

Description: When ireike starts during boot up on Win95o or Win95A, it crashes due to missing functions in RAS. This could be avoided with an upgraded to DUN1.3.

CERTIFICATEISSUER entry corrupted on policy save.

Description: When saving a policy, all connections using certificates, whose My Identity page has not yet been visited, have their CERTIFICATEISSUER entry corrupted in the Registry.
address-suppressed