cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
834
Views
0
Helpful
4
Replies

Can't Access Subnet When VPN'd In

Thomas Reiling
Level 1
Level 1

When I vpn into our network it gives me an ip address within the range: 192.168.200.1 - 192.168.200.50.

The following access works when vpn'd in: 192.168.200.x -> 10.2.28.x

The following access does not work when vpn'd in: 192.168.200.x -> 192.168.50.x

Can someone please let me know what I need to have in the PIX config to make this work?

Thank you,

Thomas

1 Accepted Solution

Accepted Solutions

1. Add 192.168.50.0 to your split tunnel acl

access-list remotevpnbhc_splitTunnelAcl permit ip 192.168.50.0 255.255.252.0 any

2. add the traffic between 192.168.50.0 and vpn client to ACL which is used by NAT 0

access-list vpn_insideacl permit ip 192.16.50.0 255.255.252.0 192.168.200.0 255.255.255.0

View solution in original post

4 Replies 4

Yudong Wu
Level 7
Level 7

In general

1) nat bypass for traffic 192.168.200.x -> 192.168.50.x, make sure this traffic is included in ACL which is used by nat 0 command.

2) check routing

3) if using split-tunnel, make sure 192.168.50.x is included in split tunnel acl.

Yudong,

Thank you for the quick response.  I have attached a scrubbed version of our config.  Can you please take a quick look and see if anything missing is obvious?

Thanks again,

Thomas

1. Add 192.168.50.0 to your split tunnel acl

access-list remotevpnbhc_splitTunnelAcl permit ip 192.168.50.0 255.255.252.0 any

2. add the traffic between 192.168.50.0 and vpn client to ACL which is used by NAT 0

access-list vpn_insideacl permit ip 192.16.50.0 255.255.252.0 192.168.200.0 255.255.255.0

Yudong,

Thank you very much.  Your suggestion worked!  All I had to do after adding your lines was to add the route.

Also, for the 192.168.50.0 network I had to use a subnet a 255.255.255.0 instead of 255.255.252.0.

Thank again!

Thomas