RV042, quickVPN hangs

Question

I have 5 static IP addresses from my cable provider.  One IP address is for my network that I use IPCop as my firewall.  I have setup the RV042 router+vpn appliance with a different IP address so I can access my network remotely.  When I am connected to the RV042 directly I get an IP address from my home network (10.1.x.x).  When I try to connect from my friends house with DSL, behind a dlink router, my vpn client hangs at "verifying network" and then I get gateway not responding.  I have tried connecting directly to my cable router, configuring my network card with a third static IP from my cable provider, and get the same error.  Any suggestions?

Answer 1

I have 5 static IP addresses from my cable provider.  One IP address is
for my network that I use IPCop as my firewall.  I have setup the RV042
router+vpn appliance with a different IP address so I can access my
network remotely.
I just want to make sure that I am clear with your set up and what you are saying. From your original quote you state that you have 5 public IPs, and two (as of this point) are being used; one for IPCop and the other for the RV042 WAN connection.
Keeping in mind that the whole time you are trying to connect via QVPN.
Here is where I get a little lost:
When I am connected to the RV042 directly I get an IP address from my home network (10.1.x.x).
Not really sure what you meant. Did you mean you connected from your house to the RV by using the PPTP VPN server feature on the RV042, or did you mean you connected  to the RV using QVPN and your home router issued you a 10.1.x.x IP address?
When using QVPN; the connection established is an IPSec connection, so you will not receive an IP address from the remote router. This type of VPN connection creates a route statement on the participating routers so you are able to access the remote site and network resources.
I have tried connecting directly to my cable router, configuring my
network card with a third static IP from my cable provider, and get the
same error.
Here I understood that from your home (remote location - not local to the RV042) you assigned your computer a public IP address (a third of the original five) and you were still not able to connect. Now I would assume that at both locations home and work (RV042 side) you have the same ISP and you block of five IPs would be valid at either location.
So, working with that assumption what is the local IP address of your network on both sides of the tunnel?
One thing that can not be is having the same network ID on both sides of the tunnel. So if I connect from my home which has an internal IP address scheme of 172.16.10.20 the internal IP address of the RV cannot be 172.16.10.x.
This is what the tunnel whether established or not should look like:
IP: 172.16.20.1 (LAN) << == >> RV042 (WAN) 64.23.x.x <<==>> CLOUD <<==>> 159.35.x.x (WAN) "HOME ROUTER" <<==>>(LAN) 192.168.12.1 IP --- QVPN client
NOTE: the ip numbers do not matter so long both sides are different networks as shown. This would also be a different network: 192.168.20.x  and 192.168.30.x both with a subnet mask of 255.255.255.0.
Some other notes which may have already been mentioned is that if your PC is Vista the Firewall must be running, but if XP the Firewall needs to be turned off. In XP turning of the firewall via the GUI may not be enough, you may want to disable the service and try again. You can do this by clicking "Start" > "Run" then type "services.msc" (with out quotes) hit enter. Browse the serivces window for "Windows Firewall (ICS)" and just STOP the service while testing. If that works, then you may want to disable the service.
On a later post you stated:
Thanks for the information.  I am able to connect but I still am not
getting an IP address from my dhcp server and cannot connect to any of
my network resources.
Remmember you will not get an IP address from the remote side (RV042 network), but you should be able to get to shares via IP address. Later you said that you were not able to ping; don't get too hung up on not being able to ping, as the device you pinging may not be set to respong with echos. Try testing the connection using know running services of the remote site, such as file shares, remote desktop, VNC and so on. Maybe open up a command prompt and launch a telnet session to the DHCP server on port 67 and see if you are able to get there (the session should not time out).
Let us know what you are able to find.
Hope this helps a little.