Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | RE: [ISSForum] SiteProtector SP5 |
|---|---|
| Date: | Thu, 3 Feb 2005 06:16:33 +0200 |
Hi, If you are using a firewall to the WWW, you have to do rules to allow your machine to connect to another update server. Ip address 209.134.161.18. They don't tell in the documentation. Regards Albert Hertzog Technology Risk Management +2711 889 5208 +2783 660 8994 -----Original Message----- From: issforum-bounces@iss.net [mailto:issforum-bounces@iss.net] On Behalf Of Wassim Nakadi Sent: 01 February 2005 04:50 To: issforum@iss.net Subject: [ISSForum] SiteProtector SP5 Hi, Just finished installing a new SitePro sp5 from the latest Deployment manager. the XPU status for all sensors is "unavailable" I added the realsecure license as well as other licenes. Configured the proxy setting from both the "preferences tab" and the new Update Server and added a username and password. I restarted the Appl. service and i also restarted the whole server and still the the XPU status for all sensors is "unavailable". i downloaded the latest xml file manually, and still i get the same issue. i checked the file UpdateServer.log : *********************************************** 2005/02/01 15:06:37.60 T:0464 US_DownloadingThread::SetTheGuid Found the update_server section. 2005/02/01 15:06:49.85 T:0b80 CUpdateServices::LoadUpdatePolicy() Failed to load update policy file: 2005/02/01 15:06:49.85 T:0b80 CUpdateServices::Reload() Failed reloading update policy. 2005/02/01 15:06:49.85 T:0b80 CUpdateServices::LoadUpdatePolicy() Failed to load update policy file: 2005/02/01 15:06:49.85 T:0b80 CUpdateServices::Reload() Failed reloading update policy. 2005/02/01 15:06:50.29 T:0b80 No cached license data found. US_License::GetCachedCredentialString 2005/02/01 15:06:50.29 T:0b80 SelfUpdate LaunchUpdaterThread No license credentials yet, cannot start self-updating schedule. 2005/02/01 15:06:50.98 T:0c30 Xpu SessionConfigInterface Error message from Controller 0 for file SiteProtector/XPU_4_0.xml: -950468599 - The send operation failed due to a communication failure. [ID=0xc7590009] 2005/02/01 15:06:50.98 T:0c30 Xpu SessionConfigInterface SCS_PostDataFile failed for C:\Program Files\ISS\RealSecure SiteProtector\Application Server\webserver\Apache2\htdocs\XPU\SiteProtector/XPU_4_0.xml - -950468599 : The send operation failed due to a communication failure. [ID=0xc7590009] 2005/02/01 15:06:50.98 T:0c34 Xpu SessionConfigInterface Error message from Controller 0 for file SiteProtector/RiskIndex.xml: -950468599 - The send operation failed due to a communication failure. [ID=0xc7590009] 2005/02/01 15:06:50.98 T:0c34 Xpu SessionConfigInterface SCS_PostDataFile failed for C:\Program Files\ISS\RealSecure SiteProtector\Application Server\webserver\Apache2\htdocs\XPU\SiteProtector/RiskIndex.xml - -950468599 : The send operation failed due to a communication failure. [ID=0xc7590009] 2005/02/01 15:06:50.98 T:0c2c Xpu SessionConfigInterface Error message from Controller 0 for file SiteProtector/XPU_2_5.xml: -950468599 - The send operation failed due to a communication failure. [ID=0xc7590009] 2005/02/01 15:06:50.98 T:0c2c Xpu SessionConfigInterface SCS_PostDataFile failed for C:\Program Files\ISS\RealSecure SiteProtector\Application Server\webserver\Apache2\htdocs\XPU\SiteProtector/XPU_2_5.xml - -950468599 : The send operation failed due to a communication failure. [ID=0xc7590009] 2005/02/01 15:07:01.25 T:0d88 Xpu SessionConfigInterface Error message from Controller 0 for file SiteProtector/XPU_2_5.xml: -950468599 - The send operation failed due to a communication failure. [ID=0xc7590009] 2005/02/01 15:07:01.25 T:0d88 Xpu SessionConfigInterface SCS_PostDataFile failed for C:\Program Files\ISS\RealSecure SiteProtector\Application Server\webserver\Apache2\htdocs\XPU\SiteProtector/XPU_2_5.xml - -950468599 : The send operation failed due to a communication failure. [ID=0xc7590009] 2005/02/01 15:07:01.42 T:0d8c Xpu SessionConfigInterface Error message from Controller 0 for file SiteProtector/XPU_4_0.xml: -950468599 - The send operation failed due to a communication failure. [ID=0xc7590009] 2005/02/01 15:07:01.42 T:0d8c Xpu SessionConfigInterface SCS_PostDataFile failed for C:\Program Files\ISS\RealSecure SiteProtector\Application Server\webserver\Apache2\htdocs\XPU\SiteProtector/XPU_4_0.xml - -950468599 : The send operation failed due to a communication failure. [ID=0xc7590009] 2005/02/01 15:07:01.54 T:0d90 Xpu SessionConfigInterface Error message from Controller 0 for file SiteProtector/RiskIndex.xml: -950468599 - The send operation failed due to a communication failure. [ID=0xc7590009] 2005/02/01 15:07:01.54 T:0d90 Xpu SessionConfigInterface SCS_PostDataFile failed for C:\Program Files\ISS\RealSecure SiteProtector\Application Server\webserver\Apache2\htdocs\XPU\SiteProtector/RiskIndex.xml - -950468599 : The send operation failed due to a communication failure. [ID=0xc7590009] ********************************************************** Regards _______________________________________________ ISSForum mailing list ISSForum@iss.net TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to https://atla-mm1.iss.net/mailman/listinfo/issforum To contact the ISSForum Moderator, send email to mod-issforum@iss.net The ISSForum mailing list is hosted and managed by Internet Security Systems, 6303 Barfield Road, Atlanta, Georgia, USA 30328. ___________________________________________________________________________________________________ The views expressed in this email are, unless otherwise stated, those of the author and not those of the FirstRand Banking Group an Authorised Financial Service Provider or its management. The information in this e-mail is confidential and is intended solely for the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, any disclosure, copying, distribution or any action taken or omitted in reliance on this, is prohibited and may be unlawful. Whilst all reasonable steps are taken to ensure the accuracy and integrity of information and data transmitted electronically and to preserve the confidentiality thereof, no liability or responsibility whatsoever is accepted if information or data is, for whatever reason, corrupted or does not reach its intended destination. ________________________________ _______________________________________________ ISSForum mailing list ISSForum@iss.net TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to https://atla-mm1.iss.net/mailman/listinfo/issforum To contact the ISSForum Moderator, send email to mod-issforum@iss.net The ISSForum mailing list is hosted and managed by Internet Security Systems, 6303 Barfield Road, Atlanta, Georgia, USA 30328.
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | [ISSForum] Packet Filter at ISS Sensor, Hee Kiong |
|---|---|
| Next by Date: | [ISSForum] How to detect(prevent) Bropia worm with ISS., Byungkuk Seo |
| Previous by Thread: | [ISSForum] SiteProtector SP5, Wassim Nakadi |
| Next by Thread: | [ISSForum] Third Party Module stopping, Jason Baeder |
| Indexes: | [Date] [Thread] [Top] [All Lists] |