Quick VPN client can not connect to RV042

[arifwa2009]

PID VID :           RV042 V03

LAN IPv4/ Subnet mask : 192.168.0.7/255.255.255.0

Working Mode :           Router

2012/04/09 11:55:40 [STATUS]OS Version: Windows 7

2012/04/09 11:55:40 [STATUS]Windows Firewall Domain Profile Settings: ON

2012/04/09 11:55:40 [STATUS]Windows Firewall Private Profile Settings: ON

2012/04/09 11:55:40 [STATUS]Windows Firewall Private Profile Settings: ON

2012/04/09 11:55:40 [STATUS]One network interface detected with IP address 192.168.1.141

2012/04/09 11:55:40 [STATUS]Connecting...

2012/04/09 11:55:40 [DEBUG]Input VPN Server Address = 1.2.3.4

2012/04/09 11:55:40 [STATUS]Connecting to remote gateway with IP address: 1.2.3.4

2012/04/09 11:55:42 [STATUS]Remote gateway was reached by https ...

2012/04/09 11:55:42 [STATUS]Provisioning...

2012/04/09 11:55:54 [STATUS]Success to connect.

2012/04/09 11:55:54 [STATUS]Tunnel is configured. Ping test is about to start.

2012/04/09 11:55:54 [STATUS]Verifying Network...

2012/04/09 11:56:00 [WARNING]Failed to ping remote VPN Router!

2012/04/09 11:56:03 [WARNING]Failed to ping remote VPN Router!

2012/04/09 11:56:06 [WARNING]Failed to ping remote VPN Router!

2012/04/09 11:56:09 [WARNING]Failed to ping remote VPN Router!

2012/04/09 11:56:12 [WARNING]Failed to ping remote VPN Router!

2012/04/09 11:56:16 [WARNING]Ping was blocked, which can be caused by an unexpec

ted disconnect.

2012/04/09 11:56:21 [STATUS]Disconnecting...

2012/04/09 11:56:26 [WARNING]Failed to disconnect.

PPTP working fine but not with Quick VPN .. test on some computer and internet access still can not get connect to router.

[rmanthey]

Wendell,

The three VPN softwares that are working because they install a virtual network addapter on the computer. When this is done it adds rules to the Microsoft Operating system firewall and any third party antivirus/firewalls. The QuickVPN utility leverages Microsofts own built in IPSEC client, it dosnt' add a separate addapter or modify any Microsoft or third party antivirus rules when it is installed. QuickVPN utility just provides a user friendly interface with the Microsoft IPSEC client to establish the tunnel.

Cisco Small Business Support Center

Randy Manthey

CCNA, CCNA - Security

[javier-sanchez]

All very acceptable explanations.  I am still struggling with your indications, but one other question, by the way:

What about the issue with the backup of the configuration?  When I click on the button to proceed, it immediately shows me a Page not found 400 or 404 http error.

The same is true when I try to upgrade the firmware.

This for now, I'll get back with positive or sad results shortly.

Regards.

Javier.

[javier-sanchez]

Hi there again,

Sad results.  I changed the remote access port to 50443, and I could log in to the web admin page.

HTTPS is enabled.

I started QVPN, and just at the point where the "The remote gateway is not responding.  Do you want to wait?" message appears, without replying to it, I can see me connected in the VPN web admin page.  I displayed the log and the last 12 message lines I can see are:

