Pix 506 E - Major Issues

[vtgman]

I am not sure what the problem is. When I try the inside,outside command my server stops going to the internet and does not ping out either. Then I tried the
outside, inside command and then all clients could get to the Internet but mail stopped. What am I missing?

Below is the config.

Thanks,

PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 auto
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password dfpDMlUUFcv/E6Bu encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
hostname VTGPIX
domain-name cisco.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
no fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names
access-list letin1 permit icmp any any echo
access-list letin1 permit icmp any any echo-reply
access-list letin1 permit icmp any any traceroute
access-list letin1 permit icmp any any time-exceeded
access-list letin1 permit tcp any host XX.XXX.XX.135 eq smtp
access-list letin1 permit tcp any host xx.xxx.xx.135 eq pop3
access-list letin1 permit tcp any host xx.xxx.xx.135 eq www
access-list letin1 permit tcp any host xx.xxx.xx.135 eq 3389
access-list letin1 permit tcp any host xx.xxx.xx.135 eq 3389
access-list letout permit ip any any
pager lines 24
mtu outside 1500
mtu inside 1500
ip address outside xx.xxx.xx.134 255.255.255.192
ip address inside 192.168.2.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
static (outside,inside) xx.xxx.xx.135 192.168.2.5 netmask 255.255.255.255 0 0
access-group letin1 in interface outside
access-group letout in interface inside
route outside 0.0.0.0 0.0.0.0 xx.xxx.xx.129 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
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
terminal width 80

 

[Supergrrover]

Change this - global (outside) 1 interface
to
global (outside) 1 xx.xx.xx.134
You should only use "interface" if the external IP is assigned by DHCP and not static.
and then for your static -
static (inside,outside) xx.xx.xx.135 192.168.2.5 netmask 255.255.255.255


Brent
Systems Engineer / Consultant
CCNP, CCSP

 

[vtgman]

When I do the above this is what I get
ERROR: XX.XXX.XX.134-XX.XXX.XX.134 overlaps with outside interface address

 

[vtgman]

I did get the above to work but the server can not go out to the internet or ping the firewall. All the other PCs in my network can ping the firewall and internet.

 

[Supergrrover]

Can you confirm your IP and subnetmask that you were given from your ISP? (don't post it, just XX out the first 3 octets and leave the full subnet mask.)

You can try just using policy NAT instead of a full static

static (inside,outside) tcp xx.xx.xx.135 3389 192.168.2.5 netmask 255.255.255.255
static (inside,outside) tcp xx.xx.xx.135 25 192.168.2.5 netmask 255.255.255.255
static (inside,outside) tcp xx.xx.xx.135 110 192.168.2.5 netmask 255.255.255.255
static (inside,outside) tcp xx.xx.xx.135 80 192.168.2.5 netmask 255.255.255.255
static (inside,outside) tcp xx.xx.xx.135 443 192.168.2.5 netmask 255.255.255.255


Brent
Systems Engineer / Consultant
CCNP, CCSP

 

[vtgman]

Here is the IP information from the ISP
XX.XXX.XX.134 255.255.255.192

Also did the above with the same issue. I used the following sh command sh xlate and 192.168.2.5 is translating to .134 and not .135.

I also talked to Cisco for 3 hours and they could not fix the issue.