This website uses Cookies. Click Accept to agree to our website's cookie use as described in our Cookie Policy. Click Preferences to customize your cookie settings.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- Discussions
- Network Security
- VM-Series in the Public Cloud
- Who Me Too'd this solution
Who Me Too'd this solution
Options
- Mark as New
- Subscribe to RSS Feed
- Permalink
04-19-2019 07:10 AM
From logs I found 10.90.0.200 did not match as Peer Identification, so I put that IP in IKE Gateway property as Peer Identification and my Public IP as Local Identification and problem got resolved.
Customer is saying I should not see this IP because their firewall is behind NAT and this is internal IP of their VPN gateway. I am still not sure why but tunnel came up.
I don't have this issue anymore.
Who Me Too'd this solution
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks