I have been hacking this issue for days... I have gotten rid of this Verifying Network issue on some networks by changing order of adapters (get Advanced tab (hit Alt) under "Change Adapter Settings" on Network and Sharing Center ... that solved the Verifying Network problem at home. In this case the pings to the remote routers intranet IP address were going out on the wrong network adapter (possibly other VPN software adapters, etc...). But still not over my Verizon hotspot (where PPTP works fine) would QuickVPN work with this fix.
I finally gave up on bogus Internet posts (change MTU size and use static IP, and other such nonsense), and installed Wireshark. Now I capture all ethernet level traffic between my laptop and the remote router.
I find that while the QuickVPN is stuck on "Veriyfing Network...", I see unanswered ESP packets going out from PC to the remote router. No answer ... then eventually I get the dreaded "Remote network not responding ...". Indeed. I assume these ESP packets are containing encrypted PINGs to the remote router. So clearly my local laptop is sending out these PINGs, and either the network is munching them or the remote router is getting them and dropping them on the floor. Or perhaps the local router, in this case my Samsung S3, is not return the ICMP response to my laptop due to some NAT bug... but all other traffic works OK.
I dunno. Just thought I would report the low level trace results.
Windows firewall has nothing to do with it. If Win firewall was blocking a port it would notify you. In any case these ESP packets are originating from my machine, so WIn firewall would not block return packets.
back at home, I have two network connections, Ethernet and Wireless. Ethernet doesn't work, and I don't see any ESP (PING) packets going out on the wire! I suspect it's trying to send packets out on the Wireless connection which is also connected to the router. The routing metric though favors Ethernet of course, and also the connection was initiated on Ethernet, so you'd think QuickVPN and Windows would continue to test the remote ping on the EThernet connection.
Switch to Wireless and QuickVPN works fine, and I see the ESP packets go out AND response come back from the remote gateway! Interestingly enough, however, there is no route to my remote router in the 'route print' report. Should there not be a route over to the tunnel for traffic to my remote subnet? There is when I use PPTP instead of QuickVPN.
Well,apparently QuickVPN does not use tunnel mode encapsulation using routing tables. Instead it is using Windows Firewall to create rules for which traffic is to be encrypted, using rules like IPChains forwarding rules on Linux. That's why there is no route in the routing table. You can check in Windows Firewall and find the Security rules there... with the tunnel endpoints defined as you would expect.
Switching back and forth between WiFi and Ethernet, now both Ethernet and WiFi work, and I cannot figure out what changed. ESP packets get response on both interfaces. So now I have verified QuickVPN to work thru wifi and ethernet at my house. But trying through WiFi hotspot on Verizon SGS3, no can do. Outgoing ESP packets from my laptop never get a response back. I conclude this is a problem with either Verizon or the SGS3.
Hello, This article will describe how to configure PPTP VPN on the new
RV340/345 routers from the Small Business series. RV340/345
Configuration The first step is to enable the PPTP Server: Go to VPN ->
PPTP Server Change PPTP Server: from Off to On Selec...
Article ID:5748 Use TheGreenBow VPN Client to Connect with RV34x Series
Router Introduction A Virtual Private Network (VPN) connection allows
users to access, send, and receive data to and from a private network by
means of going through a public or share...
Article ID:5728 Configure a Teleworker VPN Client on the RV34x Series
Router Objective The Teleworker VPN Client feature minimizes the
configuration requirements at remote locations by allowing the device to
work as a Cisco VPN hardware client. When the T...