RV042 configuration with QuickVPN in Windows 7

threecreeks · ‎10-02-2012

Hi,

I've been working on getting a client to Gateway configuration going for quite some time now. Had it working with a different Cisco single wan router that failed. The user replaced the router with an RV042 and we are trying to get the QuickVPN to once again connect to the router as it did before the replacement. Previously we did connect successfully with Windows 7 clients.

Router: RV042 v3 firmware 4.0.4.02-tm

Quickvpn version 1.4.2.1

what i keep getting in the log is the following :

2012/10/02 12:55:07 [STATUS]OS Version: Windows Vista

2012/10/02 12:55:07 [STATUS]Windows Firewall Domain Profile Settings: ON

2012/10/02 12:55:07 [STATUS]Windows Firewall Private Profile Settings: ON

2012/10/02 12:55:07 [STATUS]One network interface detected with IP address 192.168.10.20

2012/10/02 12:55:07 [STATUS]Connecting...

2012/10/02 12:55:07 [DEBUG]Input VPN Server Address = 72.14.99.251

2012/10/02 12:55:07 [STATUS]Connecting to remote gateway with IP address: 72.14.99.251

2012/10/02 12:55:08 [STATUS]Remote gateway was reached by https ...

2012/10/02 12:55:08 [WARNING]Remote gateway wasn't reached...

2012/10/02 12:55:08 [WARNING]Failed to connect.

2012/10/02 12:55:08 [STATUS]Remote gateway was reached by https ...

2012/10/02 12:55:08 [WARNING]Remote gateway wasn't reached...

2012/10/02 12:55:08 [WARNING]Failed to connect.

2012/10/02 12:55:08 [WARNING]Failed to connect!

2012/10/02 12:55:07 [STATUS]OS Version: Windows Vista

2012/10/02 12:55:07 [STATUS]Windows Firewall Domain Profile Settings: ON

2012/10/02 12:55:07 [STATUS]Windows Firewall Private Profile Settings: ON

2012/10/02 12:55:07 [STATUS]One network interface detected with IP address 192.168.10.20

2012/10/02 12:55:07 [STATUS]Connecting...

2012/10/02 12:55:07 [DEBUG]Input VPN Server Address = 72.14.99.251

2012/10/02 12:55:07 [STATUS]Connecting to remote gateway with IP address: 72.14.99.251

2012/10/02 12:55:08 [STATUS]Remote gateway was reached by https ...

2012/10/02 12:55:08 [WARNING]Remote gateway wasn't reached...

2012/10/02 12:55:08 [WARNING]Failed to connect.

2012/10/02 12:55:08 [STATUS]Remote gateway was reached by https ...

2012/10/02 12:55:08 [WARNING]Remote gateway wasn't reached...

2012/10/02 12:55:08 [WARNING]Failed to connect.

2012/10/02 12:55:08 [WARNING]Failed to connect!

the interior LAN subnet is 192.168.0.X while mine is 192.168.10.X so that should not be a conflict. I have allowed access to all ports on WAN1 in the router firewall at this point as well.

Not sure of the complete setup steps in the new router when it asks for IP, IP & FQDN, etc. Also not clear on what is happening when I get the lines stating the gateway was reached, then immediate that it was not reached. Split personality?

Any help would be greatly appreciated

Andrew

mpyhala · ‎10-02-2012

Hi,

I think that the issue is that you are trying to set up the router as "Client to Gateway". Set up your QuickVPN users under

"VPN Client Access". All you need is a Username and Password, check the box for "Active" and Add To List. Save the settings at the bottom of the page and you are done and should be able to connect as before.

- Marty

threecreeks · ‎10-03-2012

Thanks so much for your reply. I did indeed try that option as I a read about that in another group somewhere when researching the issue. Unfortunately, I get the exact same results and log messages.

-Andrew

mpyhala · ‎10-03-2012

Andrew,

Please call Small Business Support: www.cisco.com/go/sbsc

We can test from our lab and find out if the issue is with the router or the PC. Usually the error that you are seeing means that the IP, Username or Password are incorrect. In rare cases the ISP is blocking ports.

- Marty

threecreeks · ‎10-04-2012

Hello again,

Out of curiosity I deleted everything regarding the vpn on the router. Any tunnel, group vpn, or user. I then rebooted, added a new user and rebooted again. The QuickVPN started working after that. I did not setup the new user any different than the old, but the new one worked.

Thanks for your help!

Andrew

threecreeks · ‎10-11-2012

Well it worked a llittle. I got the client in as well as my own. The very next day we started getting message regarding being unable to reach the remote gateway. Upon looking at the log we saw, on both machines, that the final ping to verify failed. In the router we do allow ping to the router. Not very impressed with the router or the QuickVPN software and the clients is about to return the router and demand a refund. It should not be this difficult. Working, then when nothing has changed it just stops working. That's bull. Now trying to setup a tunnel without QuickVPN but I do not understand the remote client setup settings on the 'client to gateway' setup. When it says email or domain name what are they referring to?