10-31-2003 03:20 PM - edited 02-21-2020 12:51 PM
Hi,
We have a few VPN Clients connecting to VPN 3005 concentrator using SBC Cable.
SBC Cable gives these users Private IP Addresses in 172.16.0.0\16 range and then does NAT.
Unfortunately we also have 172.16.0.0\16 as one of our corporate subnets.
Users can connect fine and can access all corporate subnets except 172.16.0.0\16, which probably is due to the reason that the Client PC tries to send the packets through normal LAN connection and not through the VPN Connection.
We have tried the Cisco Client but it still doesn't work. The VPN group for these Clients is set to "Tunnel Everything".
Is there a solution to this problem ?
Regards \\ Naman
Regards \\ Naman
11-03-2003 08:00 PM
We are encountering the same issue when designing VPN remote access for a client. I think the only workaround is to NAT the corporate 172.16.0.0/16 network to another segment. Would like to see if there is another suggestion for workaround.
Best Regards,
Engel
11-06-2003 12:29 PM
Hi,
Actually we just resolved this problem using Cisco VPN Client 4.0.3A-K9.
With this newer version, a Cisco Virtual Network Adapter gets installed and effectively disables Client's Local LAN routes.
Regards \\ Naman
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide