behind pix501 internal machines, cant access mail, web servers also behind pix

we have pix 501 prtotecting web, dns, mail, ftp servers, anyone outside can access the servers, but anyone on the internal machines cannot.

Please help

7/13/2006 2:57PM

Result of firewall command: "show running"

: Saved : PIX Version 6.3(5) interface ethernet0 auto interface ethernet1 100full nameif ethernet0 outside security0 nameif ethernet1 inside security100 enable password xxxxxxxxxxxxxx encrypted passwd xxxxxxxxxxxx encrypted hostname xxxxxxx domain-name ciscopix.com 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 access-list acl_out permit tcp any interface outside eq www access-list acl_out permit tcp host x.x.x.x interface outside eq 3389 access-list acl_out permit tcp host y.y.y.y interface outside eq 3389 access-list acl_out permit tcp host z.z.z.z interface outside eq 3389 access-list acl_out permit tcp any interface outside eq 81 access-list acl_out permit tcp any interface outside eq https access-list acl_out permit tcp any interface outside eq 465 access-list acl_out permit tcp any interface outside eq smtp access-list acl_out permit tcp any interface outside eq pop3 access-list acl_out permit tcp any interface outside eq 995 access-list acl_out permit tcp any interface outside eq imap4 access-list acl_out permit tcp any interface outside eq 993 access-list acl_out permit tcp any interface outside eq 8000 access-list acl_out permit tcp any interface outside eq ftp-data access-list acl_out permit tcp any interface outside eq ftp access-list acl_out permit tcp any interface outside eq 5500 pager lines 24 mtu outside 1500 mtu inside 1500 ip address outside a.a.a.20 255.255.255.224 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.3 255.255.255.255 inside pdm location 192.168.1.7 255.255.255.255 inside pdm location b.b.b.b 255.255.255.255 outside pdm location c.c.c.c 255.255.255.255 outside pdm location d.d.d.d 255.255.255.255 outside pdm location 192.168.1.5 255.255.255.255 inside pdm location 192.168.1.9 255.255.255.255 inside pdm history enable arp timeout 14400 global (outside) 1 e.e.e.e netmask 255.255.255.224 global (outside) 10 interface nat (inside) 10 0.0.0.0 0.0.0.0 0 0 static (inside,outside) tcp 68.x.x.20 www 192.168.1.7 1024 netmask

255.255.255.255 0 0 static (inside,outside) tcp 68.x.x.20 3389 192.168.1.3 3389 netmask 255.255.255.255 0 0 static (inside,outside) tcp 68.x.x.20 81 192.168.1.7 81 netmask 255.255.255.255 0 0 static (inside,outside) tcp 68.x.x.20 https 192.168.1.7 https netmask 255.255.255.255 0 0 static (inside,outside) tcp 68.x.x.20 465 192.168.1.5 465 netmask 255.255.255.255 0 0 static (inside,outside) tcp 68.x.x.20 smtp 192.168.1.5 smtp netmask 255.255.255.255 0 0 static (inside,outside) tcp 68.x.x.20 pop3 192.168.1.5 pop3 netmask 255.255.255.255 0 0 static (inside,outside) tcp 68.x.x.20 995 192.168.1.5 995 netmask 255.255.255.255 0 0 static (inside,outside) tcp 68.x.x.20 imap4 192.168.1.5 imap4 netmask 255.255.255.255 0 0 static (inside,outside) tcp 68.x.x.20 993 192.168.1.5 993 netmask 255.255.255.255 0 0 static (inside,outside) tcp 68.x.x.20 8000 192.168.1.5 8000 netmask 255.255.255.255 0 0 static (inside,outside) tcp 68.x.x.20 ftp-data 192.168.1.7 ftp-data netmask 255.255.255.255 0 0 static (inside,outside) tcp 68.x.x.20 ftp 192.168.1.7 ftp netmask 255.255.255.255 0 0 static (inside,outside) tcp 68.x.x.20 5500 192.168.1.9 5500 netmask 255.255.255.255 0 0 access-group acl_out in interface outside route outside 0.0.0.0 0.0.0.0 f.f.f.f 1 timeout xlate 3:00: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 sip-disconnect 0:02:00 sip-invite 0:03:00 timeout uauth 0:05:00 absolute aaa-server TACACS+ protocol tacacs+ aaa-server TACACS+ max-failed-attempts 3 aaa-server TACACS+ deadtime 10 aaa-server RADIUS protocol radius aaa-server RADIUS max-failed-attempts 3 aaa-server RADIUS deadtime 10 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.25-192.168.1.49 inside dhcpd dns x.x.x.x y.y.y.y dhcpd lease 3600 dhcpd ping_timeout 750 dhcpd domain ddddddd.com dhcpd enable inside terminal width 80 Cryptochecksum:5b9b52ee455daed406d7beedae626d78 : end
Reply to
savage
Loading thread data ...

You only have two interfaces, what exactly is connected to these.. from your question i thougt you would have had the inside network, a dmz (with your servers) and an outside interface (untrusted to the net).

Flamer.

Reply to
die.spam

When you use a PIX, you cannot access internal hosts using the public IP *address*.

The ways to deal with this have been discussed many times. The easiest of them is to access by host *name* and to make changes so that internal hosts resolve the name to the internal IP and external hosts resolve the name to the public IP.

Reply to
Walter Roberson

Cabling-Design.com Forums website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.