cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
905
Views
0
Helpful
11
Replies

asa 8.2 access files share on outside network from VPN Client.

shlee1005
Level 1
Level 1

please help me

I have cisco asa 5505 with 8.2

 

outside is 111.22.200.51

inside is 192.168.1.0/24 dhcp

vpnpool is 192.168.10.1-192.168.10.30

configured split tunnel to vpn client to access web

 

I was able to connect from outside via vpn.

 

Goal is access fileserver(on window) on 111.22.200.21 from vpn clients.

internal client can access the share folder

vpn client cannot access ther share on 111.22.200.21

 

 

============================

names
name 192.168.1.1 ciscogw
name 111.21.200.1 umgw
!
interface Ethernet0/0
 switchport access vlan 2
!
interface Ethernet0/1
!
interface Ethernet0/2
!
interface Ethernet0/3
 switchport access vlan 5
!
interface Ethernet0/4
!
interface Ethernet0/5
 switchport access vlan 5
!
interface Ethernet0/6
 switchport access vlan 5
!
interface Ethernet0/7
 switchport access vlan 5
!
interface Vlan1
 nameif inside
 security-level 100
 ip address ciscogw 255.255.255.0
!
interface Vlan2
 nameif outside
 security-level 0
 ip address 111.22.200.51 255.255.255.0
!
interface Vlan5
 no nameif
 security-level 50
 ip address dhcp setroute
!
ftp mode passive
clock timezone MST -7
clock summer-time MDT recurring
dns server-group DefaultDNS
 domain-name vpn.nmecsc.org
access-list RAteam_splitTunnelAcl standard permit 192.168.1.0 255.255.255.0
access-list inside_nat0_outbound extended permit ip 192.168.1.0 255.255.255.0 192.168.10.0 255.255.255.192
pager lines 24
logging asdm informational
mtu inside 1500
mtu outside 1500
ip local pool vpnpool 192.168.10.1-192.168.10.30 mask 255.255.255.224

icmp unreachable rate-limit 1 burst-size 1
no asdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 0 access-list inside_nat0_outbound
nat (inside) 1 0.0.0.0 0.0.0.0
route outside 0.0.0.0 0.0.0.0 111.22.200.1 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
timeout floating-conn 0:00:00
dynamic-access-policy-record DfltAccessPolicy
http server enable
http 192.168.1.0 255.255.255.0 inside

no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart

  quit
crypto isakmp enable outside
crypto isakmp policy 10
 authentication pre-share
 encryption 3des
 hash sha
 group 2
 lifetime 86400
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd auto_config outside
!
dhcpd address 192.168.1.5-192.168.1.50 inside
dhcpd dns 8.8.8.8 8.8.4.4 interface inside
dhcpd wins 111.22.210.65 111.22.210.61 interface inside
dhcpd enable inside
!

threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
ssl trust-point ASDM_TrustPoint0 outside
webvpn
 enable outside
group-policy DfltGrpPolicy attributes
 banner value WARNING: Unauthorized access to this system is forbidden and will be prosecuted by law. By accessing this system, you agree that your actions may be monitored if unauthorized usage is suspected.
group-policy RA_SSLVPN internal
group-policy RA_SSLVPN attributes
 vpn-tunnel-protocol webvpn
 webvpn
  url-list value team
group-policy RAteam internal
group-policy RAteam attributes
 wins-server value 111.22.210.65
 dns-server value  8.8.8.8 8.8.4.4
 vpn-tunnel-protocol IPSec
 split-tunnel-policy tunnelspecified
 split-tunnel-network-list value RAteam_splitTunnelAcl
 default-domain value vpn.nmecsc.org
username teamssl2 password 5ZBa0qXxwLBPpvoR encrypted privilege 0
username teamssl2 attributes
 vpn-group-policy RA_SSLVPN
username team2 password 5ZBa0qXxwLBPpvoR encrypted privilege 0
username team2 attributes
 vpn-group-policy RAteam
username teamssl1 password 5ZBa0qXxwLBPpvoR encrypted privilege 0
username teamssl1 attributes
 vpn-group-policy RA_SSLVPN
