Shabbir, I've seen this recently. About 1.5 days after pushing XPU 24.2 to 14 server sensors (all now at 7.0 SP4.1 XPU 24.2), _one_ sensor began producing this error. That system is NT4.0. Before we (security) could do anything, the sysadmin had rebooted the box. The errors have not returned.
One other system that was updated at the same time also exhibited an error. This one was a Win2K system that dropped communication with SiteProtector. In this case we were able to approach the box with the sysadmin. A reboot would have been a drastic measure for this particular system. Fortuately, manually stopping and restarting all of the ISS processes resolved the issue. Jason Baeder CISSP, GCIA --- "Bashir, Shabbir" <[EMAIL PROTECTED]> wrote: > ALL, > We have 5 windows server sensors that are reporting this alert in the > thousands. The OS are NT, 2K and 2K3. The sensors are on different > XPU and SP levels. When I googled for this error, I saw a post from > this mailing list > (archives.neohapsis.com/archives/iss/2004-q3/0079.html) that mentions > the same issue. > First I thought, I should install all the XPU's, but one of the NT4 > server sensor that is seeing this event shows as 7.0 (SP4.1:XPU > 22.37). > > Has anyone else seen this alert > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com _______________________________________________ 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.
