Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Community Member

Remote VPN Problem

My remote access vpn client is not able to connnect with internal network.

concentrator is connected with core switch and server 172.28.31.171(server) 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

VPN POOL: 172.28.31.128/248

Core switch Ip address is 172.28.31.91

Client is able to connect without any problem, but client not able to ping or connect with any network device.

In VPN session i can see bytes send and receive. My LAN-2-LAN tunnles are working fine without any problem.

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

Both connected on same switch but different VLAN. 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.

Core switch routing table

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.28.32.50 255.255.255.255 172.28.31.92

ip route 172.29.0.0 255.255.0.0 172.28.31.68

Concentrator routing table

172.28.31.160 255.255.255.224 via 172.28.31.91

172.28.92.0 255.255.255.0 via 172.28.31.91

172.29.0.0 255.255.0.0 via 172.28.31.91

192.168.0.0 255.255.0.0 via 172.28.31.91

172.28.31.170 255.255.255.255 via 172.28.31.91

Split tunnel is enable for

172.28.31.88/0.0.0.7

192.168.0.0/0.0.255.255

172.29.0.0/0.0.255.255

172.28.92.0/0.0.0.255

172.28.31.170/0.0.0.0

172.28.31.171/0.0.0.0

Please help me out, more than 10 days has passed but still not solution.

1 REPLY
Gold

Re: Remote VPN Problem

on your core switch, see if IPs from the pool range are even hitting the switch:

access-list 100 permit ip 172.28.31.128 0.0.0.7 any

deb ip packet 100

96
Views
0
Helpful
1
Replies
CreatePlease to create content