Jun 7 20:42:52 2012	VPN Log	(qknipsÿÿ©yð) #8: responding to Quick Mode
Jun 7 20:42:52 2012	VPN Log	(qknipsÿÿ©yð) #8: [Tunnel Negotiation Info] Inbound SPI value = 2169d8cb
Jun 7 20:42:52 2012	VPN Log	(qknipsÿÿ©yð) #8: [Tunnel Negotiation Info] Inbound SPI value = 2169d8cb
Jun 7 20:42:52 2012	VPN Log	(qknipsÿÿ©yð) #8: [Tunnel Negotiation Info] Outbound SPI value = c38929e4
Jun 7 20:42:52 2012	VPN Log	(qknipsÿÿ©yð) #8: [Tunnel Negotiation Info] Outbound SPI value = c38929e4
Jun 7 20:42:52 2012	VPN Log	(qknipsÿÿ©yð) #8: [Tunnel Negotiation Info] >>> Responder send  Quick Mode 2nd packet
Jun 7 20:42:52 2012	VPN Log	(qknipsÿÿ©yð) #8: [Tunnel Negotiation Info] >>> Responder send  Quick Mode 2nd packet
Jun 7 20:42:52 2012	VPN Log	(qknipsÿÿ©yð) #8: [Tunnel Negotiation Info] <<< Responder Received  Quick Mode 3rd packet
Jun 7 20:42:52 2012	VPN Log	(qknipsÿÿ©yð) #8: [Tunnel Negotiation Info] <<< Responder Received  Quick Mode 3rd packet
Jun 7 20:42:52 2012	VPN Log	(qknipsÿÿ©yð) #8: [Tunnel Negotiation Info] Quick Mode Phase 2 SA  Established, IPSec Tunnel Connected
Jun 7 20:42:52 2012	VPN Log	(qknipsÿÿ©yð) #8: [Tunnel Negotiation Info] Quick Mode Phase 2 SA  Established, IPSec Tunnel Connected
Jun 7 20:42:52 2012	VPN Log	(qknipsÿÿ©yð) #8: IPsec SA established {ESP=>0xc38929e4 <0x2169d8cb

So, it does connect, but the problem obviously is the "Verifying network" step, when QVPN is pinging the RV082 it does not receive the replies, and thus it thinks it is not connected.  This has to be something with the configuration of the firewall within Windows.  Then, what is it?

And when I reply NO to the message window, then I would disconnect me truly, and then I can see me disconnected.

Would you like to give it a try?  My public IP for the RV082 is 190.212.233.85, port 50443.  Browse on that address and you'll see it.  Well...as long as I keep it on.  As it doesn't work well, then I turn it off most of the day.

javier.

[javier-sanchez]

Arif, Wendell, I just found this interesting so-called solution, I am going to give it a try.

http://www.google.com.ni/url?sa=t&rct=j&q=quickvpn%20the%20remote%20gateway%20is%20not%20responding&source=web&cd=2&ved=0CGsQFjAB&url=http%3A%2F%2Fhomecommunity.cisco.com%2Ft5%2FWired-Routers%2FRV082-QuickVPN-trouble-remote-gateway-is-not-responding%...

Maybe this is what has to be done, this fellow says to factory-reset the router and then re-configure everything by hand, with no backup/restore in the middle until all is done.

I'll try this and will come back with comments.

Regards.

[johanvermeij]

Get a RV042 hardware version 3 and your problems will vanish

[arifwa2009]

In my 1st post.

PID VID :           RV042 V03

LAN IPv4/ Subnet mask : 192.168.0.7/255.255.255.0

Working Mode :           Router

[Te-Kai Liu]

It was found the printer/file sharing property on a Win7 computer may affect QuickVPN client from connecting to a QuickVPN server. Stop the sharing and see if it helps.

Windows firewall on Win7 has to be enabled for QuickVPN to work.

[javier-sanchez]

At my very first attempts to have QuickVPN connected to my RV082, I learned from the known issues, that you had to run it as administrator.  That's what I've been doing ever since.  And it doesn't work.

I was also trying to upgrade the firmware, and as I browse the binary file with the flash image, and clicking ont "Upgrade", it sadly shows me a Page not found error.  And this other secondary effect has not had a comment from the gurus either.

It's several things that are happening to me with this product.  I don't know whether I will be lucky or not with the reseller when I try to return it.

It's just frustrating Cisco has these problems.  I am very dissapointed with them.

[paulantonacci]

Hi,

I  have not read all the way through the post to your question, but one thing that solved my issues with Quickvpn was running the application as administrator. 

