RV220W IPSec Tunnel not working

[aaron.connell]

We have 2 RV220W Routers installed in seperate offices. We are attempting to setup a IPSec tunnel between the two sites. So far we have been unsuccessful in getting this to work.

On both sides, we are getting a successful connection established, but netiher site is recieving any packets. Both sides are transmitting packets though. We have exhausted our resources trying to figure out why.

Site A:

Active IPsec Security Association Table

Policy Name	Endpoint	Packets		KBytes		State	Action
		Rx	Tx	Rx	Tx
SiteA-SiteB-Tunnel	209.xxx.xxx.xxx	0	4643	0.00	607.70	IPsec SA Established

Site B:

Active IPsec Security Association Table

Policy Name	Endpoint	Packets		KBytes		State	Action
		Rx	Tx	Rx	Tx
SiteB-2-SiteA	71..xxx.xxx.xxx	0	107	0.00	15.55	IPsec SA Is Established

Has anyone else run into a similar issue and were they able to solve this? Any thoughts on what might be the problem?

[Tom Watts]

Hi Aaron, a lot of times something like this is because the local group / remote group ip or subnet masks are not configured correctly.

Realistically, if you leave the advance configuration for the IKE and VPN policy completely default, where you only make the policy names, the same password between sides and input the correct local/remote groups and WAN ip addresses, the tunnel will come up and work great provided you don't have connectivity issues.

Here is an example-

-Tom
Please rate helpful posts

[aaron.connell]

Thomas,

Thanks for your reply. I have tried both Advanced setup as well as just using the basic setup. I just deleted all the previous configs and re-added them using just the basic setup and only entering the minimum requirements. I am still getting the same results.

Here is my local/remote traffic config:

Local Traffic Selection
Local IP:	Any                             Single                             Range                             Subnet
Start Address:
End Address:
Subnet Mask:
Remote Traffic Selection
Remote IP:	Any                                 Single                                    Range                                 Subnet	This field is not editable, because netbios is selected.
Start Address:
End Address:
Subnet Mask:

[aaron.connell]

oops - the fields are filled in - I promise :-)

Anyway -  Looks like my counterpart on the otherside just isolated an issue with the firewall on their end - hopefully that is the problem.

[aaron.connell]

Firewall misconfiguration on the remote site was the problem. Issue now resolved.