![]() Eventually it generates an IKE failure "No Response to Peer" I have attached the 1st log of the communication. This access currently does not work.įirewall logging indicates that this traffic attempts to be encrypted across the VPN Community. ![]() ![]() The 3rd party, now wants WebGUI access for users to use an A Record that resolves to the same PIP as the interoperable Device. Therefore this access is across the native internet, but does passthrough the checkpoint firewall that also peer's the IPSEC Tunnel. Essentially the 3rd party use the tunnel to keep printing traffic encrypted to client printers.Ĭurrently, users access 3rd party web portal by an A record with public IP address that differs to the PIP that the Interoperable Device is configured with. ![]() VPN Community is built so client private /16 and external party private /27 can communicate. Star Based IPSEC VPN Community, which is working perfectly fine to external 3rd party. I consider this a strange request, but will outline the situation. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |