client and site to site vpn not working after introducing peplink device

[naomi.rampersad@gmail.com]

NGX 62 firewall was functional witha static routable Ip address on the external interface....
a PEPlink device was introduced and the firewall reconfiured with a static non routable ip address which is then natted to a public ip via the peplink, outbound connections are okay and static one-to-one nat for two internal servers is working however cannot connect to gateway via securelcient and also the site to site vpns are not working
when readding the site in the SC configuration the site gets added, certificate comes up but cannot authenicate the user, get a connection to gateway failure...
Has anybody troubleshooted this problem and it may have more to do with the external interace now having a private ip address...

[RayPesek]

When SecuRemote or SecureClient connect, they download the topology from the firewall as entered in the firewall so it is going to see the private IP address.

What happened to the old public IP address? Is it on the PePLink box?

Have you looked at this article Knowledge Base - PePLink to configure IPSec passthrough?

Ray

[naomi.rampersad@gmail.com]

yes the old public ip address now resides on the peplink device so the firewall external private ip address 172.16.0.5 is natted on the peplink device to 200.3.183.45 (public)

No I have not checked out the article, will do so now...

[naomi.rampersad@gmail.com]

I am working with a customer that has a vendor that put in the Peplink device, I spoke with him, showed him the article and he verified that it is all setup on the peplink device...
The problem seems to be that the IKe hnadshake is not being completed...