QuickVPN doesn't connect to Cisco Router WRVS4400N
I'm getting frustrated this worked the first day a couple times and then I kept getting a network TIMEOUT.
And my logs says the following.
I have seen sevarl people post information on the fact this VPN software and router just dont' work and I should just toss it.
I can't believe CISCO would make a product like this that takes this long to get to work.
Anyone that can help here I would apprecaite it.
I have been checking WINDOWS firewalls and other FIREWALLS and just beating my head.
2010/02/07 18:25:22 [STATUS]OS Version: Windows Vista 2010/02/07 18:25:22 [STATUS]Windows Firewall Domain Profile Settings: OFF 2010/02/07 18:25:22 [STATUS]Windows Firewall Private Profile Settings: OFF 2010/02/07 18:25:22 [STATUS]Windows Firewall Private Profile Settings: OFF 2010/02/07 18:25:22 [STATUS]One network interface detected with IP address 192.168.5.32 2010/02/07 18:25:22 [STATUS]Connecting... 2010/02/07 18:25:22 [STATUS]Connecting to remote gateway with IP address: 184.108.40.206 2010/02/07 18:25:23 [WARNING]Server's certificate doesn't exist on your local computer. 2010/02/07 18:25:53 [STATUS]Remote gateway was reached by https ... 2010/02/07 18:25:53 [STATUS]Provisioning... 2010/02/07 18:26:02 [STATUS]Tunnel is configured. Ping test is about to start. 2010/02/07 18:26:02 [STATUS]Verifying Network... 2010/02/07 18:26:08 [WARNING]Failed to ping the LAN IP of the remote VPN Router! 2010/02/07 18:26:11 [WARNING]Failed to ping the LAN IP of the remote VPN Router! 2010/02/07 18:26:14 [WARNING]Failed to ping the LAN IP of the remote VPN Router! 2010/02/07 18:26:17 [WARNING]Failed to ping the LAN IP of the remote VPN Router! 2010/02/07 18:26:20 [WARNING]Failed to ping the LAN IP of the remote VPN Router! 2010/02/07 18:26:23 [WARNING]Ping was blocked, which can be caused by an unexpected disconnect. 2010/02/07 18:26:29 [STATUS]Disconnecting... 2010/02/07 18:26:35 [STATUS]Tunnel is disconnected successfully.
Re: QuickVPN doesn't connect to Cisco Router WRVS4400N
As the log states, the PING is not reaching the LAN side of the remote router. This is usually caused by the router blocking PING or as it's labled on the router: Block WAN Requests, under the Firewall tab. This message is also displayed when attempting to connect over Broadband Wireless; such as Verizon's Air Card, or AT&T's Wireless card. When testing a QVPN connection from the client to the router, first make sure you can ping your WAN IP Address of the router. And then perform a ping from the diagnostic page of the router back to your client's public IP. (The WAN IP of the router in front of the client). If the clients router is also blocking PING, the connection will not complete.
We are able to test your connection from our lab if necessary, feel free to call and test it.
Hi every one!!!When you are configuring a remote VPN connection, there
are some steps that are lost on the path. Here you can see those steps.
A) In your Cisco device: 1. Ensure you don´t have any rule denying the
traffic between the device and the remote...
You have a Cisco Unified Communications Manager (CUCM) system and want
to configure a SPA112 analog telephone adaptor (ATA) to register to the
CUCM so that you can use up to two analog phones or similar FXS devices
with the CUCM.In this application note, ...
Introduction: This document describes how to connect SG300 with Catalyst
switch via STP. Spanning Tree Protocol (STP) is a Layer 2 protocol that
runs on mainly on switches. The specification for STP is IEEE 802.1D.
The main purpose of STP is to ensure tha...