You are running the Security Gateway on SecurePlatform and configure SNX with default settings. The client fails to connect to the Security Gateway. What is wrong?

SNX modifies the client routing table automatically upon a successful connection; routing table modification failure is a post-connection symptom, not a cause of initial connection failure.

SNX uses Java or a native client for VPN functionality and does not depend on ActiveX, so blocking ActiveX would not prevent SNX from connecting.

The question specifies default settings are used, so client misconfiguration is ruled out as the cause - the issue is a server-side port conflict.

SecurePlatform's built-in Web User Interface listens on TCP port 443 by default, which is the same port that SNX requires for its HTTPS-based SSL VPN tunnel. This port conflict prevents the SNX client from establishing a connection to the Security Gateway. To resolve this, the WebUI port must be changed or disabled so that SNX can exclusively use port 443.