Perfect, thanks, lrmoore.
I'll wrestle some more with the PDM 3.0 failure to load.
RG
Main Topics
Browse All TopicsApologies if this is so basic.
I'm not able to route from the inside interface to the outside after restting a 506e to default factory configuration and making a few minor customizations. It never worked with the factory defaults and I've now exhausted my little knowledge of how to reconfigure this properly.
I set the outside interface with an address on my local (working) subnet 10.100.100.0 and plugged it into Interface0. I've confirmed the outside interface of the PIX is indeed pingable from my active production subnet.
I set the inside interface to provide DHCP in the 172.18.16.x range and added things like DNS and WINS that exist on my production subnet. I've confirmed when I plug my laptop into Interface1 it gets a valid IP address from the PIX in the correct range; also correct are the DNS and WINS addresses. So DHCP works. And I can ping the PIX inside address.
So both sides work, but they don't apparently talk to each other. However, any attempt to access anything on my 10.100.100.0 subnet fails. It just times out.
Another clue, perhaps unrelated: On the laptop (connected to the inside interface) I can browse to https://172.18.16.1 and, in fact, get a website security certificate error. I click on "Continue to this website" and get prompted for the User name and Password which I enter as blank (first time). I get the PDM 3.0 spalsh screen and allow pop-ups always. I go to the new "popped up" browser window and it says "Loading PIX Device Manager. Please wait ..." That's as far as it ever gets.
This PIX was working perfectly on another production subnet before I reset it to its factory defaults. So I suspect it's my lack of knowledge and not something inherently broken with the device.
I've copied the configuration below.
Thanks very much.
RG
PIX Version 6.3(3)
interface ethernet0 auto
interface ethernet1 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password 8Ry2YjIyt7RRXU24 encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname pixfirewall
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside 10.100.100.5 255.255.255.0
ip address inside 172.18.16.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
route outside 0.0.0.0 0.0.0.0 172.18.16.1 1
timeout xlate 0:05:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 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
http server enable
http 172.18.16.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
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd address 172.18.16.100-172.18.16.19
dhcpd dns 10.100.100.3
dhcpd wins 10.100.100.3
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd enable inside
terminal width 80
Cryptochecksum:3f4e069b93d
: end
pixfirewall(config)#
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Business Accounts
Answer for Membership
by: lrmoorePosted on 2007-01-07 at 11:31:25ID: 18262803
>route outside 0.0.0.0 0.0.0.0 172.18.16.1 1
You can't use this because your outside is 10.something
Remove it with
no route outside 0.0.0.0 0.0.0.0 172.18.16.1 1
Replace it with
route outside 0.0.0.0 0.0.0.0 10.100.100.x <== where 'x' is a router on your network, or the existing default gateway of a host on the 10.100.100.x network, or really any ip in the 10.100.100.0 subnet, it doesn't matter if all you want to do is reach hosts on the 10.100.100.0 subnet
Add this for pinging/testing
access-list permit_icmp permit icmp any any
access-group permit_icmp in interface outside