RV042 to RV042 VPN connects, but no thru communications

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by pabblo, Mar 21, 2007.

  1. pabblo

    pabblo LI Guru Member

    I'm trying to get my home RV042 to connect to the office RV042.
    I've setup G2G vpn tunnels, and they connect, but I cannot ping the office side from home, or the other direction.

    I'm cable internet at home, the office is static with 1 ip.
    I am using a different LAN ip scheme than at the office.
    The office RV042 LAN ip is I cannot ping that from home.

    I checked the NAT traversal option in the VPN setup.

    Any suggestions?
  2. starlight

    starlight Network Guru Member

    with no ip setup information its hard to answer you problems

    Do you have two subnets ? like and

    If yes, what is your touting setup ?

    Do you have enabled rip on both sides ?

  3. pabblo

    pabblo LI Guru Member

    Sorry I didn't provide more info.

    At home, I'm using the standard linksys nat
    Router is

    At the office, they are using nat
    Router is

    I did not enable rip on either router.
    I did update to the latest firmware on both routers.

    Basically I just followed the "How To" for Gateway 2 Gateway on the router located on the linksys website
  4. pabblo

    pabblo LI Guru Member

    I just enabled ripv2 on both routers. Now I can see the routing tables, and they have the remote subnets in there. Looks ok. The routers are set to Gateway, not Router.
  5. Toxic

    Toxic Administrator Staff Member

    do any of the workstation have there own firewalls running? do they allow ICMP ping requests?
  6. ifican

    ifican Network Guru Member

    I am uncertain why its not working as if the tunnels show up then it should be good and unless as toxic mentioned you have firewalls blocking the icmp requests then it should work. Some gateways dont like to respond to icmp direct at it from the tunnel so try going to a host inside. The best thing you can do for yourself at this point is get a packet sniffer (wireshark is my favorite) and see what info is returning and where it is comming from. Also there is not need to run a routing protocol as doing this turns the device into a router and not a gateway and could potentially gum up your connection. Something else to be aware of, 192.0.x.x is public domain. Granted you can run whatever ip you want inside your network but it can cause issues down the road if you are not careful. 192.168.x.x was specifically designed for nat and should be used for that purpose as it is filtered at the isp level and there is never any worry of contaminating routing tables. One last thing, Nat-T is not needed if you are going G-2-G, i dont think that is causing the issue but who knows for sure.
  7. pabblo

    pabblo LI Guru Member

    Well, I did a chat session with linksys and let him remote into the routers and he got it working. Not sure what he did cuz I lost my chat session when I had to power down the router. Anywho, I can ping across the vpn and use ip unc share access. But boy, is the throughput slow. At home I have a standard 6Mb/256K cable, at the office it is 1Mb adsl, soon to be AT&T T1. I don't think I can send this router to the soon to be remote office with this vpn troughput. What do you guys do a std practices for best vpn troughput? I will read some more articles. Is a T1 or SDSL required on both ends to make this usable?

    I remembered the main thing the Linksys tech changed was the access method for my home side. I had Dynamic + FQDN, but he changed it to IP only with the current dhcp public ip I have. Obviously that is not an idea setting.
  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice