PIX 501 Config

[rmeder]

I have tried to read through everything on here to come up with the answer on my own, but I have not been sucessfull to this point. This is my first Cisco firewall that I have configured, and I'm running into an issue. I have created what I believe to be the proper access lists and static routes, but I have not been able to enable inbound traffic to my SBS server which is our mail & web server.
Here is my current config:

: Saved
: Written by enable_15 at 15:52:57.602 UTC Fri Jul 18 2003
PIX Version 6.2(2)
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password 8Ry2YjIyt7RRXU24 encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname pixfirewall
domain-name private.com
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 100 permit icmp any any echo-reply
access-list 100 permit icmp any any time-exceeded
access-list 100 permit icmp any any unreachable
access-list 100 permit tcp any host 111.77.0.26 eq www
access-list 100 permit tcp any host 111.77.0.26 eq smtp
access-list 101 permit tcp any host 111.77.0.26 eq www
access-list 101 permit tcp any host 111.77.0.26 eq smtp
access-list 101 permit tcp any host 111.77.0.26 eq pop3
pager lines 24
interface ethernet0 10baset
interface ethernet1 10full
mtu outside 1500
mtu inside 1500
ip address outside 111.77.0.26 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 location 192.168.1.10 255.255.255.255 inside
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 interface
global (outside) 1 111.77.0.27
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
static (inside,outside) 111.77.0.26 192.168.1.10 netmask 255.255.255.255 0 0
access-group 100 in interface outside
route outside 0.0.0.0 0.0.0.0 192.168.2.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 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
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 192.168.1.10 255.255.255.255 inside
telnet timeout 5
ssh timeout 5
dhcpd address 192.168.1.2-192.168.1.129 inside
dhcpd lease 3600
dhcpd ping_timeout 750
dhcpd auto_config outside
terminal width 80
Cryptochecksum:49dcbb4820657b3a993aff9f919f7fc1

I'm sure it is something simple that I have missed.

Thanks for any help.

Rick

 

[rmeder]

Any suggestions??? Please help!

 

[yizhar]

HI.

> ip address outside 111.77.0.26 255.255.255.248
> static (inside,outside) 111.77.0.26 192.168.1.10
This is wrong (conflict).
You have a pool of several registered ip addresses, so you can use one address for the pix interface, and a different address for "static" to the SBS server.

> but I have not been able to enable inbound traffic to my SBS server
What about outbound traffic?
Can you ping/telnet/http from the SBS server to an external host?
Can you ping/telnet/http from a workstation to an external host?

> route outside 0.0.0.0 0.0.0.0 192.168.2.1
This seems to be part of the problem...

You can erase the configuration, and start again using PDM - the wizard will help you eliminate some newbie errors and will guide you with the initial (and future) configuration.

Then, one of the initial steps is to start using syslog messages so you have better communication between yourself and that strange machine - without syslog you only tell the pix what to do, but with syslog messages you can see what the pix thinks about your commands and better understand what it is actualy doing.


Yizhar Hurwitz

http://come.to/yizhar

http://teachers.sivan.co.il/yizhar

 

[FCCC]

you have to add on your access-list permit ip any any. hope this helps.