Hi Kevin, To your question about the intermittent pinging, yes, I can ping again (a 3rd, nth time) and sometimes get through to the 192.169.1.x address and sometimes not (can't reach the destination address). However, I was able to connect via remote desktop to a PC on that remote network 192.168.1.100. So as you suggested, maybe the router treats the pings as a menace.
I agree with you that 0 bytes received is a red flag and changing the assigned IP subnet from 192.168.1.x to 192.168.2.x in the Netgear Mode Config was the key in solving. So yep, the problem was on the router end. Thanks Mike and Kevin for your great help! Mike -----Original Message----- From: kevin shrew-vpn <[email protected]> To: [email protected] Sent: Sun, May 9, 2010 9:29 pm Subject: Re: [vpn-help] VPN not passing traffic using Shrew Client On Sun, 09 May 2010 19:22:35 -0400 [email protected] wrote: > Attached is the iked.log file as you requested. As well as a screenshot.png of the two VPN Trace tabs you mentioned in your reply for your convenience. As always, it's a good idea to run a virus scan. The 2.1.6 Beta did not solve the issue. FYI:. I also have the Netgear VPN client on a different PC going through my same home network. It connects fine and I can communicate Hi Mike, the red flag that I see on the screenshot is on the SA tab, here it shows that you've been connected for over a minute yet no data as come through the tunnel from the gateway to your PC. I assume that ome of the 3.96 KB that you've sent are some pings which should enerate a response. That suggests the problem lies at the other end. However, you appear to have made a change afterwards based on MikeW's ail which has gotten you farther ahead, so maybe the zero returned ytes is now moot. ______________________________________________ pn-help mailing list [email protected] ttp://lists.shrew.net/mailman/listinfo/vpn-help
_______________________________________________ vpn-help mailing list [email protected] http://lists.shrew.net/mailman/listinfo/vpn-help
