No, you will not have to reenter your configuration. However, like the above poster mentions it would be a good idea to have a current copy of the running configuration.
It would be helpful to see your config. Absent that, here are some suggestions:
If your PIX isn't heavily loaded with connections turn debuggin on and watch the messages for errors i.e. denied packets etc
VPN will not work through PIX OS < 6.3 without an available NAT address -NOT- a PAT...
The error is because the PIX can't find a valid remote image. Make sure when you download from Cisco the image remains as a '.bin' file extension and that you have the correct path that that .bin file setup on your tftp server.
pdm v1.1 is not compatible with pix os 6.31. To upgrade PDM you...
I wouldn't put 6.3 into production use without first testing it. While I run it at home on my 501 without any problems, I did find that the production 515R at work had all kinds of unusal problems. I had to downgrade to 6.2.
This would require the IAS server which is speaking RADIUS to pass certain RADIUS attributes to the Cisco PIX which it does not support. In short you cannot limit ports, per user via IAS. You can however, limit access to your internal network on a system wide basis via a VPN access list...
>> If you're going to use MS VPN protocols, and you have a W2K server that you're going to use as part of it, then you can consider using the MS W2K server as the VPN tunnel endpoint (RRAS VPN server) instead of the pix.
If you already have a PIX firewall then whats the point of using a...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.