(Category) (Category) NetMAXFAQ : (Category) NetMAX VPN Server Suite (Virtual Private Networking) :
3rd Party Compatibility Notes
Information on the interoperability of other VPN servers/clients with NetMAX VPN Suite

address-suppressed
Subcategories:

Answers in this category:
(Answer) Can other Windows IPSec compliant VPN clients be used?
(Answer) Is the NetMAX VPN Server Suite interoperable with Cisco PIX Secure Firewall?
(Answer) Is the NetMAX VPN Server Suite interoperable with Checkpoint FW-1?
(Answer) What programs are known to conflict with the NetMAX IRE client?
(Answer) Why does Windows 2000 MTU settings cause problems with NetMAX VPN gateway communications?
(Answer) Can the native IPSEC component in Windows 2000/XP connect as a VPN Road Warrior?

(Answer) (Category) NetMAXFAQ : (Category) NetMAX VPN Server Suite (Virtual Private Networking) : (Category) 3rd Party Compatibility Notes :
Can other Windows IPSec compliant VPN clients be used?
Applies to: All versions of NetMAX VPN Server Suite
address-suppressed
The NetMAX VPN Server Suite has been tested for interoperability with SafeNet SoftRemote as well as Intel Netstructure (Shiva). The results of the Shiva test can be seen at the following location:
Intel Netstructure (Shiva) VPN Client

For other clients, ensure that the client software meets the requirements for communication with NetMAX VPN Server Suite, listed at: Technical Specifications

Also, FreeS/WAN keeps a list of compatible VPN clients in the documentation area of their website. NetMAX VPN Server is based on the FreeS/WAN project, so these clients are more likely to work with NetMAX.

Any information regarding interoperability with other products would greatly assist the further development of NetMAX VPN Server Suite, and may be submitted via email to support@netmax.com.
address-suppressed
(Answer) (Category) NetMAXFAQ : (Category) NetMAX VPN Server Suite (Virtual Private Networking) : (Category) 3rd Party Compatibility Notes :
Is the NetMAX VPN Server Suite interoperable with Cisco PIX Secure Firewall?
Applies to: NetMAX VPN Server Suite version 3.1 - 4.0x
address-suppressed
For information on interoperability with Cisco PIX Secure Firewall, see the Cisco PIX Secure Firewall Configuration Guide .

Please note that the document referred to by the link above is in PDF format.

Viewing PDF documents requires a PDF viewer, such as Adobe Acrobat Reader.
address-suppressed
(Answer) (Category) NetMAXFAQ : (Category) NetMAX VPN Server Suite (Virtual Private Networking) : (Category) 3rd Party Compatibility Notes :
Is the NetMAX VPN Server Suite interoperable with Checkpoint FW-1?
Applies to: NetMAX VPN Server Suite version 3.1 - 4.0x
address-suppressed
For information on interoperability with Checkpoint FW-1 (with 3DES), see the Checkpoint FW-1 Configuration Guide.

Please note that the document referred to by the link above is in PDF format.

Viewing PDF documents requires a PDF viewer, such as Adobe Acrobat Reader.
address-suppressed

(Answer) (Category) NetMAXFAQ : (Category) NetMAX VPN Server Suite (Virtual Private Networking) : (Category) 3rd Party Compatibility Notes :
What programs are known to conflict with the NetMAX IRE client?
Applies to: All versions of SafeNet SoftPK that were distributed by Cybernet
address-suppressed
The following programs are known to have conflicts with the NetMAX IRE SafeNet/Soft-PK VPN client, and should not be installed together on the same machine.

Microsoft®'s NetMeeting
JGAA's War FTP Daemon
Windows(tm) 2000

It is possible that the NetMAX IRE SafeNet/Soft-PK VPN client will not work on Windows ME.

Most conflicts involve the method in which the NetMAX IRE client takes control of the tcpstack (winsock).

Some of these conflicts have been addressed in later versions of SafeNet's VPN Client. This client can now be purchased directly from SafeNet.
address-suppressed

(Answer) (Category) NetMAXFAQ : (Category) NetMAX VPN Server Suite (Virtual Private Networking) : (Category) 3rd Party Compatibility Notes :
Why does Windows 2000 MTU settings cause problems with NetMAX VPN gateway communications?
Applies to: NetMAX VPN Server Suite version 3.1 - 4.0x
address-suppressed
We have found that Windows 2000 does not do MTU discovery by default, and it's MTU setting is by default set to 1500.

Most encapsulated protocols will have an MTU that is smaller than 1500 because additional bytes must be added to each packet. IPSEC requires an MTU of 1480. When a NetMAX VPN Server Suite gateway and a Windows 2000 machine begin an IP conversation, MTU discovery should allow the Windows 2000 machine to lower it's MTU setting to the one offered by the NetMAX in the MTU Discovery negotiation.

Since the Windows 2000 machine is set to not perform this MTU negotiation, it will continue to send packets that are 1500 bytes. If the Windows 2000 machine sends a packet larger than 1480 bytes, the NetMAX will be unable to accept the packet and will report this with an ICMP message asking the Windows 2000 machine to fragment packets larger than 1480 bytes. Windows 2000 ignores these ICMP messages.

This problem can be worked around by enabling MTU discovery on your Windows 2000 machines by making a registry entry:

Under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters, create a DWORD value with the name "EnablePMTUDiscovery", and the value of "1".

Modifying your registry is considered advanced configuration for Windows 2000 users and can cause serious problems if done incorrectly. We will not be able to support this. This article is for information purposes only, and we can not recommend your modifying the default behavior of Windows 2000.
address-suppressed

(Answer) (Category) NetMAXFAQ : (Category) NetMAX VPN Server Suite (Virtual Private Networking) : (Category) 3rd Party Compatibility Notes :
Can the native IPSEC component in Windows 2000/XP connect as a VPN Road Warrior?
Applies to: NetMAX VPN Server Suite version 3.1 - 4.0x
address-suppressed
The native IPSEC component in Windows 2000/XP can not make a Road Warrior connection to the 3.x versions of the NetMAX VPN Server Suite, because it does not support IPSEC aggressive mode negotiation.

The native IPSEC component in Windows 2000/XP only supports certificates for Road Warrior connections when using Microsoft's proprietary L2TP VPN protocol, which NetMAX does not support. This makes it unusable as a Road Warrior VPN client with NetMAX 4.x.

The Windows 2000/XP IPSEC component can support making a VPN connection to a NetMAX VPN Server Suite using Main Mode. Instructions are in the VPN Server Suite documentation.

If you would like to make a Road Warrior connection to a NetMAX VPN Server Suite using Windows 2000/XP, you will need a third party VPN client, such as SafeNET's SoftRemote.
address-suppressed

Previous: (Category) Troubleshooting VPN client connections
Next: (Category) Hints / Suggestions
This document is: http://www.netmax.org/cgi-bin/fom.cgi?file=351
[Search] [Appearance] [Show Top Category Only]
This is a Faq-O-Matic 2.721.
This FAQ administered by ...Cybernet Systems Corp.