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.
Quite a strange problem and also intermittent. One particular VPN in crypto map list keeps picking up the wrong remote peer to the one configured in the crypto map, sometimes this can be an invalid peer address, such as 50.0.0.0. This is currently ha...
Hi for some reason TACACS+ authentication has stopped working (it works on all other devices on the network) so trying to do a password recovery on a PIX 535 running 6.3(4). Seem to fail on the first hurdle in that in will not accept the first comman...
Hi for some reason TACACS+ authentication has stopped working (it works on all other devices on the network) so trying to do a password recovery on a PIX 535 running 6.3(4). Seem to fail on the first hurdle in that in will not accept the first comman...
I have just rebooted the PIX and as you can see below the correct peer information is there and the file transfer is now working.local ident (addr/mask/prot/port): (AXA_ftpap001/255.255.255.255/6/0) remote ident (addr/mask/prot/port): (192.168.1.1...
Solution to this is there is no solution! If the PIX only has a 4 port ethernet card in it you cannot perform a password recovery. The only solution is to install at leat one single port ethernet card, then do the password recovery.
Hi - normally the cusomer lets us know that it has stopped working and issueing the command "sh crypto ipsec sa" confirms that the peer is 50.0.0.0(local ident (addr/mask/prot/port): AXA_ftpap001/255.255.255.255/0/0) remote ident (addr/mask/prot/p...
