Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations bkrike on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Cannot access WWW Server in DMZ

Status
Not open for further replies.

accconst

IS-IT--Management
Oct 4, 2003
33
US
I'm running a Cisco PIX 515E with three interfaces, one connected to the internet, one to my internal network, and on to a dmz w/ a
I'm not able to access my web server from a host on the public (outside) network.

I have configured a static address translation from a public address on the outside interface to a private address (the on the dmz interface.

I have setup an ACL permitting all ip traffic to the web server and applied it to the outside interface.

I can access the internet from the webserver and web-based IP Address reporting tools display the correct translated public address (216.105.166.116). Also, web-based port scanning tools do detect several open ports (including 80) on this address. (I ran the test again with the ACL disable and that time it reported no open ports). Also, I am able to acces the webserver from other hosts on the dmz.

Below is my configuration. Is there anything that I'm doing wrong or anything that I've missed? Thanks for your help.

PIX Version 6.1(4)
nameif ethernet0 outside security0
nameif ethernet1 inside security100
nameif ethernet2 dmz security50
enable password GpCqPA0Ds/rdSxBT encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname pixfirewall
domain-name allegrone.local
fixup protocol ftp 21
fixup protocol h323 1720
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol sip 5060
fixup protocol skinny 2000
fixup protocol http 80
names
access-list outside permit tcp any host 216.105.166.116
pager lines 24
interface ethernet0 auto
interface ethernet1 auto
interface ethernet2 auto
mtu outside 1500
mtu inside 1500
mtu dmz 1500
ip address outside 216.105.166.118 255.255.255.248
ip address inside 192.168.0.1 255.255.255.0
ip address dmz 10.0.0.1 255.0.0.0
ip audit info action alarm
ip audit attack action alarm
pdm history enable
arp timeout 14400
static (dmz,outside) 216.105.166.116 10.0.0.11 netmask 255.255.255.255 0 0
access-group outside in interface outside
route outside 0.0.0.0 0.0.0.0 216.105.166.113 1
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h323 0:05:00 si
p 0:30:00 sip_media 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.0.207 255.255.255.255 inside
http 192.168.0.0 255.255.255.0 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
no sysopt route dnat
telnet timeout 5
ssh timeout 5
terminal width 80
 
HI.

> access-list outside permit tcp any host 216.105.166.116
This line opens ALL tcp ports which is not a good idea.
You should change it to:
access-list outside permit tcp any host 216.105.166.116 eq 80

Other then that - you should troubleshoot on all devices:
Check router configuration and try to reboot it.
Check web server configuration and logs.

Use syslog messages at level 6 to see what exactly is going on.




Yizhar Hurwitz
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top