Remote access VPN problem

Unanswered Question
May 9th, 2008

My remote access client are not able to ping inside network.

my concentrator is connected with core switch.

My 172.28.31.171 is also connected in core switch. InterVLN routing is working fine. server and conncentrator is

able to reach other via core switch.

concentrator private Ip address 172.28.31.92/248

Public IP address: 208.74.112.157

VPN POOL: 172.28.31.128/248

Split tunnel is enable for 172.28.0.0/16, 172.29.0.0/16.

Routing on concentrator is

172.28.0.0/16 is connected via 172.28.31.91

172.29.0.0/16 is connected via 172.28.31.91

Core switch Ip address is 172.28.31.91

Core switch also has the route

ip route 0.0.0.0 0.0.0.0 172.28.31.85

ip route 10.0.0.0 255.255.224.0 172.28.31.68

ip route 10.11.0.32 255.255.255.224 172.28.31.68

ip route 172.28.0.0 255.255.0.0 172.28.31.68

ip route 172.28.0.0 255.255.224.0 172.28.31.77

ip route 172.28.31.128 255.255.255.248 172.28.31.92

ip route 172.29.0.0 255.255.0.0 172.28.31.68

ip route 172.31.205.224 255.255.255.224 172.28.31.68

ip route 192.168.249.0 255.255.255.0 172.28.31.68

ip route 192.168.250.0 255.255.255.0 172.28.31.68,

As u have tested you are able to connect but not able to reach anywhere, though from internal network I can ping your vpn IP 172.28.31.129.

In VPN session i can see sometimes bytes send and receive, and sometime only sending no recving.

No firewall involoved in the path between the concentrator and desired server 172.28.31.171.

Both connected on same switch but different VLAN. but Inter VLAN routing is working and both are able to ping.

ONly remote access client 172.28.31.128/248 is not able to reach anywhere.

VPN concentrator has public default filter on public interface and private filter on local interface.

I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.

Actions

This Discussion