Searching Phoneboy I found this - a well know issue, usually with Nat or memory implications.
Hope it helps, Cheers, Jonathan I see these error messages on my console or NT event viewer: fw: fw_xlate_forw: failed to initalize the connection fw: fw_init_xlation: ld_set forward failed A: These messages appear when FireWall-1 is attempting to perform address translation on a service or protocol where address translation is not supported. Check your FireWall-1 logs to see which service in particular that is causing that error. It will be listed as something that was accepted. SNMP and GRE are common culprits, though anything may cause the error. Sometimes, you will see this error message because you are running out of kernel memory. You will usually see messages to this effect at the same time. This can be fixed by following the steps in the following FAQ: halloc: memory exhausted Some sites have reported that a trojan horse on their network that appears to do a portscan to specific sites. This trojan is documented at http://www.cert.org/advisories/CA-1999-02.html. If this trojan horse has been installed on a machine behind your network and that machine is subject to HIDE-mode translation, it is possible that it will cause this error message to occur over and over on your firewall and prevent legitimate users from initiating connections through the firewall. Another way to achieve the same effect is to use a port scanning program through the firewall from a host subject to HIDE-mode NAT. You might also see this problem if you are close to the limit of 25,000 simultaneous connections. It may be caused by the trojan horse mentioned above or it may be caused by legitimate use. To check to see how close you are, check the output of the following commands: fw tab -t connections -s fw tab -t fwx_forw -s fw tab -t fwx_backw -s If the #VALS for any of these commands is close to 25,000, you should consider bumping up the number of connections allowed. See Increasing Number of Connections Allowed for details on how to do this. -----Original Message----- From: ext Rao, Mona [mailto:[EMAIL PROTECTED]] Sent: Thursday, October 17, 2002 5:46 AM To: [EMAIL PROTECTED] Subject: [FW-1] Critical log error on Nokia appliance Hello, I am running fw1 v4.1 sp5 and recently I started seeing a [LOG CRITICAL] error on console of my Nokia IP330 applianceFW-1: fw_xlate_forw: failed to initialize the connection. Has anyone seen this before and what it means and what is the solution. I would really appreciate a quick response since I don't know how critical it is to the functioning of the firewall. Thanks, Mona ================================================= To set vacation, Out Of Office, or away messages, send an email to [EMAIL PROTECTED] in the BODY of the email add: set fw-1-mailinglist nomail ================================================= To unsubscribe from this mailing list, please see the instructions at http://www.checkpoint.com/services/mailing.html ================================================= If you have any questions on how to change your subscription options, email [EMAIL PROTECTED] ================================================= ================================================= To set vacation, Out Of Office, or away messages, send an email to [EMAIL PROTECTED] in the BODY of the email add: set fw-1-mailinglist nomail ================================================= To unsubscribe from this mailing list, please see the instructions at http://www.checkpoint.com/services/mailing.html ================================================= If you have any questions on how to change your subscription options, email [EMAIL PROTECTED] =================================================
