If this is a windows host as a destination, I've had great luck with WireShark on the destination to see just what does go in and out over a NIC.
-greg -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Matthew Grooms Sent: Wednesday, January 12, 2011 3:42 PM To: [email protected] Cc: [email protected] Subject: Re: [vpn-help] FVS338 tunnel established but can't ping remote IP's/SSH/DNS etc. On 1/12/2011 3:33 PM, David Borges wrote: > Matthew, > > Both subnets are /24. As for the firewall on 10.1.1.4. This issue > happens to all IP's on the internal network. I tried ssh'ing into a box > and tcpdump port 22 on the receiving box sees the ssh request but it > never replys. > > I'm sorry if I am missing something easy. I think it's so close ;/ > David, I'm not sure what to tell you. You need to figure out why the target hosts aren't responding to the client traffic. Have you tried using tcpdump src or dst [vpn client IP] from a target host to see if there is anything interesting? -Matthew _______________________________________________ vpn-help mailing list [email protected] http://lists.shrew.net/mailman/listinfo/vpn-help _______________________________________________ vpn-help mailing list [email protected] http://lists.shrew.net/mailman/listinfo/vpn-help
