From: Sadiq Yakasai (sadiqtanko@gmail.com)
Date: Fri Mar 06 2009 - 07:40:33 ARST
Hi John,
Your culprit sounds like its the ACL you are using to define the split
tunnel on the EZVPN server. Can you show that to us please?
It should punch a hole for the 172.16.0.0/16 network not to be
"IPSec-tunnelled".
HTH,
Sadiq
On Fri, Mar 6, 2009 at 1:33 AM, John Edom <jedom123@gmail.com> wrote:
> Hi,
>
> I configured ezvpn on router to provide connectivity to remote user. I
> defined pool range 172.16.100.1-20 and enable split tunneling. Remote site
> (from where users are dialing) is having two local networks there i.e.
> 192.168.1.0/24 (users network), 172.16.1.0/24 (server farm) Now i am
> facing
> problem when user connect vpn, he can ping central IPs and
> its192.168.1.0/24
> network but unable to access 172.16.1.0/24 network there. when i see users
> PC routing table (route print) after connecting VPN, all traffic for
> 172.16.0.0 255.255.0.0 is going through VPN.
>
> Central Site (10.x.x.x)---------------ezvpn
> (172.16.100.1-20)-------------------RemoteSite (users network
> 192.168.1.0/24,
> server network 172.16.1.0/24)
>
> If i changes pool range from 172.16.100.1-20 (class B ) to 192.168.100.1-20
> (class C), it start working fine
>
> Any way to solve this issue..
>
> Best Regards
>
>
> Blogs and organic groups at http://www.ccie.net
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
>
>
>
>
>
>
>
-- CCIE #19963Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Mon Apr 06 2009 - 06:44:04 ART