Question Locked

How come VPN Users are not able to connect to website in a DMZ?

0 helpful
23 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Hi,

I have a internal network and a DMZ. In the DMZ there is a webserver.

Internal and HTTP clients can access the website in the DMZ, but when users access the network via VPN (cisco asa 5510) they are not able to access those websites hosted on the webserver.

I have no experience with this subject, so any help would be appreciated!

Any ideas?

23 replies

by netman1958

Does the access list associated with the VPN allow access to the DMZ's subnet?

by nbmprivat

I guess you mean under Security Policy Rules?

I just added vpn/24 (source) - dmz-network (destination) in the "outside" policy. Now i must test.

Or did you mean something else?

by netman1958

is this? Is it a point-to-point VPN between your 5510 and another VPN device or is it an SSL VPN or a VPN client on a computer to the 5510? Feel free to post your sanitized config.

by nbmprivat

It's a VPN client (Cisco Systems VPN Client) on the computer to the 5510.

How do i post the config? I have no experience with firewalls/firewalls/VPN.

by netman1958

To post your config, connect to hte ASA either by the console or telnet/ssh. If you are using Putty or Hyperterminal, you can enable them to save the session to a file. Once connected, go into privileged mode with the command "enable". Then run the command "show run". This will cause your running config to display a page at a time. If you are capturing the session to a file, just keep hitting the space bar until it returns to the prompt. Otherwise, copy each page of output to the clipboard and paste it in a text file before you hit the space bar. After you have the complete config in a file, go through it and mask your passwords with "************" then copy / paste the file into a new post here.

by nbmprivat

I dont think any passwords are showing here. Otherwise please delete my post!

