| CPUG | |
| The Check Point User Group | |
| A Resource For The Check Point Community. Fast. Useful. Independent. | |
|
| |||||||
![]() |
| | LinkBack | Thread Tools | Display Modes |
| |||
| I have desktop security and secureclient clients working fine with office mode. However none of our secuRemote clients can connect. Is it either one or the other or have I missed something. They (secuRemote users) can authenticate ok, but not access any of the services behind the firewall. No dns seems available either, when using secuRemote... thanks for any help. |
| |||
| Check you Security rules for VPN communities: You can permit OfficeMode users matching by source subnet (office mode assigned subnet) You can Ignore VPN Community column. Traditional CheckPoint VPN users should be permitted by matching VPN community criteria. |
| |||
| Not quite sure what you are referring to. Are you saying that on the security tab the VPN column should be 'any'? Here is an example of what I currently have. I'd like some of the members of vpngroupA to be able to use secureclient (hence the desktop security) and others to be able to use securRemote. Currently secureclient users are fine, but securemote users can only log on... On the security tab, the rule is: SOURCE vpngroupA@any DEST. serverA VPN remoteaccess ACTION terminalservices, dns There is also the corrosponding desktop security policies: Inbound: SOURCE DESKTOP SERVICE ACTION enc-domain vpngroupA@any terminalservices encrypt any vpngroupA@any any drop Outbound: DESKTOP DEST. SERVICE ACTION vpngroupA@any enc-domain terminalservices encrypt |
![]() |
| Thread Tools | |
| Display Modes | |
| |