Solved

Cisco ASA VPN Routing Issue

Posted on 2011-02-24
8
666 Views
Last Modified: 2012-05-11
I have a Cisco ASA firewall and I am having some very slight issues with my VPN clients.

I have several internal networks, all connected by point-to-point private T1's... They are the networks located at:

192.168.0.x
192.168.1.x
192.168.3.x
192.168.5.x
192.168.6.x
192.168.7.x

The ASA is located at 192.168.1.1.... The VPN clients are given addresses from a pool at 192.168.4.x

Here is the problem... When a client is connected via VPN they can reach ANY of the internal networks (p.s. all the routers are at 192.168.x.254)... EXCEPT the devices on the 192.168.0.x network.....

Here is the (pertinant) portion of the running config:


: Saved
:
ASA Version 8.2(2)
!
interface Ethernet0/0
 nameif inside
 security-level 100
 ip address 192.168.1.1 255.255.255.0
!
interface Ethernet0/1
 shutdown
 nameif vacant
 security-level 75
 no ip address
!
interface Ethernet0/2
 nameif dmz
 security-level 25
 ip address 10.1.1.177 255.255.255.240
!
interface Ethernet0/3
 nameif outside
 security-level 0
 ip address 203.66.100.178 255.255.255.240
!
ftp mode passive
dns server-group DefaultDNS
access-list outbound extended permit ip any any
access-list inside_nat0_outbound extended permit ip any 192.168.4.0 255.255.255.192
access-list to-dmz extended permit icmp any any
access-list dmz-in extended permit ip DMZ-Net 255.255.255.0 any
access-list dmz-in extended permit icmp any any
access-list inside extended deny udp any any eq 135
access-list inside extended permit udp any any eq tftp
access-list inside extended deny udp any any eq netbios-ns
access-list inside extended deny udp any any eq netbios-dgm
access-list inside extended deny udp any any eq 139
access-list inside extended deny tcp any any eq 135
access-list inside extended deny tcp any any eq 137
access-list inside extended deny tcp any any eq 138
access-list inside extended deny tcp any any eq netbios-ssn
access-list inside extended deny tcp any any eq 445
access-list inside extended deny tcp any any eq 593
access-list inside extended deny tcp any any eq 4444
access-list inside extended permit ip any any
ip local pool VPN-Pool 192.168.4.25-192.168.4.50 mask 255.255.255.0
global (dmz) 10 interface
global (outside) 10 interface
nat (inside) 0 access-list inside_nat0_outbound
nat (inside) 10 192.168.0.0 255.255.240.0
access-group inside in interface inside
access-group dmz-in in interface dmz
access-group to-dmz in interface outside
route outside 0.0.0.0 0.0.0.0 203.66.100.177 1
route inside 192.168.0.0 255.255.255.0 192.168.1.254 1
route inside 192.168.3.0 255.255.255.0 192.168.1.254 1
route inside 192.168.5.0 255.255.255.0 192.168.1.254 1
route inside 192.168.5.0 255.255.255.0 192.168.1.254 1
route inside 192.168.7.0 255.255.255.0 192.168.1.254 1
group-policy unity internal
group-policy unity attributes
 wins-server value 192.168.1.2 192.168.3.2
 dns-server value 192.168.1.2 192.168.3.2
 vpn-tunnel-protocol IPSec
 default-domain value mydomain.com
username unity password txOP8663574s9f6 encrypted privilege 0
username unity attributes
 vpn-group-policy unity
tunnel-group unity type remote-access
tunnel-group unity general-attributes
 address-pool VPN-Pool
 default-group-policy unity
tunnel-group unity ipsec-attributes
 pre-shared-key *****
0
Comment
Question by:ThePhreakshow
8 Comments
 
LVL 3

Author Comment

by:ThePhreakshow
ID: 34976115
The router located at 192.168.1.254 is aware of all of the networks and has no problem getting to devices on the 192.168.0.x network and vice-versa
0
 
LVL 79

Expert Comment

by:lrmoore
ID: 34976853
What about the router on the 192.168.0.x end of the P2P T1?
Does it have a route to 192.168.4.0 pointing the wrong direction?
0
 
LVL 33

Expert Comment

by:MikeKane
ID: 34982290
Can the VPN client tracert into 192.168.0.x?   Do you see the router as 192.168.1.254 as a 'hop'?   If you do, then I think you can eliminate the ASA as the source of the issue.    

As lrmoore mentioned, check the route on the router.   I would also mention to look at any ACL on the router as well.  

0
 
LVL 3

Author Comment

by:ThePhreakshow
ID: 34982867
It does NOT see the 192.168.1.254 router as a hop, and times out straight away.

When I try ANY of the other networks (3.x, 5.x, 6.x, 7.x) from a VPN client, the first hop in the route is the 192.168.1.254 router which is also on the same local private segment as the inside interface of the ASA.

The router at 192.168.0.254 is "managed" (poorly) by our new AT&T PTP services, so despite many attempts to get them to give me at least a show run from that router have failed.
0
PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

 
LVL 3

Author Comment

by:ThePhreakshow
ID: 34982965
what is strange, however is that the routers at 3.254, 5.254, 6.254 and 7.254 are all the same routers as the problem child at 0.254... They are all "managed" by AT&T and were all installed at the same time.

Again I will reiterate that the only problem I am having is with VPN clients that get something out of the 192.168.4.x pool. Otherwise connectivity from end to end on the PTP connections works fine.
0
 
LVL 33

Expert Comment

by:MikeKane
ID: 34983503
From the ASA CLI, can you ping into that subnet?  

Can we see the entire sanitized config from the ASA also...
0
 
LVL 30

Accepted Solution

by:
renazonse earned 500 total points
ID: 34987038
Have you verified that these particular VPN clients are not connecting from an internet connection where their internal private subnet is 192.168.0.x? 192.168.0.x is a very common internal subnet and may very easily be their subnet if they are using the VPN client from home or from another office. This will prevent their routing to the .0.x subnet.
0
 
LVL 3

Author Closing Comment

by:ThePhreakshow
ID: 35203972
That was EXACTLY the problem... The far away place that I had was using a private IP range that was in conflict with one of the networks behind my VPN.. I changed the network I was on to a far off IP range unrelated to my work network and it worked perfect.
0

Featured Post

Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Secure VPN Connection terminated locally by the Client.  Reason 442: Failed to enable Virtual Adapter. If you receive this error on Windows 8 or Windows 8.1 while trying to connect with the Cisco VPN Client then the solution is a simple registry f…
Let’s list some of the technologies that enable smooth teleworking. 
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
As a trusted technology advisor to your customers you are likely getting the daily question of, ‘should I put this in the cloud?’ As customer demands for cloud services increases, companies will see a shift from traditional buying patterns to new…

910 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

21 Experts available now in Live!

Get 1:1 Help Now