Also, Outside_In should probably be outside_in to stay consistent. I can't remember if case matters. It's been a while since I've worked on a PIX fw
Main Topics
Browse All TopicsI have a pix 501 that this morning I took out the following lines
access-list outside_in permit tcp any host 67.139.220.197 eq 3389
access-list outside_in permit tcp any host 67.139.220.196 eq 3389
access-list outside_in permit tcp host 207.97.230.54 host 67.139.220.196 eq smtp
access-list Outside_In permit tcp host 207.97.230.54 host 67.139.220.196 eq smtp
After taking out these lines I can no longer access the internet or ping the gateway of 67.139.220.193. I tried to put the lines back in but no luck. Anyone help would be great.
**** NOTE*****
the interface Ethernet0 is showing up up but NO traffic
PIX Version 6.2(2)
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password ac1X4xzZOr2zxD3d encrypted
passwd ac1X4xzZOr2zxD3d encrypted
hostname path-spec
domain-name ps.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 125 permit icmp any any
access-list 125 permit tcp any host 67.139.220.197 eq 3389
access-list 125 permit tcp any host 67.139.220.196 eq 3389
access-list 125 permit tcp any host 67.139.220.196 eq smtp
access-list 125 permit tcp host 207.97.230.54 host 67.139.220.196 eq smtp
access-list 100 permit ip 192.168.6.0 255.255.255.0 130.94.124.0 255.255.255.192
access-list 101 permit ip 192.168.6.0 255.255.255.0 130.94.124.0 255.255.255.192
access-list outside_in permit tcp any host 67.139.220.197 eq 3389
access-list outside_in permit tcp any host 67.139.220.196 eq 3389
access-list outside_in permit tcp host 207.97.230.54 host 67.139.220.196 eq smtp
access-list Outside_In permit tcp host 207.97.230.54 host 67.139.220.196 eq smtp
pager lines 24
logging on
logging console alerts
logging history alerts
interface ethernet0 10baset
interface ethernet1 10full
mtu outside 1500
mtu inside 1500
ip address outside 67.139.220.194 255.255.255.248
ip address inside 192.168.6.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool clinetvpn 172.19.1.1-172.19.1.4
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 67.139.220.195
nat (inside) 0 access-list 100
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
static (inside,outside) tcp 67.139.220.197 3389 192.168.6.100 3389 netmask 255.2
55.255.255 0 0
static (inside,outside) tcp 67.139.220.196 smtp 192.168.6.252 smtp netmask 255.2
55.255.255 0 0
static (inside,outside) tcp 67.139.220.196 3389 192.168.6.252 3389 netmask 255.2
55.255.255 0 0
route outside 0.0.0.0 0.0.0.0 67.139.220.193 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.6.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
sysopt connection permit-ipsec
no sysopt route dnat
crypto ipsec transform-set pathspec esp-3des esp-md5-hmac
crypto map pathmap 10 ipsec-isakmp
crypto map pathmap 10 set peer 130.94.121.60
crypto map pathmap 10 set transform-set pathspec
crypto map pathmap interface outside
isakmp enable outside
isakmp key ******** address 130.94.121.60 netmask 255.255.255.255 no-xauth no-co
nfig-mode
isakmp identity address
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption 3des
isakmp policy 10 hash md5
isakmp policy 10 group 1
isakmp policy 10 lifetime 86400
vpngroup remtevphgrp address-pool clinetvpn
vpngroup remtevphgrp dns-server 192.168.6.100
vpngroup remtevphgrp idle-time 1800
telnet 192.168.6.0 255.255.255.0 inside
telnet timeout 60
ssh timeout 60
terminal width 80
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.
- you have no access-group commands applying the ACLs?
Add the following
no access-list 101 permit ip 192.168.6.0 255.255.255.0 130.94.124.0 255.255.255.192
access-list
access-group 100 in interface inside
access-group 125 in interface outside
then get rid of these
no access-list outside_in permit tcp any host 67.139.220.197 eq 3389
no access-list outside_in permit tcp any host 67.139.220.196 eq 3389
no access-list outside_in permit tcp host 207.97.230.54 host 67.139.220.196 eq smtp
no access-list Outside_In permit tcp host 207.97.230.54 host 67.139.220.196 eq smtp
that should do you :)
The assumption is that you created the following two ACLS for VPN:
access-list 100 permit ip 192.168.6.0 255.255.255.0 130.94.124.0 255.255.255.192
access-list 101 permit ip 192.168.6.0 255.255.255.0 130.94.124.0 255.255.255.192
These ACLS are only permitting traffic from 192.168.6.0 to 130.94.124.0/26. This would severely limit your access on the internet, not sure you really want to do that.
This ACL below is used to allow traffic in from the internet into your firewall on the outside interface.
access-list 125 permit icmp any any
access-list 125 permit tcp any host 67.139.220.197 eq 3389
access-list 125 permit tcp any host 67.139.220.196 eq 3389
access-list 125 permit tcp any host 67.139.220.196 eq smtp
access-list 125 permit tcp host 207.97.230.54 host 67.139.220.196 eq smtp
This correlates to your Static translations and should be fine if you apply it to the outside interface.
Made the changes as suggested. here is the running config now.
path-spec# sh run
: Saved
:
PIX Version 6.2(2)
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password ac1X4xzZOr2zxD3d encrypted
passwd ac1X4xzZOr2zxD3d encrypted
hostname path-spec
domain-name ps.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 125 permit icmp any any
access-list 125 permit tcp any host 67.139.220.197 eq 3389
access-list 125 permit tcp any host 67.139.220.196 eq 3389
access-list 125 permit tcp any host 67.139.220.196 eq smtp
access-list 125 permit tcp host 207.97.230.54 host 67.139.220.196 eq smtp
access-list 100 permit ip 192.168.6.0 255.255.255.0 130.94.124.0 255.255.255.192
access-list 100 permit ip any any
pager lines 24
logging on
logging console alerts
logging history alerts
interface ethernet0 10baset
interface ethernet1 10full
mtu outside 1500
mtu inside 1500
ip address outside 67.139.220.194 255.255.255.248
ip address inside 192.168.6.1 255.255.255.0
ip audit info action alarm
ip audit attack action alarm
ip local pool clinetvpn 172.19.1.1-172.19.1.4
pdm logging informational 100
pdm history enable
arp timeout 14400
global (outside) 1 67.139.220.195
nat (inside) 0 access-list 100
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
static (inside,outside) tcp 67.139.220.197 3389 192.168.6.100 3389 netmask 255.255.255.255 0 0
static (inside,outside) tcp 67.139.220.196 smtp 192.168.6.252 smtp netmask 255.255.255.255 0 0
static (inside,outside) tcp 67.139.220.196 3389 192.168.6.252 3389 netmask 255.255.255.255 0 0
access-group 125 in interface outside
access-group 100 in interface inside
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 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.6.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
sysopt connection permit-ipsec
no sysopt route dnat
crypto ipsec transform-set pathspec esp-3des esp-md5-hmac
crypto map pathmap 10 ipsec-isakmp
crypto map pathmap 10 set peer 130.94.121.60
crypto map pathmap 10 set transform-set pathspec
crypto map pathmap interface outside
isakmp enable outside
isakmp key ******** address 130.94.121.60 netmask 255.255.255.255 no-xauth no-config-mode
isakmp identity address
isakmp policy 10 authentication pre-share
isakmp policy 10 encryption 3des
isakmp policy 10 hash md5
isakmp policy 10 group 1
isakmp policy 10 lifetime 86400
vpngroup remtevphgrp address-pool clinetvpn
vpngroup remtevphgrp dns-server 192.168.6.100
vpngroup remtevphgrp idle-time 1800
telnet 192.168.6.0 255.255.255.0 inside
telnet timeout 60
ssh timeout 60
terminal width 80
Cryptochecksum:03ba1dbc624
: end
path-spec#
path-spec# sho int
interface ethernet0 "outside" is up, line protocol is up
Hardware is i82559 ethernet, address is 000c.8549.8d5b
IP address 67.139.220.194, subnet mask 255.255.255.248
MTU 1500 bytes, BW 10000 Kbit half duplex
1 packets input, 60 bytes, 0 no buffer
Received 1 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collisions, 0 deferred
0 lost carrier, 0 no carrier
input queue (curr/max blocks): hardware (128/128) software (0/1)
output queue (curr/max blocks): hardware (0/0) software (0/0)
interface ethernet1 "inside" is up, line protocol is up
Hardware is i82559 ethernet, address is 000c.8549.8d5c
IP address 192.168.6.1, subnet mask 255.255.255.0
MTU 1500 bytes, BW 10000 Kbit full duplex
254 packets input, 18143 bytes, 0 no buffer
Received 48 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
152 packets output, 9349 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collisions, 0 deferred
0 lost carrier, 0 no carrier
input queue (curr/max blocks): hardware (128/128) software (0/2)
output queue (curr/max blocks): hardware (1/2) software (0/1)
path-spec#
path-spec# sh access-list
access-list 125; 5 elements
access-list 125 permit icmp any any (hitcnt=0)
access-list 125 permit tcp any host 67.139.220.197 eq 3389 (hitcnt=0)
access-list 125 permit tcp any host 67.139.220.196 eq 3389 (hitcnt=0)
access-list 125 permit tcp any host 67.139.220.196 eq smtp (hitcnt=0)
access-list 125 permit tcp host 207.97.230.54 host 67.139.220.196 eq smtp (hitcnt=0)
access-list 100; 2 elements
access-list 100 permit ip 192.168.6.0 255.255.255.0 130.94.124.0 255.255.255.192 (hitcnt=0)
access-list 100 permit ip any any (hitcnt=74)
path-spec# sh xlate
0 in use, 0 most used
Not sure if you are up and running now. If not be aware that in the running config above, the lines that provide outbound Internet access such as browsing are simply...
global (outside) 1 67.139.220.195
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
If still not working try this.
no access-group 100 in interface inside
Access list 100 is used for NOT natting VPN traffic and for choosing to encrypt it. But in your running configuration it also prevents any outbound traffic except that going to subnet 130.94.124.0 255.255.255.192
And to fix your VPN you'll need this....
crypto map pathmap match address 100
By the way in access-list 100 130.94.124.0 255.255.255.192 is the remote VPN subnet. Is that correct?
Please take access-group 100 off of inside interface. This is restricting your traffic as it arrives at your inside interface to only allow 192.168.6.0 traffic destined towards 130.94.124.0. Not sure why it was suggested that you apply that.
Okay, so you are not making any translations from the inside to outside. Do me a favor and ping from the Pix to the outside with this command "ping outside 4.2.2.2" and let me know status
I am diving the points between everyone for assisting me on this. While everyone contributed to the configuration issues, the actual fix was not even suspected by me. After an exhausting day stated at 3am and lasted until 9pm I replaced the Pix 501 with an ASA. This ASA took an hour to get up and running. However the actual cause of this problem was the Ethernet0 port itself is bad.
Thanks Again for everyones prompt responses in assisting me.
Business Accounts
Answer for Membership
by: themrrobertPosted on 2009-10-15 at 13:11:27ID: 25584342
Have you restarted the PIX firewall?