trouble with config of Pix 501

Guys,

I'm having severe problems with my Pix 501 config. I've spent 8-9 hours trying to get it to work put no joy. I'm at the stage where i can ping from the pix my internal network and also able to ping out to the internet.

However, nothing on my internal network can get to the outside

I'm having to use the CLI as the Cisco PDM will not work. If i post my config in the morning when i get into work, would someone mind taking a look? It's bound to be something silly like routing/NAT. I'll post the config and some details on my SDSL setup.

Many thanks

Garrett

Garrett,

We'll take a look at your configuration once you've posted it.

Cheers,

Ok,

So below is my Pix config. The setup is as follows. I have a SDSL router that already has one firewall connected to FE1. This Pix is connected to FE2. The ISP has given me the ip address to use, [***.***.***.130]. The gateway is ***.***.***.134, should this be in there somewhere?

Garrett

*****************************************************

PIX Version 6.3(3)
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password ****************** encrypted
passwd ******************encrypted
hostname fuse
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 ***.**.***.130 255.255.255.248
ip address inside 192.168.1.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 ***.***.***.130 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 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
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd address 192.168.1.2-192.168.1.33 inside
dhcpd dns 194.72.6.38 194.72.6.39
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
dhcpd enable inside
terminal width 80
: end

The following line needs to be changed:

route outside 0.0.0.0 0.0.0.0 ***.***.***.130 1


Instead of .130, this should be the Gateway your isp gave you, .134.

then it should work as expected.

Yep, I spotted that earlier today. I'm off site for the next couple of days and i am dying to get this sorted. It may be a qustion for another forum but how could i test this with out loosing my connection to the server on the inside?

I have a server with 2 interfaces, one interface is on my production network giving me access to the console of the firewall, the other interface is connected to the switch that the pix is on. How could i ping from the windows interface that is connected to the pix? And so test the new pix connection?

Garrett