username team1 password 5ZBa0qXxwLBPpvoR encrypted privilege 0
username team1 attributes
 vpn-group-policy RAteam
tunnel-group team type remote-access
tunnel-group team general-attributes
 default-group-policy RA_SSLVPN
tunnel-group team webvpn-attributes
 group-alias team enable
 group-url https://111.22.200.51/team enable
tunnel-group RAteam type remote-access
tunnel-group RAteam general-attributes
 address-pool vpnpool
 default-group-policy RAteam
tunnel-group RAteam ipsec-attributes
 pre-shared-key *
!
class-map inspection_default
 match default-inspection-traffic
!
!
policy-map type inspect dns preset_dns_map
 parameters
  message-length maximum client auto
  message-length maximum 512
policy-map global_policy
 class inspection_default
  inspect dns preset_dns_map
  inspect ftp
  inspect h323 h225
  inspect h323 ras
  inspect rsh
  inspect rtsp
  inspect esmtp
  inspect sqlnet
  inspect skinny 
  inspect sunrpc
  inspect xdmcp
  inspect sip 
  inspect netbios
  inspect tftp
  inspect ip-options
!
service-policy global_policy global
prompt hostname context
call-home reporting anonymous
Cryptochecksum:680b9059ca6ca6610857bab04d855031

11 Replies 11

rizwanr74
Level 7
Level 7

Lets say you have a translation for this public IP inside your network.

111.22.200.21 translated to 192.168.1.111

 

Now you permit that host to be injected into client routing table (on workstation), through this ACL.


access-list RAteam_splitTunnelAcl standard permit host 111.22.200.21

 

Let me know, if this helps.

 

Thanks

Rizwan Rafeek.

 

 

'Lets say you have a translation for this public IP inside your network.

111.22.200.21 translated to 192.168.1.111'

 

this part is confuse me. you want to add extra nic on server and connect to inside?

 

Is your file server at 111.22.200.21 is directly connected to internet? If yes then you need this.

Connect your file server to a switch and the inside interface of your ASA to the same switch.

Change your file server NIC to same ip-address range and let say it is 192.168.1.11 and lets says example your file server is running on port 32897 and so you allow traffic from internet to come in on that particular port.  You change the port number on ACL according to your file server setup.

 

Now apply these line on your ASA.

 

access-list outside_in extended permit tcp any host 111.22.200.21 eq 32897 

access-group outside_in in interface outside

static (inside,outside) 111.22.200.21 192.168.1.11 netmask 255.255.255.255

 

Hope that helps.

 

Thanks

Rizwan Rafeek.

if I cannot move 111.22.200.21 server to inside network, is it possible to have vpn clients to have same access rule as inside client?

From inside workstation, we can \\111.22.200.21 to access share folder.

"if I cannot move 111.22.200.21 server to inside network, is it possible to have vpn clients to have same access rule as inside client?"

 

Yes you can, as long as your ASA can reach (i.e. route-able) to that IP address: 111.22.200.21 through its inside interface or dmz interface, or other interfaces.

 And so, your static nat statement will change accordingly to respective interface, either "static (inside,outside)" or "static (dmz,outside)" 

 

thanks

 

 

 

"static (inside,outside)" or "static (dmz,outside)" 

it will take care inside and dmz to reach public server.

it seems like it is already exist because I can access .21 server from desktop connected to inside network.

how about vpn clients? it is on different subnet( 192.168.10.0).

 

Thanks you for your input.

If you say this host can be reached via inside interface then you add this line so that ASA will inject the route on remote-client workstation when users remote-in.

access-list RAteam_splitTunnelAcl standard permit host 111.22.200.21

access-list inside_nat0_outbound extended permit host 111.22.200.21 192.168.10.0 255.255.255.192

 

Since you say that this host is located inside the ASA, then you need to info ASA to route the traffic to inside the ASA.

 

X = equal IP address which ASA's inside interface is connected.

route inside 111.22.200.21 255.255.255.255 192.168.1.x

 

If this does not work, please post a diagram of your network, shows where your host: 111.22.200.21 is located in the network.

 

