connection timed out for inbound connections

[spazmahoney]

I've been getting connection timed out when trying to access an internal web server from the outside. can anyone help?

 

[themut]

Sure but you do not give us any information in order to help you out. Try to look at the FAQ on how to post your configuration safely, a network layout will also help.

 

[spazmahoney]

I have a single subnet connected to the internet via cable modem. The outside Ip address is dynamically assigned. When I use access-list 101 permit tcp any any eq

http://www (or

ftp with a static statement for that) it seems as if the pix is letting the traffic in, but I get a connection timed out error (for both services)without the actual web page or ftp site displaying in the browser (sh access-list 101 shows some hitcnts. When I use access-list 101 permit tcp xxx.xxx.xxx.xxx eq

http://www (xxx

= actual ip dynamically assigned) I get page cannot be displayed.

Here's my conf. Any advice on the correct access-list statement for outside dhcp assigned ip and the troubles I am having would be greatly appreciated. THANKS!


PIX Version 6.2(2)
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password
passwd xxxxxxxxxxxxxxxxxxxxxxxxxxxx
hostname pixfirewall
domain-name lab.org
fixup protocol ftp 21
fixup protocol http 80
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol ils 389
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol sip 5060
fixup protocol skinny 2000
names
access-list 101 permit tcp any host xxx.xxx.xxx.xxx eq

http://www (xxx

= actual ip dynamically assigned)
pager lines 24
interface ethernet0 10baset
interface ethernet1 10full
mtu outside 1500
mtu inside 1500
ip address outside dhcp setroute
ip address inside 192.168.1.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm location xxx.xxx.xxx.xxx 255.255.255.255 inside
pdm location xxx.xxx.xxx.xxx 255.255.255.255 inside
pdm location xxx.xxx.xxx.xxx 255.255.255.255 inside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 192.168.1.0 255.255.255.0 0 0
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
static (inside,outside) tcp interface

http://www 192.168.1.10

http://www netmask

255.255.25
5.255 0 0
access-group 101 in interface outside
timeout xlate 0:05: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
aaa-server LOCAL protocol local
aaa authorization command LOCAL
http server enable
http 192.168.1.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
dhcpd address 192.168.1.20-192.168.1.30 inside
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
privilege show level 0 command version
privilege show level 0 command curpriv
privilege show level 3 command pdm
privilege show level 3 command blocks
privilege show level 3 command ssh
privilege configure level 3 command who
privilege show level 3 command isakmp
privilege show level 3 command ipsec
privilege show level 3 command vpdn
privilege show level 3 command local-host
privilege show level 3 command interface
privilege show level 3 command ip
privilege configure level 3 command ping
privilege configure level 5 mode enable command configure
privilege show level 5 command running-config
privilege show level 5 command privilege
privilege show level 5 command clock
privilege show level 5 command ntp
terminal width 80
Cryptochecksum:xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
: end

 

[themut]

You need to upgrade your PIX to 6.3(3) and configure the following statements:

static (inside,outside) tcp interface 80 192.168.1.10 80 netmask 255.255.255.255

and use the keywords "interface outside" instead of its IP address on the ACL 101.

 

[spazmahoney]

I take it that this is a problem with the pix 6.2(2).
thanks for the advice. In order to upgrade, do I have to buy a Smartnet warranty. If so, am I able to get that from any vendor that sells Cisco devices. I was overcharged by the company I bought the pix from (both for the unit's advertised price and the stated shipping costs) and I vowed I would never do business with PCMall.com again!

 

[themut]

6.2(2) does not have the ability to use the keywords interface outside on an ACL but if you know the IP address it should work by IP address. It is not required to upgrade the PIX to make it work. 6.3 has the feature mentioned above so it makes it easier to work. If you want to buy a smarnet contract then you can get it from a Cisco distributor or reseller I think you can also buy it online from Cisco. The good part about a smarnet contract is you get all the new images for PIX, routers, switches, VPN clients, etc and you also gain access to TAC.

 

[spazmahoney]

Thanks forthe advice and taking the time to help me with my problem.