: Saved
:
ASA Version 7.2(3)
!
hostname pix1
domain-name dilf.dk
enable password a23WFee/cfUp5U3Q encrypted
names
name 192.168.1.8 dilf-exchange
name 192.168.1.10 odin
name 192.168.128.0 vpn
name 192.168.1.0 inside-network
name 192.168.2.11 loke
name 192.168.2.12 heimdal
name 192.168.1.7 dilf-master
name 192.168.1.16 SAN
name 192.168.1.9 deathstar
name 192.168.1.138 IT3
name 188.120.77.163 public-mail-ip
name 188.120.77.164 public-webmail-ip
name 188.120.77.165 public-website-dilf-ip
name 188.120.77.166 public-website-kairos-ip
name 192.168.2.0 dmz-network
name 192.168.2.15 kairostest
dns-guard
!
interface Ethernet0/0
nameif outside
security-level 0
ip address 188.120.77.162 255.255.255.240
ospf cost 10
!
interface Ethernet0/1
nameif inside
security-level 100
ip address 192.168.1.1 255.255.255.0
ospf cost 10
!
interface Ethernet0/2
nameif dmz
security-level 50
ip address 192.168.2.1 255.255.255.0
ospf cost 10
!
interface Ethernet0/3
shutdown
no nameif
no security-level
no ip address
!
interface Management0/0
shutdown
nameif management
security-level 100
ip address 172.16.1.1 255.255.255.0
ospf cost 10
management-only
!
passwd a23WFee/cfUp5U3Q encrypted
boot system disk0:/asa723-k8.bin
ftp mode passive
clock timezone CEST 1
clock summer-time CEDT recurring last Sun Mar 2:00 last Sun Oct 3:00
dns server-group DefaultDNS
domain-name dilf.dk
access-list outside_access_in extended permit icmp any any echo-reply
access-list outside_access_in extended permit icmp any any time-exceeded
access-list outside_access_in extended permit icmp any any unreachable
access-list outside_access_in extended permit ip vpn 255.255.255.0 inside-network 255.255.255.0
access-list outside_access_in extended permit ip vpn 255.255.255.0 dmz-network 255.255.255.0
access-list outside_access_in extended permit tcp any host public-mail-ip eq smtp
access-list outside_access_in extended permit tcp any host public-webmail-ip eq imap4
access-list outside_access_in extended permit tcp any host public-webmail-ip eq https
access-list outside_access_in extended permit tcp any host public-website-kairos-ip eq www
access-list outside_access_in extended permit tcp any host public-webmail-ip eq ftp
access-list outside_access_in extended permit tcp any host public-website-dilf-ip eq www
access-list dmz_access_in extended permit tcp host heimdal any eq smtp
access-list dmz_access_in extended permit udp host heimdal any eq domain
access-list dmz_access_in extended permit tcp host heimdal any eq www
access-list dmz_access_in extended permit tcp host heimdal any eq https
access-list dmz_access_in extended permit tcp host loke host odin eq 1433
access-list dmz_access_in extended permit udp host loke any eq domain
access-list dmz_access_in extended permit tcp host loke any eq www
access-list dmz_access_in extended permit tcp host loke host dilf-master eq 1801
access-list dmz_access_in extended permit tcp host loke any eq smtp
access-list dmz_access_in extended permit tcp host loke any eq https
access-list dmz_access_in extended permit tcp host kairostest any eq www
access-list dmz_access_in extended permit tcp host kairostest any eq https
access-list dmz_access_in extended permit tcp host loke host deathstar eq 1433
access-list dmz_access_in extended permit tcp host loke any eq 1500
access-list dmz_access_in extended permit udp host loke any eq 1500
access-list dmz_access_in extended permit tcp host loke any eq ftp
access-list dmz_access_in extended permit tcp host 192.168.2.66 eq www any eq www
access-list dmz_access_in extended permit tcp host SAN any
access-list dmz_access_in extended permit tcp host loke vpn 255.255.255.0 eq www
access-list dmz_access_in extended permit tcp host kairostest any eq smtp
access-list dmz_access_in extended permit tcp host kairostest host deathstar eq 1433
access-list dmz_access_in extended permit udp host kairostest any eq domain
access-list dmz_access_in extended permit tcp host kairostest host dilf-master eq 1801
access-list inside_nat0_outbound extended permit ip inside-network 255.255.255.0 vpn 255.255.255.0
access-list inside standard permit inside-network 255.255.255.0
pager lines 24
logging enable
logging timestamp
logging buffer-size 16348
logging asdm-buffer-size 200
logging monitor notifications
logging buffered notifications
logging trap notifications
logging history notifications
logging asdm informational
logging device-id hostname
mtu outside 1500
mtu inside 1500
mtu dmz 1500
mtu management 1500
ip local pool vpn-scope 192.168.128.2-192.168.128.20
icmp unreachable rate-limit 1 burst-size 1
icmp permit any echo-reply outside
icmp permit any unreachable outside
asdm image disk0:/asdm-522.bin
no asdm history enable
arp timeout 14400
nat-control
global (outside) 1 interface
global (dmz) 1 interface
nat (inside) 0 access-list inside_nat0_outbound
nat (inside) 1 inside-network 255.255.255.0
static (inside,dmz) tcp odin smtp odin smtp netmask 255.255.255.255
static (inside,dmz) tcp dilf-master 1801 dilf-master 1801 netmask 255.255.255.255
static (inside,dmz) tcp odin 1433 odin 1433 netmask 255.255.255.255
static (inside,dmz) tcp deathstar 1433 deathstar 1433 netmask 255.255.255.255
static (inside,outside) tcp public-webmail-ip imap4 odin imap4 netmask 255.255.255.255
static (inside,outside) tcp public-webmail-ip ftp SAN ftp netmask 255.255.255.255
static (inside,outside) tcp public-webmail-ip https odin https netmask 255.255.255.255
static (dmz,outside) public-website-dilf-ip kairostest netmask 255.255.255.255
static (dmz,outside) public-mail-ip heimdal netmask 255.255.255.255
static (dmz,outside) public-website-kairos-ip loke netmask 255.255.255.255
access-group outside_access_in in interface outside
access-group dmz_access_in in interface dmz
route outside 0.0.0.0 0.0.0.0 188.120.77.161 1
route inside dilf-master 255.255.255.255 192.168.1.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 uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server RADIUS protocol radius
http server enable
http 192.168.1.118 255.255.255.255 inside
http 192.168.1.11 255.255.255.255 inside
http 192.168.1.140 255.255.255.255 inside
http 192.168.1.105 255.255.255.255 inside
http 192.168.1.126 255.255.255.255 inside
http 83.92.8.24 255.255.255.255 outside
http inside-network 255.255.255.0 management
http 192.168.1.15 255.255.255.255 inside
http IT3 255.255.255.255 inside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
crypto ipsec transform-set jkn-trans esp-3des esp-md5-hmac
crypto dynamic-map dynmap 10 set transform-set jkn-trans
crypto map jkn-map 30 ipsec-isakmp dynamic dynmap
crypto map jkn-map interface outside
crypto isakmp enable outside
crypto isakmp policy 10
authentication pre-share
encryption 3des
hash md5
group 2
lifetime 86400
crypto isakmp nat-traversal 20
client-update enable
telnet timeout 5
ssh 83.90.238.242 255.255.255.255 outside
ssh timeout 5
console timeout 10
vpdn username sv password *********
dhcpd address 172.16.1.10-172.16.1.20 management
dhcpd enable management
!
!
class-map inspection_default
match default-inspection-traffic
!
!
policy-map type inspect dns migrated_dns_map_1
parameters
message-length maximum 512
policy-map global_policy
class inspection_default
inspect dns migrated_dns_map_1
inspect ftp
inspect h323 h225
inspect h323 ras
inspect rsh
inspect rtsp
inspect sqlnet
inspect skinny
inspect sunrpc
inspect xdmcp
inspect sip
inspect netbios
inspect tftp
!
service-policy global_policy global
group-policy vpn3000 internal
group-policy vpn3000 attributes
dns-server value 192.168.1.7
split-tunnel-policy tunnelspecified
split-tunnel-network-list value inside
default-domain value dilf.dk
address-pools value vpn-scope
username denice password 4i/YM.cvO4HOkbV/ encrypted
username mortenc password MuS4JK5WsOmD6StU encrypted
username camillah password Yu57eadvH6Dcx3YM encrypted
username carsten password GyOnk5J2IAL01TXq encrypted
username kirsten password j2GnKFxmD.WeGVLe encrypted
username mortenm password zGwhLUvxzdPgnHfr encrypted
username captokonto password kSnYCdg6ofgA77nO encrypted
username miec password /8d.BJg5WEBRjxzM encrypted
username usertest password vHEkJH8AWqY+OZgMdBVAGA== nt-encrypted
username usertest attributes
vpn-tunnel-protocol IPSec
group-lock value DefaultRAGroup
username servicegruppen password b/MSKf2yvkXUoICz encrypted
username berit password pwwVO7MGDeqmjXo/ encrypted
username ebita password 9WZv77dQ6rkR1.xi encrypted
username nicolai password u.vUujDnRcIZqymu encrypted
username mette password LkJGZAtXCBOArnXB encrypted
username karent password D9aDlAdXz4KERz1T encrypted
username tobias2 password vHEkJH8AWqY+OZgMdBVAGA== nt-encrypted
username tobias2 attributes
vpn-tunnel-protocol IPSec
group-lock value DefaultRAGroup
username tobias password 5Yk62l6dmm79C2z5 encrypted
username tobias attributes
vpn-group-policy DfltGrpPolicy
username toni password MUxV7zleBlZV2NmN encrypted
username unisys password o5i8GEabDlDtfjTe encrypted
username tomb password nw3DvEEmuN361z2H encrypted
username sorenv password .D2tK6VyXIcQ1Kx9 encrypted
username sorenkj password XRzQ28RVBHO42IKI encrypted
username Lasse password 5QTha3fQUUT88RhF encrypted
username kurt password jihAZ31/ZkgoapC9 encrypted
username jesper password ZG4prnkKi2nnewiW encrypted
username andersaa password JtDL/q7I88cUYrpw encrypted
username anders password d/zaT9pRuyEE9rwW encrypted
username jens password VfdCNc.90ppKrX7u encrypted
tunnel-group DefaultRAGroup general-attributes
authentication-server-group (outside) LOCAL
tunnel-group DefaultRAGroup ipsec-attributes
pre-shared-key *
tunnel-group vpn3000 type ipsec-ra
tunnel-group vpn3000 general-attributes
address-pool vpn-scope
authentication-server-group (outside) LOCAL
default-group-policy vpn3000
tunnel-group vpn3000 ipsec-attributes
pre-shared-key *
prompt hostname context
Cryptochecksum:c2dfe0e06ed7f59c9c923779986db659
: end
asdm image disk0:/asdm-522.bin
no asdm history enable

