RVS4000 QuickVPN issues

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by chiplowry, Aug 17, 2006.

  1. chiplowry

    chiplowry LI Guru Member

    I've just purchased an RVS4000 to replace an old Sonicwall device I had. I've had absolutely no luck getting the quickvpn to work. I've tried different machines (both xp sp2 laptops though), firewall on & off, attempting to connect from different networks (one behind another linksys router, one behind a hawking technology router)

    Each time I hang on 'verifying network' although when I look at the router, it shows me as connected.

    Anything else I might try? I'm using latest firmware from linksys site and 1.0.40 QuickVPN.
  2. Toxic

    Toxic Administrator Staff Member

  3. OpticalMan

    OpticalMan LI Guru Member

    Just some suggestions if you are reaching for something to try.

    Check and make sure the IPSEC service is running. Also, I'm not positive, but I think the windows login you are using needs administrative rights to let QuickVPN configure the security policy.

    Another common issue people have with QuickVPN and this symptom is having multiple network interfaces on the same machine. Try disabling any extra network interfaces in network settings. I know on my laptop, I have 3 interfaces and I have to disable one of them for it to get past the "verifying network" status.
  4. chiplowry

    chiplowry LI Guru Member

    I checked the ipsec service and it actaully *wasn't* running. After starting it, I was able to connect for about 1 min. Wasn't able to ping anything on the far network but was able to bring up the login box for the router. After I entered the admin password, the connection dropped and haven't been able to get it working again. I'll keep plugging along and see if I can come up with anything.
  5. OpticalMan

    OpticalMan LI Guru Member

    I don't know what it could be now. Perhaps the MTU needs to be lowered.

    One other thing I forgot to add before, is make sure your QuickVPN username and password contain only pure alpha-numeric characters. No spaces, hyphens, etc.

    Make sure the IP address subnets are different at both ends.
  6. chiplowry

    chiplowry LI Guru Member

    Maybe I have made a total newbie mistake here. But changing from using the FQDN to the actual IP address seems to have fixed the issue on both laptops. I still cannot ping anything on the far network but can access resources on the far network.

    Other network vpn clients I have used in the past can use the fqdn. Maybe Linksys devices are different?
  7. TazUk

    TazUk Network Guru Member

    Shouldn't make a difference as all it does is resolve the FQDN to an IP address :unsure:
  8. Toxic

    Toxic Administrator Staff Member

    FQDN will only work is DNS is working.
  9. TazUk

    TazUk Network Guru Member

    True but I would assume the original poster could access web pages fine so DNS must be functioning correctly :unsure:
  10. DocLarge

    DocLarge Super Moderator Staff Member Member

  11. Dhondi

    Dhondi LI Guru Member

    Chip, I'm having the same problems...

    Hey Chiplowry,

    I'm experiencing the same problem. It may not be much help, but it's helpful to know what other users are experiencing. I can connect to the RVS4000 router, i can use RDP (Remote Desktop) to connect to PC's on the remote network, but I can't ping by IP or NetBIOS name, and i can't connect to any network shares. I'm still looking for an answer as well.
  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