I can ping my other subnet

venkatadrich

PIX Version 6.3(3)
interface ethernet0 auto
interface ethernet1 auto
interface ethernet2 auto shutdown
nameif ethernet0 outside security0
nameif ethernet1 inside security100
nameif ethernet2 intf2 security4
hostname backuppix
domain-name butler.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
pager lines 24
mtu outside 1500
mtu inside 1500
mtu intf2 1500
ip address outside 203.187.127.194 255.255.255.224
ip address inside 192.168.141.19 255.255.255.0
no ip address intf2
ip audit info action alarm
ip audit attack action alarm
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 192.168.141.0 255.255.255.0 0 0
route outside 0.0.0.0 0.0.0.0 203.187.137.193 1
route inside 192.168.1.0 255.255.255.0 192.168.141.1 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 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.141.12 255.255.255.255 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
telnet 192.168.141.0 255.255.255.0 inside
telnet timeout 5
ssh timeout 5
console timeout 0
dhcpd dns 195.206.66.146
terminal width 80
Cryptochecksum:309d07d510457555fa6488b5c5c2f4e0
: end




with the abouve configuration , I could ping the 192.168.1.0 subnet from the pix console , but from the pc i could not ping the 192.168.1.0...... Please help why i cant ping the other subnet only from the p.c

garv221

this pix looks like the gateway. What device separates or is the other subnet connected to?

forbesl

The PIX is a solid brick until you "poke some holes" in it. You need to configure either access-lists or conduits on the device.

Cisco PIX Firewall and VPN Configuration Guide, Version 6.3

garv221

forbesl wrote:

The PIX is a solid brick until you "poke some holes" in it. You need to configure either access-lists or conduits on the device.

Cisco PIX Firewall and VPN Configuration Guide, Version 6.3

True. Out of the box most restrictive

forbesl

I didn't notice any access-list or conduits in his config. Looks like he just turned the interfaces on, slapped some IP addresses on them and went to town! Only the town was closed....:)