It really doesn't matter now. I've uninstalled SiteProtector, and it won't be reinstalled until we can move the server to another location and use a clustered SQL setup, because the db for SiteProtector is eatup up all the HD space on the drive. It appears the specs the sales person gave us were grossly under what we really needed, so we're going to have to drop back and punt.
Paul Schmehl ([EMAIL PROTECTED]) Adjunct Information Security Officer The University of Texas at Dallas AVIEN Founding Member http://www.utdallas.edu/~pauls/ > -----Original Message----- > From: Layer, Ben (ISS Atlanta) [mailto:[EMAIL PROTECTED] > Sent: Tuesday, March 23, 2004 11:45 AM > To: Schmehl, Paul L; [EMAIL PROTECTED] > Subject: RE: [ISSForum] Problems with scanning and other stuff > > > Hello Paul, > > Contacting Technical Support is probably the best option to > really determine the cause of the problems you are having. > The problem could lie in the sensor, the SP server, something > in between, or all of the above. > > We would start with the specific versions you are using. > Having the latest XPU's for Scanner and SiteProtector Service > Pack 3 is essential. Then we would get the failure info off > of the sensor from the Discovery and Controller log files. > > For SQL Server, you can try locking the os page file > statically at something a bit higher than what the OS > suggests. If the OS recommends 3000MB, then I'd opt for 4000. > This may help the SQL Server's run away memory issue. > _______________________________________________ ISSForum mailing list [EMAIL PROTECTED] TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to https://atla-mm1.iss.net/mailman/listinfo/issforum To contact the ISSForum Moderator, send email to [EMAIL PROTECTED] The ISSForum mailing list is hosted and managed by Internet Security Systems, 6303 Barfield Road, Atlanta, Georgia, USA 30328.
