| CPUG | |
| The Check Point User Group | |
| A Resource For The Check Point Community. Fast. Useful. Independent. | |
|
| |||||||
![]() |
| | LinkBack | Thread Tools | Display Modes |
| |||
| It is the default behavior... Secureclient intercepts traffic and decides if it must be encrypted or not (depends on the firewall topology or encryption domain). There is an option in secureclient which allows you to route all the secureclient traffic through the tunnel (right click on icon > settings > properties on profile > Advanced tab > Route all traffic through gateway) Arno |
| |||
| Hi there I am having a similar issue, I think it possible that Desktop Security could be either overriding this or preventing it happening, could somebody confirm this for me? It has also been stated that SecuRemote does not include Desktop Security Policy and therfore could help me bypass this issue. Thanks for any help or suggestions, Darren. |
| |||
| It is done using the DNS Servers defined in Office Mode, for Secure Client, or your SecuRemote DNS Servers for SecuRemote. The important part in getting it working is the domain name that you specify in the definition in the Dashboard. There is no Tag as such to do this. |
![]() |
| Thread Tools | |
| Display Modes | |
| |