Windows 7 Connect to RV 120w

paul0041 · ‎09-19-2010

Hello,

I have been trying to connect to the RV 120w via the Quick VPN client, but no success. See program log below. I was told by support that this is something on my machine that is using port 4500 or port 500 or both. So running netstat shows:

C:\Users\pcb>netstat -o -a

Active Connections

Proto Local Address          Foreign Address        State           PID
UDP    [::]:500               *:*                                    1220
UDP    [::]:4500              *:*                                    1220

and process id 1220 is svchost.exe.

I am unsure where to go from here. I would rather use the Windows 7 VPN client or Forticlient to establish a connection with this router, but can't find any resources that really explain VPN and the RV 120w or how that might be accomplished. Any help in getting the Quick Connect software or another client to work with this router would be greatly appreciated.

Quick Connect Log:

Note: Quick connect incorrectly identifies my system as XP - I have it running on Windows 7 Professional. Not sure if that matters...

C:\Users\pcb>

2010/09/19 15:20:45 [STATUS]OS Version: Windows XP
2010/09/19 15:20:46 [STATUS]One network interface detected with IP address 192.168.42.2
2010/09/19 15:20:46 [STATUS]Connecting...
2010/09/19 15:20:46 [DEBUG]Input VPN Server Address = xxx.22.41.79
2010/09/19 15:20:46 [STATUS]Connecting to remote gateway with IP address: xxx.22.41.79
2010/09/19 15:20:46 [STATUS]Windows Firewall is ON
2010/09/19 15:20:46 [WARNING]Server's certificate doesn't exist on your local computer.
2010/09/19 15:20:50 [STATUS]Remote gateway was reached by https ...
2010/09/19 15:20:50 [STATUS]Provisioning...
2010/09/19 15:20:53 [STATUS]Success to connect.
2010/09/19 15:20:53 [STATUS]Tunnel is configured. Ping test is about to start.
2010/09/19 15:20:53 [STATUS]Verifying Network...
2010/09/19 15:20:59 [WARNING]Failed to ping remote VPN Router!
2010/09/19 15:21:02 [WARNING]Failed to ping remote VPN Router!
2010/09/19 15:21:05 [WARNING]Failed to ping remote VPN Router!
2010/09/19 15:21:08 [WARNING]Failed to ping remote VPN Router!
2010/09/19 15:21:11 [WARNING]Failed to ping remote VPN Router!
2010/09/19 15:21:16 [WARNING]Ping was blocked, which can be caused by an unexpected disconnect.
2010/09/19 15:21:19 [STATUS]Disconnecting...
2010/09/19 15:21:24 [STATUS]Success to disconnect.

riroe · ‎09-20-2010

To check further about the ports being blocked I would suggest you go to GRC.com and then choose the program

called ShieldsUP and check to make sure ports 443,500,4500, and 60443 are not being blocked. ISP's block these ports

sometimes. Also are you using the latest QVPN software? The latest version is 1.4.1.2

THANKS

paul0041 · ‎09-21-2010

Thank you for your reply. Yes I have confirmed that ISP is not blocking at the location I was trying to connect from, but these ports did show "stealth" mode. Latest version of software is in use. Since a connection starts, but won't fully connect because of the ping error, I think it is narrowed down to something on my machine that is holding ports 500 and 4500 open? I'm not sure, but netstat shows them there and Cisco Support seemed to think so.

I use Forticlient (which uses ipsec) to connect to another office network without any problems on this machine from the same locations that quick connect fails in, so I was hoping that it might be possible to set up an IKE and VPN policy that would allow either the Windows 7 client or Forticlient to connect. Both of these clients are fully configurable, while the quick connect isn't. I am not sure how to configure these policies for a client though. They want endpoint ip's and the client will be in various locations... Maybe someone knows of a good resource that explains configuration of the policies? Or maybe someone knows how I can go about identifying the specific process(es) that are holding a UDP session on these ports so I get quick connect working?

Thanks much!

Paul

bbbraunschweig · ‎09-22-2010

Just a quick thought. Make sure you run QuickVPN as Administrator or it won't have rights to use IPSEC. I think what you see in netstat is svchost.exe listening on those ports. But this should not interfere with sending to those ports on another machine. Good luck.

paul0041 · ‎09-27-2010

Yes, was running it as administrator, but Quick Connect ended up being more trouble than it was worth.... never did figure it out.

These instructions were very helpful though. They work fine for Forticlient on Windows 7 too.

http://www.scribd.com/doc/31577498/Cisco-RV120W-Wireless-VPN-Firewall-GreenBow-IPSec-VPN-Client-Software-Configuration