SecuRemote Adapter Bindings

[roadrunner]

SecuRemote Adapter Bindings
Before installing SecuRemote on a Win9x platform, the bindings look like the following:


Dial Up Adapter
TCP/IP -> Dial Up Adapter
SecuRemote installs two new things: A FW1 Protocol and an FW1 Adapter. The FW1 Adapter will be installed between the Dial Up Adapter than the TCP/IP stack so it can encrypt and decrypt traffic to/from the appropriate hosts. After installing SecuRemote, the bindings should look like:


Dial Up Adapter
FW1 (Dial Up Adapter)
FW1 Protocol -> Dial Up Adapter
TCP/IP -> FW1 (Dial Up Adapter)
If you have NICs, each NIC that has TCP/IP installed will have a FW1 Adapter and FW1 Protocol associated with it as well. Anything that may upset or otherwise change the bindings may require you to re-install SecuRemote to get it to function correctly again.

In Win2x and XP, you will only see one item called "Check Point SecuRemote" that is bound to all interfaces by default (or dialups is that is what is specified at startup). One can simply uncheck the appropriate checkbox on an adaptor to disable SecuRemote on a specific interface.

-- PhoneBoy - 13 Apr 2004


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

[delta99]

Hi there,

can i uncheck the securemote adapter bindings with a batchscript
on winxp?
a vnc-remote-connection over secureclient works fine.
if the remote-computer connect now with the company-lan, we disable
the securemote-service with a logon-script. But we can't get a connection
with the remote-computer as we uncheck the securemote binding on
the lan-adapter.

Has anybody an Idea?

Thank you for help

Alex