Thanks Fabrice, but as said, this machine runs both the SmartCenter and the Eventia Reporter, the main IP (172.x.x.x) is the one used by the SmartCenter to communicate with several firewall modules and clusters, so changing the main IP is not an option.
Regards On 9/29/06, Fabrice Barutel <[EMAIL PROTECTED]> wrote:
Hi, Perhaps the trick could be to switch network interface and also IP addresses and physical link of course? With that, the second network interface could be the first one, and Eventia Reporter Server could listen to the well network interface? I haven't done this kind of trick, but when I read your mail, it comes to my mind. I hope it will help you. -- Fabrice Barutel Administrateur réseau et sécurité [EMAIL PROTECTED] ------------------------------ Date: Thu, 28 Sep 2006 22:04:13 -0600 From: Sergio Alvarez <[EMAIL PROTECTED]> Subject: Problems managing Eventia Reporter Hello, I have a customer for which I installed Eventia Reporter on the same machin= e where their SmartCenter resides (NGX R61 SPLAT), this machine has 2 NICs an= d obviously one of them was used as main IP to identify the corresponding object in the Check Point config, this IP belongs to a 172.x.x.x range. The second IP of the machine belongs to a 10.x.x.x range and is through that NI= C the administrators access the SmartCenter to open the SmartDashboard and the rest of the GUI tools, everything works, except the Eventia Reporter GUI, when they try to open it, either selecting it and authenticating from it or just by selecting it from the "window" menu of the Dashboard, the following error comes up: Failed to initialize communication with Eventia Reporter Server. Check that the server is running (172.x.x.x) Seems like the Eventia Reporter application is listenning to requests sent to the 172.x.x.x interface, the only way in which my customer has being abl= e to open the Reporter GUI is getting connected through Remote Desktop to a server in the 172.x.x.x network and from there open the Reporter GUI. Netstat in the SmartCenter/Reporter server confirms the 18205 port is associated just with the 172.x.x.x IP and the reporter logs won=B4t show mu= ch info about this. The only message on that log that I think might be relate= d with the failed connection attempts is the following: Invalid request received by server main thread. Request ID 144 Although I looked for it in the SK and the related documentation with no success. Does anybody know how to get this resolved? Any help will be very appreciated. Regards --=20 Sergio Alvarez (506)8301342 ================================================= 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] =================================================
-- Sergio Alvarez (506)8301342 ================================================= 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] =================================================
