- Posts: 6
- Thank you received: 0
VPN CheckPoint - SecuRemote
17 years 5 months ago #22039
by shaj
Replied by shaj on topic Re: VPN CheckPoint - SecuRemote
Hi thanks for your response.
Yes I agree it's messy, it's because I don't have a public IP address on the external interface of my firewal otherwise it will work just fine.
Unfortunatlly my Internet provider SKY only provide me dynamic IP there therefore I use dynamic DNS to resolve to my dnamic IP. So, as you say my dynamic DNS does resolve to the routeable public address to the Netgear router. And when I make my initial connection I do use the public address of the router.
The problem is once I made the initial connection and and after the client downloaded the topology and a site is created, the VPN client inserts 192 address as the destination address for connections to take part in the tunnel.
There is no way I can change this in the client.
So, another words had my external interface of my firewall been public address it will work.
Is there any way around this ? Thanks
Yes I agree it's messy, it's because I don't have a public IP address on the external interface of my firewal otherwise it will work just fine.
Unfortunatlly my Internet provider SKY only provide me dynamic IP there therefore I use dynamic DNS to resolve to my dnamic IP. So, as you say my dynamic DNS does resolve to the routeable public address to the Netgear router. And when I make my initial connection I do use the public address of the router.
The problem is once I made the initial connection and and after the client downloaded the topology and a site is created, the VPN client inserts 192 address as the destination address for connections to take part in the tunnel.
There is no way I can change this in the client.
So, another words had my external interface of my firewall been public address it will work.
Is there any way around this ? Thanks
Time to create page: 0.108 seconds