RV042 / Greenbow client

Discussion in 'Cisco Small Business Routers and VPN Solutions' started by JimTan, Mar 28, 2005.

  1. JimTan

    JimTan Network Guru Member

    Has anyone managed to get the RV042 ( FW 1.3.6) to work with the Greenbow client ( ver 2.51.008)?

    Seems I can get phase 1 to complete, but not phase 2.

    The log on the RV042 says that the phase 2 SA can't find the address(whatever address I put in the phase 2 remote host address).

    Haven't bee able to connect with the Microsoft VPN either - just hangs.

    I'm not real thrilled with Quick VPN because it wants to change the address of my router - I really don't want to re-engineer a network.

    I'm new to VPN, but been putting together networks, remote accress, etc etc etc for many years now. It seems to me this is way too painfull to put together.
  2. DocLarge

    DocLarge Super Moderator Staff Member Member

    I'll give you a hand since I seem to be on a roll lately.

    If you start your LAN configurationg from default ( the router is hard coded to change it to something else automatically (i.e. 10.x.x.x). However, when you turn your router on for the first time (or during a reload) just change it to some other address (such as "then" from there set it to what you want and the router won't change your ip address setting.

    For your remote secure group and your remote secure gateway, start out with any any to establish a baseline. Once you can connect consistently, then start specifying the address.

    The key to greenbow (at least for me) was understanding how their terminology varied from linksys terms (in some respect). Use version 2.05 of the greenbow client by the way...

    Phase I:
    In the interface box, leave it as an asterik. The remote gateway (just in case you didn't know, bear with me :) ) should be the WAN address (ISP provided ip address) of the router your trying to connect to obviously. For the pre-shared key, use a hexadecimal string beginning with 0x (i.e. 0x123456789).

    Phase II:
    Vpn client address should be "your" WAN ip address (provided to you by your ISP). Use "subnet address" for LAN type and put in your local lan settings.

    Everything else as you know should match your router settings. Oh, don't sweat the parameters to much, they are just timeout settings.

  3. JimTan

    JimTan Network Guru Member

    Thanks for the help on this....I've finally given up on the VPN thing and moved on to Remotely Anywhere. Much easier to set up, secure enough and no brain-dead tech support. Its just way too painful....
  4. VolTrdr

    VolTrdr Network Guru Member

    I'm having the same problem with the GreenBow client 2.51.008 and the RV042 1.3.1. I can get the Phase 1 authentication to work but the session craps out on Phase 2. The client sends out the HASH but the router never replies.

    Windows Firewall is disabled.

    Anyone have success with this configuration?
  5. VolTrdr

    VolTrdr Network Guru Member

    I just got it working. I reread Doc's post. I had the wrong Client VPN address.

    I using a Verizon EVDO connection, and didn't update the VPN Client Address with the IP address provided by Verizon.

    Once the session came up I was able to open a Remote Desktop Connection into all the Windows 2003 servers on my network.

    The wording in the GreenBow client documentation threw me off track

    "VPN Client address Virtual IP address used by the client inside the remote LAN: The computer will appear in the LAN with this IP address. It is important this IP address not to belong to theremote LAN (e.g., in the example, you should avoid an IP address like"

    Thanks for the post Doc.
  6. DocLarge

    DocLarge Super Moderator Staff Member Member

    No problem, my man. I'm just out here trying to "do this damn thing" like everyone else...

  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