Hot Downloads

Welcome, Guest
Username: Password: Remember me

TOPIC: SecureClient can not reach office PCs

SecureClient can not reach office PCs 11 years 5 months ago #9013

  • 1ding
  • 1ding's Avatar
  • Offline
  • New Member
  • Posts: 1
  • Karma: 0
SecureClient can not reach office PCs which has not been configured with default gateway.

Such as the checkpoint internal IP addres: 10.10.10.254, which will be used as office PCs default GW.

If the secureclient can reach the office PCs which has been configured with deault gateway (10.10.10.254).

But SecureClient can not reach office PCs which has not been configured with default gateway.
The administrator has disabled public write access.

SecureClient 11 years 5 months ago #9022

  • TheBishop
  • TheBishop's Avatar
  • Offline
  • Moderator
  • Posts: 1719
  • Thank you received: 8
  • Karma: 5
If I understand your scenario correctly then I think you will need the default gateway configured on your PCs if SecureClient is to work. A VPN by definition needs to be a tunnel between two endpoints and usually the endpoints have to be on differing IP networks to allow your traffic to be routed down the tunnel. Because of this your PCs will need to know the address of the Checkpoint box as the gateway to devices not on the same IP network as themselves.
The administrator has disabled public write access.
Time to create page: 0.072 seconds

CCENT/CCNA

Cisco Routers

  • SSL WebVPN
  • Securing Routers
  • Policy Based Routing
  • Router on-a-Stick

VPN Security

  • Understand DMVPN
  • GRE/IPSec Configuration
  • Site-to-Site IPSec VPN
  • IPSec Modes

Cisco Help

  • VPN Client Windows 8
  • VPN Client Windows 7
  • CCP Display Problem
  • Cisco Support App.

Windows 2012

  • New Features
  • Licensing
  • Hyper-V / VDI
  • Install Hyper-V

Linux

  • File Permissions
  • Webmin
  • Groups - Users
  • Samba Setup