2821 VPN Client ACL and NAT woes - can't access internal LAN
I'm having trouble getting my configuration to work properly and I've spent countless hours researching with no luck.
This is a simple problem I hope. Once connected to the 2821 via the Cisco VPN Client (V5), I can access the router's LAN IP and even telnet into it without any problems but I cannot access any other IP's on the network.
I started using Virtual-Templates and I couldn't get it to work so I changed the config per articles and posts that I had been reading.
How can I make this configuration work? Do I have to use virtual-templates (or should I)?
also I did notice you are using a VPN pool ip subent that is different from the LAN subnet?
Do all other devices on the LAN have the routers ip address as a default gateway?? You might want to change the VPN ip pool to a subnet of the LAN ip range for testing to see if it is a simple routing issue?
Re: 2821 VPN Client ACL and NAT woes - can't access internal LAN
This is not the solution you are looking for - if you have tested assinging the VPN users IP address in the same range as the LAN subnet - and this works? When you change the IP subnet to something differenet - and remote users can only access the router - the issue is not the VPN or router, the issue is your routing on the LAN.
Do you have another layer 3 routing device on your LAN? IS the default gateway on the servers & workstations point to the 2821 router?
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...