Hi All,Out of the blue one of our customer's S2S VPN has gone down and doesn't come up since. We have hundreds of other tunnels working just fine.The remote end - 999.999.999.25, peer named "WIBBLE-F2F" - says they have done no changes, and we didn't...
Hi!I'm still awaiting the remote side to come back to me on their troubleshooting efforts with their supplier.We tried swapping over policies and IKE versions relentlessly in a remote session last week, short on trying 3DES and MD5 (not going to happ...
Hi MHM!Remote side confirmed that nothing is blocking traffic and they can also see bidirectional movement on port 500.They are using a Fortigate firewall, and seeing the exact same retransmission debugs I do.We had an hour-long session today, moving...
@Rob Ingram wrote:@Mate.BarnaI'm very familar with HSCN/N3 network.Looks like there is bi-directional traffic, so there is a response at least. I do notice there are 2 x established SPIs, can you send me that packet capture file please (send DM) so I...
@MHM Cisco World wrote:https://www.petenetlive.com/KB/Article/0001531check this link, I think it solution for your casein other words, the other side using ACL that deny your ASA reply to ISAKMP, and hence other side send again, here you see the dupl...
@Rob Ingram wrote:@Mate.Barnaif the VPN was previously working then randomly changing settings is unlikely to resolve the issue.It seems like a communication issue from the debug provided, can you ping the remote peer IP address from your device?Is t...
