<div>
It's probably blocking the ICMP protocol used by PING and TRACERT. If you enable that in the PIX, you should be able to ping it.
</div>


It's probably blocking the ICMP protocol used by PING and TRACERT. If you enable that in the PIX, you should be able to ping it.

<div>
D'OH! I just noticed you said you can ping the internet... :)<br />
<br />
I checked and it looks like it's a limitation of NAT - the external interface can't respond to a request from it's own internal interface.
</div>


D'OH! I just noticed you said you can ping the internet... :)

I checked and it looks like it's a limitation of NAT - the external interface can't respond to a request from it's own internal interface.

<div>
Thanks uter,<br />
<br />
Yes, I do have ICMP rules. I just want to be sure that it's normal and not something in the way I've configured PIX. Where did you get the info from?<br />
<br />
I can ping both interfaces from the PIX (ie - in a telnet session.)<br />
<br />
<br />
Ciderspine
</div>


Thanks uter,

Yes, I do have ICMP rules. I just want to be sure that it's normal and not something in the way I've configured PIX. Where did you get the info from?

I can ping both interfaces from the PIX (ie - in a telnet session.)


Ciderspine

<div>
<div class="content wysiwyg-content">
Hi experts,<br />
<br />
An easy one here:<br />
<br />
I get no respose from my PIX's external interface when I ping it from the internal network - I can however ping the internet from the internal network . Is this normal behaviour of PIX - is it a limitation of NAT or is something up with my PIX?<br />
<br />
Ciderspine<br />

</div>
</div>


Hi experts,

An easy one here:

I get no respose from my PIX's external interface when I ping it from the internal network - I can however ping the internet from the internal network . Is this normal behaviour of PIX - is it a limitation of NAT or is something up with my PIX?

Ciderspine


PIX internal to external icmp

Networking software modules are interfaced with a framework implemented on the machine's operating system that implements the networking functionality of the operating system. The best known frameworks are the TCP/IP model and the OSI model. Systems typically do not use a single protocol to handle a transmission. Instead they use a set of cooperating protocols, sometimes called a protocol family or protocol suite.[9] Some of the best known protocol suites include: IPX/SPX, X.25, AX.25, AppleTalk and TCP/IP. Other protocols indirectly related to networking include the hypertext transfer protocol (HTTP) and its related technologies, Dynamic Host Configuration Protocol (DHCP), Domain Name Server (DNS) and other Internet protocols.

Networking Protocols

Networking is the process of connecting computing devices, peripherals and terminals together through a system that uses wiring, cabling or radio waves that enable their users to communicate, share information and interact over distances. Often associated are issues regarding operating systems, hardware and equipment, cloud and virtual networking, protocols, architecture, storage and management.

Networking

Cisco PIX is a dedicated hardware firewall appliance; the Cisco Adaptive Security Appliance (ASA) is a firewall and anti-malware security appliance that provides unified threat management and protection the PIX does not. Other Cisco devices and systems include routers, switches, storage networking, wireless and the software and hardware for PIX Firewall Manager (PFM), PIX Device Manager (PDM) and Adaptive Security Device Manager (ASDM).