We're using a Cisco RV320 at one of our locations.
It's primarily used for two Hardware VPN's using IPSec. Tunnel 1 goes to our hosted server (which has no issues) and Tunnel 2 goes to a Rogers hosted server.
Recently, the Rogers hosted server location changed their WAN IP. Therefore, I rebuilt Tunnel 2 to point to the new WAN IP and was able to establish the connection and the Tunnel went UP. All remote LAN IP's and IPSec protocols remained the same, the only change was the WAN IP.
Since this change, accessing remote server resources on Tunnel 2 is intermittent. i.e in the morning it will be inaccessible, but a few hours in the afternoon it will be accessible During this whole time, VPN Tunnel 2 remains UP and doesn't go down, we just cannot communicate with the Remote LAN IP....
I asked the Rogers tech to change back to the old Remote WAN IP for testing. As soon as we changed back to the old Remote WAN IP, all resources became available again..... We then changed back to the new Remote WAN IP and server resources once again became unavailable. During these VPN changes, I've made sure to reboot our Cisco RV320 numerous time's as well as rebuilt this tunnel.
In addition to this, we have 4 other locations with the same Cisco RV320 on the same firmware connecting to the old Remote WAN IP of the Rogers hosted server. We briefly tested the remote WAN IP change on another router's Tunnel 2, and the same issue occurred as it did on the other one.
My suspicion is something to do with the Rogers hosted server routing between the WAN and LAN interfaces but they're refusing otherwise and pointing this issue to our Cisco RV320. I've reviewed the logs on the RV320 as well as checked the firewall rules.....but the only thing that has changed is the remote WAN IP on Tunnel 2 to connect to the Rogers hosted server.
Any info on this scenario will greatly help me narrow down the issue.
Thank you and Merry Christmas!