1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

2 vpn routers rv042 set up, connected and nothing...

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by jrhessey, Mar 24, 2006.

  1. jrhessey

    jrhessey Network Guru Member

    I have 2 rv042 routers set up and had them connected in gateway to gateway. However I couldn't get to anything on the other network. I've got most of the settings here...

    Site 1

    dhcp - 192.168.0.1
    addy's - 192.168.0.2-50
    tunnel - test
    IP Only on both
    local ip - wan ip addy
    remote ip range - 192.168.0.110-150

    Site 2

    dhcp - 192.168.0.1
    addy's - 192.168.0.100-150
    tunnel - test
    IP Only on both
    local ip - wan ip addy
    remote ip range - 192.168.0.1-109


    I have been able to get it to connect using agreesive mode in the advanced part of the tunnel set up. However when it connects it kill our ip phone and our internet connection at site 1. Can someone give me the correct steps for 2 rv042 routers? I've looked at the greenbow guide, but I don't think that will work since I'm not using the wrv54g. Also would you guys suggest gateway to gateway or gateway to client. Thanks for any help!
     
  2. d__l

    d__l Network Guru Member

    Sheesh, I wouldn't have believed those settings would even connect!

    The routers' local subnets HAVE to be different. So one subnet might be 192.168.1.xxx and the other 192.168.2.xxx. The 192.168.0.xxx subnet has been problematic with other Linksys VPN products so I avoided that one.

    Maybe you should review what the Linksys knowledgebase says about VPN connections? They explain the settings pretty well.
     
  3. mkiv

    mkiv Network Guru Member

    I have similar problem.

    1. RV042 - 192.168.1.1 - local
    2. RV016 - 192.168.2.1 - remote

    Tunnel is "connected", I am able to ping 192.168.2.1 from 192.168.1.x subnet, but nothing else - looks like remote router doesn't route anything from vpn connection.

    Help, please!
     
  4. d__l

    d__l Network Guru Member

    A common cause of this problem is when the remote end IP subnet is not "trusted" by a software firewall such as Zone Alarm on the computers on the local end. It looks as though the remote end is not routing any packets, but in reality they are all being blocked by the software firewall as they get to the local computers.
     

Share This Page