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

RVS4000 Setup Help

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by Jasonv, Apr 6, 2007.

  1. Jasonv

    Jasonv Guest

    Have the required Info Input, but still does not Show VPN as "UP".

    I hit Connect on the VPN setup Page, and still stays down, and on the new firmware, the test tunnel button, I get nada. Im sitting @ the station with the RVS4000, and wife is @ home trying to connect with QuickVPN.

    What Info you guys needing/wanting to mebbe help me get this figured out?

    Local Security Gateway Type: IP Only

    Domain Name:

    IP address: xx.xxx.xxx.xx

    Local Security Group Type: IP Addr. Subnet

    IP Address:

    Subnet Mask:

    Remote Security Gateway Type: IP Only

    IP address xx.xxx.xxx.xx

    Remote Security Group Type: Any

    This Gateway accepts requests from any IP address.
  2. Toxic

    Toxic Administrator Staff Member

    and what are the key management settings? are they exactly the same on each end?
  3. djcoolmax

    djcoolmax Network Guru Member

    Don't know if we are supposed to enable the VPN tunnel. THink that function is more suited for establishing VPN tunnels between to RVS4000 routers. If using with QuickVPN solution, think all that is required is the setup of the username and password in the VPN user management section.

    The problem I am facing is, once I connect using QVPN, it says I am connected but I can't seem to access the local resource in that network. I do a IPconfig and I still see the same IP address that was assigned to me before connecting via VPN. If I am not mistaken, I should be assigned a "local" IP address of router DHCP is issuing.

    To make matters worse, I even bricked my RVS4000 and had to RMA it for another one. Now I am too scared to upgrade the darn firmware!

    Someone pls advise on the steps and infrastructure to get QVPN to work properly.

  4. DocLarge

    DocLarge Super Moderator Staff Member Member

    Here's what I can add...

    I'm currently connecting to my network from school (I'm in Germany at the moment) via my SMCBR18VPN firewall router (old faithful) as the gateway and I'm using my wrvs4400n as an access point. I've opened port 1723 on the SMC router to point to my 2k3 vpn server; I can connect with the windows pptp client without any problems (works great). However....

    I noticed when I loaded the greenbow (IPSEC) vpn client (didn't try it right away) and then later on just happen to try to access my resources over vpn again via pptp, I couldn't! I could connect to my vpn server on the inside, but I couldn't "ping" anything on the inside!

    I pulled my hair out for about 20mins trying to figure things out until it finally dawned on me to put my laptop back to the configuration it was in prior to losing connectivity to my inside devices during a vpn session.

    As soon as I unloaded greenbow vpn, I was back in business :)

    Long story short, quickvpn may very well still have errors when IPSEC executes (or tries to). Everyone can make the initial connection, but can't ping anything on the inside. I'm far from being an IPSEC guru, but there's a relationship in the two issues somehow (in my opinion...)

  5. Toxic

    Toxic Administrator Staff Member

    Try checking the security policies mate you may find that each clients own policies conflict with each other. I know Linksys say not to have another VPN Client installed onto the same PC because of this.

Share This Page