Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
I just noticed recently that after I upgraded the PIX to 6.3(3) and I reboot 2 of my Windows 2000 servers, it brings my network to its knees and the switches go nuts with syslog messages saying unreachable from my server ip to the pix inside ip only ...
I am currently running a Cisco 2620 with 40MB RAMVersion 12.1(20)It is basically just doing routing for a T-1 through a serial interface via Frame Relay. No firewall inspect features or ipsec features are being utilized because it connects to a pix. ...
Is it possible to log unwanted traffic destined for the outside interface to be logged? Such as port scans and non IDS traffic. Denied tcp/udp traffic. For example: A Cisco PIX 501 with a DHCP assigned outside interface. Is it possible to log denied ...
They are both the syslog servers.The switch the servers plug into is a 3548. What's the best way to go about this. I never really noticed this in the past as I had syslog running on only one and it hardly ever got rebooted.
The packet capture thinks its rsh but its the pix sending syslog udp messages to my two syslog servers when this udp broadcast storm starts from my servers. It must be doing something to the pix inside interface that constitutes it from kicking out t...
All that did was block inside traffic from going out, logging 106023's. I want 106023's to log when someone is scanning my outside ip for that fact, my only ip. I changed the 710005 to a warning level which does essentially what I want logging denied...