Prior to running the application as administrator, the application would run, but stop with the verifying network message and the annoying messages about do you want to keep trying to connect.  The log messages indicated the ipsec service was not started. 

Please keep in mind my vpn connection was to a RVS4000 from a system running Windows XP (SP3).  I was connecting over DSL lines with DHCP on either end.  At the business there is a RVS4000 and at home a Belkin Wireless Router.

Paul

[wendellprincipe]

Good news!

Finally i made it worked!

Windows XP SP2

Windows XP SP3

Windows 7         

Disabled firewall.

On my DSL (office network) router, i allowed some ports.

Application	Trigger			Open			Schedule Rule
	Name	Protocol	Port Range		Protocol	Port Range
			Start	End		Start	End
	443	TCP/UDP	443	443	TCP/UDP	443	443	Always
	60443	TCP/UDP	60443	60443	TCP/UDP	60443	60443	Always
	500	TCP/UDP	500	500	TCP/UDP	500	500	Always
	4500	TCP/UDP	4500	4500	TCP/UDP	4500	4500	Always

On the RV042,

General

Firewall : EnableDisable SPI (Stateful Packet Inspection) : EnableDisable DoS (Denial of Service) : EnableDisable Block WAN Request : EnableDisable Remote Management : EnableDisable Port : HTTPS : EnableDisable Multicast Passthrough : EnableDisable

After 2 weeks of brutal pain of troubleshooting, finally put smile on my face..

[nathanbeach]

I am also getting "remote gateway is not responding" on the RV042 with the latest QuickVPN client I was able to find on Cisco's website.  The most frustrating part is that it worked fine the first time I tried it a week ago.  I tried again last night (from the same remote PC) and now cannot connect.

I can log in to the remote web management interface and see the negotiation going on in the VPN Log.  I've even opened up full access on the router to my remote IP address.  I guess I'm not going to be able to offer my users the ability to VPN in, if it's this unreliable.  Awesome.

I've tried downloading a couple of other VPN clients and can't get any of them to work with the RV042.  If anyone has any suggestions for other clients and how to configure them with the RV042, it would be much appreciated.

[nathanbeach]

I finally got this to work by doing something I found in another related thread, that I can no longer find.  Go into your local Windows Firewall settings and add an Inbound Rule for the quickvpn.exe, and just allow everything.  After I did that, I was able to connect with QuickVPN.  We'll see how long this good turn of events lasts.

[nathanbeach]

Well, I guess this was too good to last.  The f#$%ng thing stopped working again this week.  I'm getting "gateway is not responding" again, even though I have the inbound rules set on my local firewall and have been connecting fine for the last two weeks.  Amazing.

QuickVPN is awesome!

[linksysinfo]

When you get an error "failed to ping VPN router" it would appear the block wan requests is enabled on the routers firewall. Also you own firewall on the remote pc will most likely need to allow icmp requests.

Sent from Cisco Technical Support iPad App

[javier-sanchez]

Simon:

I swear I have tried everything mentioned on this thread.  Please, if you would just pay a little attention.

I am able to see the tunnel established on the Web Management from the RV082.  That step of pinging the router seems to me like useless.  Probably you should remove that apparently useless step of pinging the router from the QuickVPN software.  Just because of this, it gives up, and I say: Why, you're connected!!!

I even uninstalled my ESET antivirus, as I was very unconfident of it.  Most antivirus software try to be smarter than the Windows firewall, and offer you to put additional constraints to the network traffic.  I removed it with the hope of having finally a happy CONNECTED message.  Nothing!

I added the above Nathan's suggestion.  Nothing!  I disabled the Windows firewall. Nothing!

I disabled the "Block WAN request" parameter.  Nothing!  Please it is simply unacceptable that you people, THE provider cannot have an effective solution to this.  Tell me something, with all due respect, don't you feel shameful?

We're customers speaking here!  Your salary is possible because we buy from Cisco.  We are expecting to get a good service, and a good product.  And good answers to these matters.  Please!