cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
5611
Views
0
Helpful
3
Replies

Connecting Quick VPN to RV042

briandemski
Level 1
Level 1

Our main office uses an RV042 router and our plan was to allow remote staff access to our office network via Quick VPN.

We have about 5 people that work remotely, including myself, and we have all been having intermittant trouble connecting with Quick VPN. Sometimes the VPN connects fine, and other times we get the "Connection Error" screen that lists 5 possible causes (which I've confirmed are not the actual cause) or the "The remote gateway is not responding message'. Personally, I'd been having the best results with the VPN working fine for the past month and half without any problems, but then we had a power outtage at our office. The next day, I would get the error with the 5 possible causes - I had someone reboot the router and I was able to connect, but now I'm having trouble this morning. We need some help or else we'll have to explore another router / VPN solution.

We purchased the RV042 specifically for this purpose - to be used at our main office so that remote staff can connect from their homes to view files on our fileserver / sql database.

This whole process has been very trying since it seems like neither Cisco or Linksys claim ownership and the support documentation for Quick VPN is non-existant.

I have many years of computer experience but I do not have experience setting up VPN so I'm at a loss of what to look at.

I sincerely appreciate any help.

If there are any logs or settings people need to see, please let me know.

3 Replies 3

briandemski
Level 1
Level 1

After doing some trial and error, I've found that if I turn off the firewall on the RV042, I can connect from my home (Windows 7) via QuickVPN without any error messages.

One of the other staff members working remotely from her home (Windows XP SP3) now gets past the "5 reasons" connection error due to the RV042's firewall being disabled, but then fails at the "Verifying Network" phase with the error: "The remote gateway is not responding".

So I guess part of my problem comes down to opening ports in the RV042's firewall.

I've seen a similar post where they mention opening up UDP ports 500 and 4500, as well as TCP ports 443 and 60443. Would that be correct?

Please advise.

Just to note, I am using the latest version of Quick VPN (1.4.1.2) and latest RV042 firmware (1.3.12.19-tm).

Log file for remote location #1 (Windows 7) - With RV042 firewall off, it can connect successfully - I still see the "Failed to ping remote VPN Router!" messages in the log file which seems odd:

2010/09/29 09:48:03 [STATUS]OS Version: Windows 7
2010/09/29 09:48:03 [STATUS]Windows Firewall Domain Profile Settings: ON
2010/09/29 09:48:03 [STATUS]Windows Firewall Private Profile Settings: ON
2010/09/29 09:48:03 [STATUS]Windows Firewall Private Profile Settings: ON
2010/09/29 09:48:03 [STATUS]One network interface detected with IP address 192.168.50.200
2010/09/29 09:48:03 [STATUS]Connecting...
2010/09/29 09:48:03 [DEBUG]Input VPN Server Address = 64.60.*.*

2010/09/29 09:48:03 [STATUS]Connecting to remote gateway with IP address: 64.60.*.*
2010/09/29 09:48:13 [WARNING]Failed to connect.
2010/09/29 09:48:27 [WARNING]Failed to connect.
2010/09/29 09:48:27 [WARNING]Failed to connect!
2010/09/29 09:48:53 [STATUS]OS Version: Windows 7
2010/09/29 09:48:53 [STATUS]Windows Firewall Domain Profile Settings: ON
2010/09/29 09:48:53 [STATUS]Windows Firewall Private Profile Settings: ON
2010/09/29 09:48:53 [STATUS]Windows Firewall Private Profile Settings: ON
2010/09/29 09:48:53 [STATUS]One network interface detected with IP address 192.168.50.200
2010/09/29 09:48:53 [STATUS]Connecting...
2010/09/29 09:48:53 [DEBUG]Input VPN Server Address = 64.60.*.*
2010/09/29 09:48:53 [STATUS]Connecting to remote gateway with IP address: 64.60.*.*
2010/09/29 09:48:58 [STATUS]Remote gateway was reached by https ...
2010/09/29 09:48:58 [STATUS]Provisioning...
2010/09/29 09:49:07 [STATUS]Success to connect.
2010/09/29 09:49:07 [STATUS]Tunnel is configured. Ping test is about to start.
2010/09/29 09:49:07 [STATUS]Verifying Network...
2010/09/29 09:49:13 [WARNING]Failed to ping remote VPN Router!
2010/09/29 09:57:10 [WARNING]Failed to ping remote VPN Router!
2010/09/29 09:57:13 [WARNING]Failed to ping remote VPN Router!
2010/09/29 10:03:20 [WARNING]Failed to ping remote VPN Router!
2010/09/29 10:05:34 [WARNING]Failed to ping remote VPN Router!

Log file for remote location #2 (Windows XP SP3) - with RV042 firewall off, it still gets error "The remote gateway is not responding":

2010/09/29 09:18:39 [STATUS]OS Version: Windows XP
2010/09/29 09:18:40 [STATUS]Windows Firewall is ON
2010/09/29 09:18:40 [STATUS]One network interface detected with IP address 192.168.1.65
2010/09/29 09:18:40 [STATUS]Connecting...
2010/09/29 09:18:40 [DEBUG]Input VPN Server Address = 64.60.*.*
2010/09/29 09:18:40 [STATUS]Connecting to remote gateway with IP address: 64.60.*.*

2010/09/29 09:18:46 [STATUS]Remote gateway was reached by https ...
2010/09/29 09:18:46 [STATUS]Provisioning...
2010/09/29 09:18:52 [STATUS]Success to connect.
2010/09/29 09:18:52 [STATUS]Tunnel is configured. Ping test is about to start.
2010/09/29 09:18:52 [STATUS]Verifying Network...
2010/09/29 09:18:56 [WARNING]Failed to ping remote VPN Router!
2010/09/29 09:18:59 [WARNING]Failed to ping remote VPN Router!
2010/09/29 09:19:03 [WARNING]Failed to ping remote VPN Router!
2010/09/29 09:19:06 [WARNING]Failed to ping remote VPN Router!
2010/09/29 09:19:10 [WARNING]Failed to ping remote VPN Router!
2010/09/29 09:19:13 [WARNING]Ping was blocked, which can be caused by an unexpected disconnect.
2010/09/29 09:23:12 [STATUS]Disconnecting...
2010/09/29 09:23:19 [STATUS]Success to disconnect.
2010/09/29 09:23:32 [STATUS]OS Version: Windows XP
2010/09/29 09:23:32 [STATUS]Windows Firewall is ON
2010/09/29 09:23:32 [STATUS]One network interface detected with IP address 192.168.1.65
2010/09/29 09:23:32 [STATUS]Connecting...
2010/09/29 09:23:32 [DEBUG]Input VPN Server Address = 64.60.*.*
2010/09/29 09:23:32 [STATUS]Connecting to remote gateway with IP address: 64.60.*.*

2010/09/29 09:23:37 [STATUS]Remote gateway was reached by https ...
2010/09/29 09:23:37 [STATUS]Provisioning...
2010/09/29 09:23:43 [STATUS]Success to connect.
2010/09/29 09:23:43 [STATUS]Tunnel is configured. Ping test is about to start.
2010/09/29 09:23:43 [STATUS]Verifying Network...
2010/09/29 09:23:47 [WARNING]Failed to ping remote VPN Router!
2010/09/29 09:23:48 [WARNING]Failed to ping remote VPN Router!
2010/09/29 09:23:51 [WARNING]Failed to ping remote VPN Router!
2010/09/29 09:23:55 [WARNING]Failed to ping remote VPN Router!
2010/09/29 09:23:58 [WARNING]Failed to ping remote VPN Router!
2010/09/29 09:24:02 [WARNING]Ping was blocked, which can be caused by an unexpected disconnect.
2010/09/29 09:24:14 [WARNING]Failed to ping remote VPN Router!
2010/09/29 09:24:17 [WARNING]Failed to ping remote VPN Router!
2010/09/29 09:24:21 [WARNING]Failed to ping remote VPN Router!
2010/09/29 09:24:24 [WARNING]Failed to ping remote VPN Router!
2010/09/29 09:24:28 [WARNING]Failed to ping remote VPN Router!
2010/09/29 09:24:31 [WARNING]Ping was blocked, which can be caused by an unexpected disconnect.
2010/09/29 09:24:43 [STATUS]Disconnecting...
2010/09/29 09:24:50 [STATUS]Success to disconnect.

You are correct about the ports needing to be open. The following ports need to be open for QVPN:

443,500,4500,60443.  A lot of times the ISP will have these ports closed. I would check with your ISP

to make sure these ports are opened.  Also on the RV042 under the firewall do you have "Block WAN Requests"

Disabled?  If not please disable this option.

THANKS

Thank you for the response, riroe.

However, I ended up opening those four ports on the firewall of the RV042 but I still ran into the same problem - if firewall is enabled, my Quick VPN fails at the connecting phase with the "5 reasons" error message.

Here's an interesting thing, though - after I make the initial VPN connection, I can re-enable the firewall on the RV042 and my VPN connection still works just fine. The problem with the firewall must only be related to the initial "connecting" phase.

I'm attaching images of my firewall settings as well as the port settings so you (or anyone) can confirm I have this set up correctly.

Ports 500 and 4500 are UDP, while 443 and 60443 are TCP, correct? Or do I need to open up UDP and TCP for each one of those ports?

If there is any more information you all need, please let me know.

Thank you!

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: