So here is my issue. I have two sites, each with a Linksys RV042 on thier site.
We have setup a site-to-site VPN between these sites, and all traffic is running back and forth without isse.
At Site 1 we have configured the Client VPN for use with the QuickVPN software. Again, for site 1, this is not an issue. We are able to access all internal resources at Site 1 without issue (expect for some DNS related problems).
The problem that we have is attempting to access Site 2 resources via the QuickVPN connection at Site 1. Even though they are not suppose to exist, we are able to ping 192.168.26.1-6 (which are ghost addresses likely created by the RV042's) but no actual systems on at Site 2.
I have added the Client VPN connection at Site 2, but it has the same problem accessing resources at Site 1.
Hey Ed, what are your tunnel settings between the two sites. I would like to see your settings in the tunnel setup and see if I see something wrong with it. Are you including the whole subnet in the settings or just the ip address of the remote router?
Well, since when I am on either LAN segment I am able to communicate without issue, I am sure that the tunnel config is appropriate. But here is a summary of the configuration.
Since I have worked with other VPN products, my first guess is that the split-tunnel configuration of the QuickVPN configuration does not acknowledge that the remote network segment exists. At first I thought I had it working since I was able to ping 192.168.54.1 - 6 of the remote network; but again, those addresses do not actually exist on that network, and I am not able to ping any of the valid address on that segement, or connecf to network resources.
The issue is only when using the QuickVPN client, and not when actually on the network. So it is like the QuickVPN client does not know it is suppose to route that traffic on to the network, or that the remote computer does not know it is suppose to pass the traffic back through the tunnel. I mention this, since when I connect with the Quick VPN client, it does not seem to give me a internal address, it just uses my local address. I see no difference in my network interfaces or IP configuraiton using ipconfig; while most other VPN clients give you are virtual network interface that is used with the connection, which ends up with an internal IP address.
Any other suggestions? I would not figure that the client cannot handle this, since with this device I would expect this to be a standard configuration; but it is screwy when dealing with DNS not running on the router as well.
Here are the other settings for the tunnel, and there are no settings for the Client VPN settings or the client.
That is exactly what I am trying to do. Is that an official answer? I can live that, if that is the case.
I don't think it is too unbelievable that someone would want to do this with these routers.
The network has two separate segments, using the VPN site-to-site to allow data transfer between offices. Each office has a server that they use for local file services, with most services consolidated at the main office.
The Quick VPN gives functionality to connect to the offices, which again, this router is designed to support both Site-to-site and client access VPN’s; I would not think that using both of these features together would be uncommon. In the current situation, users now need to connect to whichever site they need files from, and need to ping-pong between VPN connections.
With that gripe made; thanks for confirming what I already thought was the case.
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...
** Update **These and a number of other issues have been addressed in
SRP520 MR3. Please see https://supportforums.cisco.com/docs/DOC-13853
for details on how to access this code.There have been a number of
reports of the SRP500 becoming unresponsive afte...
STANDARDSOURCECOMMENTSEthernet RJ-45 connector pin number12345678IEEE
802.3afusing data pairsRXDC+RXDC+TXDC-sparespareTXDC-sparespareIndustry
Standard for Embedded POE(used by Cisco Catalyst Switches)IEEE
802.3afusing spare pairs RXRXTXDC+DC+TXDC-DC-Indus...