thanks

I just upgrade asa to 9.3

add access-list but still no luck. I attached the diagram.

 

name 192.168.1.1 ciscogw
ip local pool vpnpool 192.168.10.1-192.168.10.50 mask 255.255.255.0
!
interface Ethernet0/0
 switchport access vlan 2
!
interface Ethernet0/1
!
interface Ethernet0/7
!
interface Vlan1
 nameif inside
 security-level 100
 ip address ciscogw 255.255.255.0

interface Vlan2
 nameif outside
 security-level 0
 ip address 111.22.200.51 255.255.255.0

boot system disk0:/asa923-k8.bin
ftp mode passive
object network obj_any
 subnet 0.0.0.0 0.0.0.0
object network NETWORK_OBJ_192.168.1.0_24
 subnet 192.168.1.0 255.255.255.0
object network NETWORK_OBJ_192.168.10.0_26
 subnet 192.168.10.0 255.255.255.192
access-list ipsec_group_splitTunnelAcl standard permit 192.168.1.0 255.255.255.0
access-list ipsec_group_splitTunnelAcl standard permit host 111.22.200.21
access-list ipsec_group_splitTunnelAcl standard permit 111.22.200.0 255.255.255.0
pager lines 24
logging enable
logging asdm informational
mtu inside 1500
mtu outside 1500
icmp unreachable rate-limit 1 burst-size 1
asdm image disk0:/asdm-731-101.bin
no asdm history enable
arp timeout 14400
no arp permit-nonconnected
nat (inside,outside) source static NETWORK_OBJ_192.168.1.0_24 NETWORK_OBJ_192.168.1.0_24 destination static NETWORK_OBJ_192.168.10.0_26 NETWORK_OBJ_192.168.10.0_26 no-proxy-arp route-lookup
!
object network obj_any
 nat (inside,outside) dynamic interface
route outside 0.0.0.0 0.0.0.0 111.22.200.1 1
dynamic-access-policy-record DfltAccessPolicy
user-identity default-domain LOCAL
http server enable
http 192.168.1.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact

threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
ssl trust-point ASDM_TrustPoint0 outside
webvpn
 enable outside
 tunnel-group-list enable
group-policy ssl_vpn internal
group-policy ssl_vpn attributes
 vpn-tunnel-protocol ssl-clientless
 webvpn
  url-list value carino
group-policy DfltGrpPolicy attributes
group-policy ipsec_group internal
group-policy ipsec_group attributes
 dns-server value 8.8.8.8 8.8.4.4
 vpn-tunnel-protocol ikev1
 split-tunnel-policy tunnelspecified
 split-tunnel-network-list value ipsec_group_splitTunnelAcl

 

It is not possible, your file-server is not inside the network but rather it is directly connected to internet.  So it is not realistic.

 

Easiest solution for you is to put your file-server on a DMZ on ASA interface and then static-nat from 111.22.200.21 to an IP address off DMZ subnet.

 

Keep this line

access-list ipsec_group_splitTunnelAcl standard permit host 111.22.200.21

 

Remove this line:
no access-list ipsec_group_splitTunnelAcl standard permit 111.22.200.0 255.255.255.0

 

object network obj-172.16.0.2
host 172.16.0.2
nat (dmz,outside) static 111.22.200.21 service tcp 21


access-list outside_in extended permit tcp any host 172.16.0.2 eq 21

access-group outside_in in interface outside

 

Hope this helps.

Thanks

thank you, I think I can give up..

If you remove these two lines below, your remote-in client should be able to access the file-server directly from the public ip address itself and no need to access through the tunnel.

 

no access-list ipsec_group_splitTunnelAcl standard permit host 111.22.200.21
no access-list ipsec_group_splitTunnelAcl standard permit 111.22.200.0 255.255.255.0

 

These two lines will inject routes on remote-in vpn-clients workstation, to push the traffic for the IP-address and subnet into the tunnel, rather than access them directly off the tunnel and remove above two lines and try it.

 

I hope that make sense to your understanding.

Thanks 

Review Cisco Networking for a $25 gift card