Hosts on DMZ interface cannot load web pages - ASA

I have been wracking my brain to make this work and need some peer review.  Hosts that are on the DMZ interface cannot access web pages (internal hosts can).  I have been attempting to do this to an IP address so I doubt DNS is an issue.

This is a very basic set up and is in my lab, so showing IP addresses is not a problem.

What am I missing?
: Saved
ASA Version 7.2(3) 
hostname fw01
domain-name ****.com
enable password ****** encrypted
interface Vlan1
 nameif inside
 security-level 100
 ip address 
interface Vlan2
 nameif outside
 security-level 0
 ip address dhcp setroute 
interface Vlan3
 no forward interface Vlan1
 nameif dmz
 security-level 50
 ip address 
interface Ethernet0/0
 switchport access vlan 2
interface Ethernet0/1
 switchport access vlan 2
interface Ethernet0/2
interface Ethernet0/3
interface Ethernet0/4
interface Ethernet0/5
 switchport access vlan 3
interface Ethernet0/6
 switchport access vlan 3
interface Ethernet0/7
 switchport access vlan 3
passwd ****** encrypted
ftp mode passive
dns server-group DefaultDNS
same-security-traffic permit inter-interface
same-security-traffic permit intra-interface
access-list dmz_access_in extended permit ip any 
access-list no-nat-dmz extended permit ip 
access-list no-nat-dmz extended deny ip any any 
pager lines 24
logging enable
logging buffered informational
logging asdm informational
mtu inside 1500
mtu outside 1500
mtu dmz 1500
icmp unreachable rate-limit 1 burst-size 1
asdm image disk0:/asdm-523.bin
no asdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1
nat (dmz) 0 access-list no-nat-dmz
nat (dmz) 1
nat (dmz) 1
static (dmz,inside) netmask 
access-group dmz_access_in in interface dmz
route outside 1 track 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
http server enable
http inside
http dmz
http inside
no snmp-server location
no snmp-server contact
snmp-server enable traps snmp authentication linkup linkdown coldstart
sla monitor 1
 type echo protocol ipIcmpEcho interface outside
sla monitor schedule 1 life forever start-time now
track 1 rtr 1 reachability
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd auto_config outside
dhcpd address inside
dhcpd enable inside
class-map inspection_default
 match default-inspection-traffic
policy-map type inspect dns preset_dns_map
  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 http 
service-policy global_policy global
prompt hostname context 
: end
asdm image disk0:/asdm-523.bin
no asdm history enable

Open in new window

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Try putting in these commands:

no nat (dmz) 0 access-list no-nat-dmz
clear configure access-list no-nat-dmz
no static (dmz,inside) netmask
no access-group dmz_access_in in interface dmz

The first 3 commands really shouldn't be there in your environment and the last command is only needed if you are going to allow traffic from the dmz to higher security level interface.  The only higher security level interface you have on this firewall is the inside interface on VLAN1, but because you apparently have the base license on this 5505, the command "no forward interface Vlan1" is going to prohibit traffic from the dmz to the inside even if you did want to allow it...your license won't permit traffic from the 3rd VLAN (the dmz) to both of the other VLAN interfaces, just 1 of the other interfaces and you get to decide which of those interfaces to allow.  In this case, you are allowing traffic to go from the dmz to VLAN2 which is the outside.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
markrsullivan1Author Commented:
OK...I'm oficially the biggest idiot on the planet.  First, thank you for your help.  Second...then next time I forget to put a default gateway from my host to the FW, I'm gong to go drink myself into oblivion.

Thanks again.
Drink one for me...;)
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.