Killing SecuRemote Doesn't Kill Active Connections to Encryption Domain

[BarryStiefel]

Killing SecuRemote Doesn't Kill Active Connections to Encryption Domain



It appears that existing connections for different applications continue to have access to the internal network. These connections will continue to "stay alive" (and continue to remain encrypted) until one of the following occurs:

• The connection times out per the normal TCP_TIMEOUT value (usually 3600 seconds)
• The connection terminates normally

Unfortunately, there is no way to set a SecuRemote-specific connection timeout. In versions of SecuRemote prior to build 4153, only established connections were allowed to continue. It now also appears that new connections can be established, even with fwenc.exe killed.

In NG FP2 and later, you can eliminate this problem entirely by using Office Mode since this requires a setup process similar to dial-up networking.

-- PhoneBoy - 11 Apr 2004

FAQForm FAQs.Class: SecureClientFAQs, TroubleshootingFAQs FAQs.OS: FAQs.Version: