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

WRV54G QuickVPN connects, but can't ping internal network

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by st_b, Sep 15, 2005.

  1. st_b

    st_b Network Guru Member

    Hey, all, first post here.

    I've got a WRV54G I've set up on a T1 connection using a static IP. I set up the quickVPN using the sticky'd guide on this page. From my remote (home) connection, I can connect to the VPN no problem. It shows me as being connected, it never loses connection. So far, so good. BUT:

    1. I can't ping any of the machines that are on the local network behind the WRV from the connecting remote machine. I CAN ping the external IP of the WRV, and the internal IP, and get responses, but can't ping any of the other machines on the internal network.

    2. Using the diagnostics tools in the admin section, I CAN ping the internal addresses.

    I'm really close here, anyone have any ideas what I'm doing wrong?

    Here's some of my connections:

    remote machine Cable Modem WRV54G
    (IP: 192.168.1.xx) -> (IP:12.222.xx.xx) -> (ext. IP) -> (int. IP 192.168.77.xx)

    Any help is greatly appreciated!

  2. TazUk

    TazUk Network Guru Member

    What firmware version are you running?
  3. st_b

    st_b Network Guru Member

    I'm running FW 2.38.

    I saw another similar post from someone else where they had to set the gateway of a device they wanted to access to be the IP of the WRV, but surely I don't have to set the computers inside the network to use the WRV's IP as a gateway? I use a proxy server to provide internet access internally, I only want to use the WRV for VPN access.
  4. russwmc

    russwmc Network Guru Member

    If the WRV54G is not your primary gateway for the internal PCs then each PC will need to have a route back to the WRV54G in order to talk back to the PC on the other end of the tunnel. If the PCs use another default gateway then they would not know the route back to the VPNed PC but would just default their response through the default gateway and out to the Internet.

    It sounded like you had a different machine acting as the Internet gateway on your second post, and therefore that gateway would provide the default route for the internal PCs.

    If what you are saying is that the proxy server is only for web browsing and your WRV54G is your default Internet gateway then this should not be the problem.

    Sorry I wrote so much but I don't want to make assumptions about your network configuration. It sounded like there was more to it than just the WRV54G router and PCs.

  5. DocLarge

    DocLarge Super Moderator Staff Member Member

    It could be an issue of putting the remote connecting computer into the "trusted" zone of the computer it's trying to connect to and vice-versa. Additionall, I've seen posts on these type of problems where the gateway router on the remote side needed to have an entry referencing the route between it and the second router that was hosting the vpn session (in this case, your WRV). Incidentally, both routers were running different subnets and the second router had an ip issued to it via the first router; also, there was a CAT5 cable running from one of the LAN ports of the first router to the WAN port of the second router (in this case the WRV54G).

    It's sounding like you may need to enter a static route "even though" the WRV54G has already added the route to its routing table via dynamic discovery.


Share This Page