by netman1958

This line specifies the subnets the VPN can access:
"split-tunnel-network-list value inside"
"inside" refers to access-list named inside that looks like this:
"access-list inside standard permit inside-network 255.255.255.0"
It only allows access to the "inside-network" (192.168.1.0)
These lines prevent NAT being applied to traffic between the inside network and VPN :
"nat (inside) 0 access-list inside_nat0_outbound"
"access-list inside_nat0_outbound extended permit ip inside-network 255.255.255.0 vpn "

You need to add the "name 192.168.2.0 dmz-network" to the above by adding this to your config:
"access-list inside standard permit dmz-network 255.255.255.0"
"access-list inside_nat0_outbound extended permit ip dmz-network 255.255.255.0 vpn "

Add those lines and give it a try. Post back with the results.

by nbmprivat

That's GREAT if that works!!! :)

Can you please explain to me how to do this in the Cisco ASDM?

by nbmprivat

I gave it a shot but it didnt work :-(

No change. Without VPN the our websites are reachable.

With VPN connection the website gives me the following message:

Under construction
The site you are trying to view does not currently have a default page... bla bla
If you are the Web site administrator and feel you have received this message in error, please see "Enabling and Disabling Dynamic Content" in IIS Help.

by netman1958

I rarely ever use ASDM and to make the changes I suggested would take longer with ASDM than with the CLI. To do it with the CLI, telnet or ssh to the ASA. Type the followingcommands at the prompt (press ENTER after each command):
pix1> enable
(you will be prompted for the password. enter it.)
pix1# conf t
pix1(config)# access-list inside standard permit dmz-network 255.255.255.0
pix1(config)# access-list inside_nat0_outbound extended permit ip dmz-network 255.255.255.0 vpn
pix1(config)# exit
pix1#wr
pix1#exit
pix1>exit

Then try your VPN access to the DMZ.

by nbmprivat

Thanks, the first line was succesfull but second line gave me the following error:

Result of the command: "access-list inside_nat0_outbound extended permit ip dmz-network 255.255.255.0 vpn"

access-list inside_nat0_outbound extended permit ip dmz-network 255.255.255.0 vpn
ERROR: % Incomplete command

by netman1958

I left off the mask. The command should look like this:
"access-list inside_nat0_outbound extended permit ip dmz-network 255.255.255.0 vpn 255.255.255.0"

by nbmprivat

That went through.

In the NAT config in ASDM there are now two new lines added:

No: 1 Type: Exempt Source: inside-network/24 Destination: vpn/24 Interface: Outbound
No: 2 Type: Exempt Source: dmz-network/24 Destination: vpn/24 Interface: Outbound

I will let you know if it works!

by nbmprivat

I gave it a shot but it didnt work

No change. Without VPN the our websites are reachable.

With VPN connection the website gives me the following message:

Under construction
The site you are trying to view does not currently have a default page... bla bla
If you are the Web site administrator and feel you have received this message in error, please see "Enabling and Disabling Dynamic Content" in IIS Help.

by nbmprivat

By the way...

The internal wiki website is reachable by VPN connection, but the websites in the DMZ are not. ARGH!

by nbmprivat

When adding www in front of the webpage in IE i get an DNS related error.

Either "The Domain Name Server (DNS) is not reachable" or "The Domain Name Server (DNS) does not have a listing for the website's domain".

When in the internal network I can't ping servers in the DMZ.

When connected via VPN i can connect to the website by WAN IP address, but not internal IP.

by majunamar

After adding the below configuration check if your are able to telnet your DMZ server on https (TCP 443) port to see if it listens. If you are then not able to access the website then it might well be DNS problem. You might need to do a local IP mapping on the DNS server.

by majunamar

Allow DMZ traffic in split-tunnel configuration by adding the below access list.
"access-list inside standard permit dmz-network 255.255.255.0"

Your VPN traffic destined to DMZ might be translated. Add the following rules to prevent it from being translated.

nat (dmz) 0 access-list vpn_nat0_DMZ
access-list vpn_nat0_DMZ extended permit ip dmz-network 255.255.255.0 vpn 255.255.255.0

Clear the NAT translation by using the following commands.
Clear xlate
Clear local

Let me know if this works. I have given an "ip" access to test if it works you can also allow "icmp" to check the connectivity. If it works then you can tie it down to very specific rule allowing only "tcp 443"

by netman1958

I decided to get to the bottom of this, so I setup a clone of your network in GNS3. I used a laptop connected via ethernet to the computer running GNS3. I installed the cisco VPN client on the laptop. To eliminate any issues with access-lists, I changed access-list "access-list outside_access_in " so that it only had these 2 lines:
access-list outside_access_in extended permit ip any any
access-list outside_access_in extended permit icmp any any
I change list "dmz_access_in" so that it only had these 2 lines:
access-list dmz_access_in extended permit ip any any
access-list dmz_access_in extended permit icmp any any
(This was probably unnecessary, but I wanted to eliminate any issues with access lists)

Next, I configured list "access-list inside" so that it looked like this:
access-list inside standard permit inside-network 255.255.255.0
access-list inside standard permit dmz-network 255.255.255.0
and I configured list "inside_nat0_outbound" like this:
access-list inside_nat0_outbound extended permit ip inside-network 255.255.255.0 vpn 255.255.255.0
access-list inside_nat0_outbound extended permit ip dmz-network 255.255.255.0 vpn 255.255.255.0

I added a new NAT statement:
nat (dmz) 0 access-list inside_nat0_outbound

I added a username and password for myself like this:
username netman password ********** encrypted
username netman attributes
vpn-group-policy vpn3000
vpn-tunnel-protocol IPSec

I changed the pre-shared key for tunnel-group vpn3000 to something I knew. Then I went to the laptop and started the Cisco VPN client. I congiured a connection to use tunnel-group vpn3000 and the password I configured and when prompted for username and password I entered my credentials. The tunnel estasblished and I was able to ping successfully from the laptop to 192.168.1.2 (which was the only device I had connected to the ASA's LAN interface) and I was able to ping 192.168.2.2 (which was the only device I had connected to the ASA's DMZ interface).

If you want, I can post the entire working config.

by nbmprivat

Did you have same problem as me with the test environment?

I will get back to you during the week when i have time to test. I appreciate it!

by nbmprivat

Finally!

The magic code was "nat (dmz) 0 access-list inside_nat0_outbound" which you statet above. Now it works! Many thanks!!!! :)

by netman1958

I didn't have any problems accessing the LAN or DMZ over the VPN using their private (internal) IPs. I'm not sure if you are trying to access the servers by their actual private IPs or by their public IPs. Either way, we need to get you configured to access them by their private IPs first, then we can work on any other issues.

This discussion is closed to new replies.