Re: Checkpoint VPN Client stopped working
prisaz
Legend

DFC

Good catch I never thought it might be your public address. duh I should have thought of that. 108.10.x.x  for example was reallocated to Frontier Communications of America, Inc. But still shows up under Verizon's parent address block. Some routers may have issues with the tables and or the reallocation of these addresses.

See this link. It looks like Frontier picked up these addresses from Verizon and your checkpoint firewall may have said these don't belong to them.

http://whois.arin.net/rest/org/FRTR/pft

and

http://whois.arin.net/rest/net/NET-108-0-0-0-1/pft

Also I read this from the above link.

"ARIN has attempted to validate the data for this POC, but has received no response from the POC since 2011-07-12"

Now depending on your location, your router may have been holding onto an old address. I do not know the whole address you had or subnet, but I looked up the above. I see the routing tables may be a mess for this whole subnet. Perhaps the transfer was not completed properly. I have passed this information over to some Verizon people, just in case it is an issue for others.

Your issue may be totally solved, as long as Verizon is still not giving out addresses they reassigned.

0 Likes
Re: Checkpoint VPN Client stopped working
mpb11
Newbie

Hi

Our company just switched to Checkpoint and I am now having this same issue. Can you please give me the fix.

Thank you

0 Likes