On 10/15/2013 01:17 AM, jslezak wrote:
On , jslezak <[email protected]> wrote:
The latest info I have says my problem is that the mobile device is
only getting a dynamically allocated private ip address, not a public
one.
Just thought I'd throw that out there for edification.
On Friday, September 6, 2013 11:54 AM, Jim Harle
<[email protected]> wrote:
Are the other nodes on the same LAN subnet as the router? Do those
other nodes reply to echo requests? Have you added those subnets to
the Policy tab in the Shrew client?
The virtual adapter not having a default gateway is normal, as policy
defines which networks are tunneled.
From:[email protected]
[mailto:[email protected]] On Behalf Of jslezak Sent:
Friday, September 06, 2013 2:09 AM To: [email protected]
Subject: [vpn-help] What next after tunnel enabled?
Please let me know what more specific questions I should ask? Or
point me to the appropriate what next document.
I have installed shrew on Windows XP. I have been able to connect to
a cisco RV042 router using shrew over a smartphone hotspot
connection. I have been able to ping the router.
However, I have not been able to connect to any other node in the
network. What steps am I missing?
I configured the router and client using
"https://www.shrew.net/support/Howto_Linksys";.
The router now has two Groups, one remote client is pnj_network.com
and the other is shrew.net. Otherwise, the configuration is as
similar as I can make them. The client would not allow me to specify
a DNS suffix of pnj_network, thus I used shrew.net.
ipconfig on my XP machine lists no entry for the Default Gateway.
Hi,
My guess would be that the phase2 negotiation (which occurs after you
see "tunnel enabled") is not completing correctly.
A bug report would help us to determine what is happening:
https://www.shrew.net/support/VPN_Bug_Report_Windows
_______________________________________________
vpn-help mailing list
[email protected]
https://lists.shrew.net/mailman/listinfo/vpn-help
