cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
894
Views
0
Helpful
5
Replies

Access DMZ Server

nabilbenyoussef
Level 1
Level 1

Hello everyone, i have prolem to access my server in Dmz. there is my config in asa firewall:

 

ciscoasa(config)# sh run
: Saved
:
ASA Version 8.4(2)
!
hostname ciscoasa
enable password 8Ry2YjIyt7RRXU24 encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
names
!
interface GigabitEthernet0
 nameif outside
 security-level 0
 ip address 209.165.200.226 255.255.255.248
!
interface GigabitEthernet1
 nameif dmz
 security-level 50
 ip address 192.168.2.1 255.255.255.0
!
interface GigabitEthernet2
 nameif inside
 security-level 100
 ip address 192.168.1.1 255.255.255.0
!
interface GigabitEthernet3
 shutdown
 no nameif
 no security-level
 no ip address
!
interface GigabitEthernet4
 shutdown
 no nameif
 no security-level
 no ip address
!
interface GigabitEthernet5
 shutdown
 no nameif
 no security-level
 no ip address
!
ftp mode passive
object network lan
 subnet 192.168.1.0 255.255.255.0
object network dmz
 subnet 192.168.2.0 255.255.255.0
object network webserver-external-ip
 host 209.165.200.227
object network webserver
 host 192.168.2.3
access-list outside_DMZ extended permit tcp any object webserver eq www
access-list outside_DMZ extended permit tcp any host 209.165.200.227 eq www
access-list outside_acl extended permit tcp any object webserver eq www
pager lines 24
mtu outside 1500
mtu dmz 1500
mtu inside 1500
icmp unreachable rate-limit 1 burst-size 1
no asdm history enable
arp timeout 14400
!
object network lan
 nat (inside,outside) dynamic interface
object network dmz
 nat (dmz,outside) dynamic interface
object network webserver
 nat (dmz,outside) static webserver-external-ip service tcp www www
access-group outside_acl in interface outside
route outside 0.0.0.0 0.0.0.0 209.165.200.225 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
user-identity default-domain LOCAL
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart warmstart
telnet timeout 5
ssh timeout 5
console timeout 0
threat-detection basic-threat
threat-detection statistics access-list
no threat-detection statistics tcp-intercept
!
!
prompt hostname context
no call-home reporting anonymous
call-home
 profile CiscoTAC-1
  no active
  destination address http https://tools.cisco.com/its/service/oddce/services/DDCEService
  destination address email callhome@cisco.com
  destination transport-method http
  subscribe-to-alert-group diagnostic
  subscribe-to-alert-group environment
  subscribe-to-alert-group inventory periodic monthly
  subscribe-to-alert-group configuration periodic monthly
  subscribe-to-alert-group telemetry periodic daily
crashinfo save disable
Cryptochecksum:a967ebb07ef51aa9d1e827f970848a66
: end
ciscoasa(config)#

please i need help

1 Accepted Solution

Accepted Solutions

 

Hi. I noticed that you are NATing in to the webserver with global IP 209.165.200.227, but you are NATing out of the DMZ to the interface, with the IP 209.165.200.226. Is that perhaps a typo? Because it looks like you are NATing all outgoing requests from the DMZ to a different IP address than the one you are NATing in on. So quite possibly you are responding to requests from .226. This could be why.

 

Test by removing the following from your config

object network dmz
 nat (dmz,outside) dynamic interface

 

 

 

 

 

 

View solution in original post

5 Replies 5

Andre Neethling
Level 4
Level 4

Where are you trying to access your DMZ from? Inside, Outside?

From the outside

 

Hi. I noticed that you are NATing in to the webserver with global IP 209.165.200.227, but you are NATing out of the DMZ to the interface, with the IP 209.165.200.226. Is that perhaps a typo? Because it looks like you are NATing all outgoing requests from the DMZ to a different IP address than the one you are NATing in on. So quite possibly you are responding to requests from .226. This could be why.

 

Test by removing the following from your config

object network dmz
 nat (dmz,outside) dynamic interface

 

 

 

 

 

 

The probleù was resolved thanks a lot Andre

Thanks for confirming.  

regards

Andre

Review Cisco Networking for a $25 gift card