On 6/29/2010 3:59 PM, Jerrard Holland wrote: > Shrew VPN client 2.1.5 > Windows 7 > Netgear FVS338 > > You guys are doing a great job of plodding me through this. The access > manager now shows me as connected, but I am not yet in tall grass. I > can't ping anything on the inside of the router. > > This time, let me give a little description of the Network. > > The inside range of the network is 192.168.10.xxx. More specifically, we > have a Netgear Readynas that serves on port 80, and three workstations > that we address with Remote Desktop. The baby step I am working on right > now is pinging, then logging to the readyNas. > My newest client logs are attached.
Hi Jerrard, You are handing out client addresses in the 192.168.10.0/24 range. The client can't use a virtual adapter address that exists in the network its trying to access. You need to pick another range for the pool that won't overlap. For example, try 192.168.20.1 -> 192.168.20.254 instead. -Matthew _______________________________________________ vpn-help mailing list [email protected] http://lists.shrew.net/mailman/listinfo/vpn-help
