Cannot Ping Computers only Router with QuickVPN Tunnel

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by RogMJ007, Oct 24, 2005.

  1. RogMJ007

    RogMJ007 Guest

    I connect to my remote network via the QuickVPN software on my laptop and the WRV54G router at the remote end. However, I can only ping the internal IP address of the router. I cannot ping any of the computers at the remote site. Does anyone have any suggestions?
  2. DocLarge

    DocLarge Super Moderator Staff Member Member

    Check to see if your laptop is added to the list of "included" computers on the distant end firewall. Also see if you have a computer/domain account for access to that local LAN, to include share/security permissions.

  3. JdW77

    JdW77 Network Guru Member

    This should not be a problem. Ping doesn't need any account permissions.
  4. DocLarge

    DocLarge Super Moderator Staff Member Member

    The second part was suggested if the first part (firewalls) was a factor, thus gaining you access. My bad for not explaining further...

  5. mons-meg

    mons-meg Network Guru Member

    Same issue here. What seems to be happening is no virtual adapter entry is created on the client machine, nor is a route generated on the client machine for the remote network.

    For example, when I use Cisco's VPN client to connect to my work network, I get a virtual IP address assigned to my client that exists on the other side of the tunnel, plus appropriate route table entries.

    I realize that QuickVPN probably "doesn't do it that way" but I am curious how I am supposed to access the remote network...are there other settings lacking on the remote WRV54G?
  6. mons-meg

    mons-meg Network Guru Member

    OK, I searched on the forums here and found a reference to routing issues, which led me to the following. The WRV54G in our case is not the primary Internet gateway for the hosts on the office network we are tunneling to. The WRV54G was purchased to provide the road warriors with a simple interface to get to the office network using QuickVPN. ;)

    Now, if we put a route on a server on the office network that points back to the Linksys for hosts in the network at my house, then it works. Basically: = office private LAN = local LAN at my house = default gateway of hosts = internal IP of the WRV54G

    Adding this route on an internal office server give me access to that server only from my house network: -->

    What I really wish were the case? Linksys did private link coimpatible VPN , or maybe gave me a pool of IPs to use on the internal LAN and used proxy arp, etc to talk to the internal hosts. i.e. I wish it was more like Cisco VPN client/server with a virtual interface. *grumble*. The main problem now is what happens when an employee is on the road somewhere and the hotel uses private addressing? Am I forced to change the routing tables on *all* internal office hosts to reflect new routes back to the Linksys for *all* possible private network spaces? ugh.

    Or, am I missing something obvious in the config on the Linksys?
  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