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

wrv54g quickvpn one user cannot connect

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

  1. ZuoNET

    ZuoNET Network Guru Member

    hi! i've run into this very strange problem. for a customer i have successfully set up 5 users which should be able to connect with the quickvpn client. this is working perfectly for 4 out of 5 users, only the fifth user (actually the second entry in the vpn client list table) always gets an error in the final phase...

    anybody run into this problem?

    it is clearly not related to wrong password because then the user would get disconnected immediately. neither is it related to his own laptop because i was just testing from my own laptop and could successfully connect with the 4 other users' credentials.

    thanks for any suggestions.
  2. DocLarge

    DocLarge Super Moderator Staff Member Member

    The issue is on the the client end. Have your client check the "Reasons Quickvpn Won't Connect" sticky in this forum. If he's getting "verifying network" it comes down to something on the client side. Ocassionally, you may have an issue where the wrv doesn't accept the username and password "although" it goes through the whole authentication process; in this case, change the username to something else (a slight variation of the original) and also the password (make sure there are no special characters or symbols because quickvpn doesn't like it).

  3. jar0000

    jar0000 Network Guru Member

    I am having the same issue all but one account works I can logon with a good account on my pc then I try the 5th account and I get kicked at the last step the vnp setup has been working for months now all of a sudden this

    I am running firmware 2.38
  4. DocLarge

    DocLarge Super Moderator Staff Member Member

    Occasionally that happens with the WRV54G (small issue but not major). Just recreate the user account with a slight modification (jsmith instead of smith) and it should be fine. The only thing I've personally seen to get around the error is a reset (again, occassionally). It's easier to just create a new account with a slight modification.


Share This Page