Search results for query: *

Anyone konw if this is a configuration eorror or a PIX bug. We are trying to get SIP messages in and out the firewall. It turns out that it is indeed a PIX problem. All of the Vias have IP addresses before the PIX. After the PIX they are all stripped out. The PIX should probably strip the...

Thank you...... I am suspecting that it is a hardware problem as well. But I have never set up a syslog server. Where can I find out how to do that?

Sorry I thought I had mentioned that: The version that I am running is: PIX Version 6.2(1) And there is a fixup like for SIP: fixup protocol sip 5060 I went to CISCO and downloaded the latest version I believe.

I am doing Voice over IP using SIP PINGTEL Xpressa phones. I have a bunch of phone inside the firewall and a bunch of them outside the firewall on the public net. Call from outside to host inside works fine, call gets set up and torn down correctly. But if call originates from NATed PIX...

Actually i found out the cause of it, but does anyone know why it is happening? I have a PIX 515 firewall running Version 6.2(1). I have been working on some issues and found out what the core problem was. It seems randomly the PIX restart itself. I have been monitoring using a serial...

I have a conduit open to a SSH port to a host inside the PIX network. For some reason now if i have a connection to a host behind the PIX firewall using SSH or telnet i get kicked off after a minute or two. I am able to reconnect with no problem but it does not seem to hold the connection. What...

I was able to use the Alias feature and get it to work.

If there is no way of doing it i will just have to change the network topolgoy. I need the machine to be accessed by external and internal hosts. Is there any other solution?

I have a machine on the network with an IP address of 10.1.1.3. On the same networking 10.1.1.xxx I have a bunch of hosts as well on the same network. On the PIX I have defined the following static (inside,outside) 65.220.123.120 10.1.1.3 netmask 255.255.255.255 0 0 conduit permit tcp...

Actually forget my last inquiry cause i found the info on the DOC you guys gave me... thanks again for your help...

YES you are right ... that seems to have solved the problem.. Thank you so much... i knew it was something simple... But i thought the PIX can use one public address for an many internal clients as need.. is there a way to map many to one instead of one to one relation?

Hello: Here are the answers to your questions below: Q. What is the pix version? A.PIX Version 6.2(1) Q. Are you using NAT, PAT or combination? A. nat (inside) 1 10.1.0.0 255.255.0.0 0 0 Q. Post here your "global" statements A. global (outside) 1 65.220.123.60-65.220.123.69 global...

It also seems like the PIX is selective in what IP it lets out. At one time 10.1.20.150 can talk to anywhere in the world and any other network. But at the same time ip 10.1.20.182 cant see the public world.

I think I have a pretty good idea of the culprit in the "poison IP address" mystery. I followed some packets through our network and learned that for some reason, some packets are simply ignored (or discarded) by the PIX firewall. The PIX is supposed to be the default gateway between...