TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED]  Contact [EMAIL PROTECTED] for help with any problems!
----------------------------------------------------------------------------

Informational! You have to be kidding, Realsecure displays them as High Level Alerts 
in its default configuration, this is very annoying.

I have tried discussing this matter with ISS Support and gotten nowhere.

>>> "Fitch, Brian (ISSAtlanta)" <[EMAIL PROTECTED]> 18/01/01 19:44:59 >>>

TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED]  Contact [EMAIL PROTECTED] for help with any problems!
----------------------------------------------------------------------------

Jeff!

The NT OS Sensor is designed for both NT Workstation and NT Sensor.

musrmgr.exe is User Manager on Workstation, usrmgr.exe is User Manager on
Server.  The OS Sensor is simply saying that those files are not resident on
the box it is monitoring, thus it cannot "grab" them for monitoring.

I don't know what "winsadmin.exe" is for, but apparently it is not resident
on that machine as well.

enginemgr.policy and enginemgr.exe are two of the three files required for
the RealSecure Command Line Interface, which ironically resides on the RS
Console, not the RS OS Sensor, which explains why the OS Sensor cannot
"grab" those files.  I do not know why by default the OS Sensor would check
for these files (except for if a console and os sensor reside on the same
box).

Simply put, these file messages are informational messages and you can
ignore them.

==================================
Brian Fitch, IDS Support Engineer
Internet Security Systems, Inc.
Login to ISS SAFEsuite Product Support Knowledgebase
http://iss.custhelp.com/cgi-bin/iss/privileged?57=faq 

Request a Knowledgebase Account
http://www.iss.net/customer_care/knowledgebase/register.php 

==================================


-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] 
Sent: Thursday, January 18, 2001 12:29 PM
To: [EMAIL PROTECTED] 
Subject: OS Sensor errors



TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to
[EMAIL PROTECTED]  Contact [EMAIL PROTECTED] for help with any
problems!
----------------------------------------------------------------------------

When establishing a connection to the OS Sensor I receive these errors, but
I don't receive them every time. This OS Sensor is on an NT web server.

C:\winnt\system32\musrmgr.exe:File not found
C:\winnt\system32\winsadmin.exe:File not found
C:\ProgramFiles\ISS\RealSecure5.0\enginemgr.exe:File not found
C:\ProgramFiles\ISS\RealSecure5.0\enginemgr.policy:File not found

Also, while trying to adjust the Auto Db sync intervals for the OS Sensors I
received another error, but the change seemed to take after I stopped and
started the Sensors.

Operation Failed-
A device attached to the system is not functioning [ID=31]

*       Are these errors related? 
*       Are these errors critical to operation?
*       Why am I getting the File not found errors on one OS Sensor and not
the other when they are using the same policy and the files that are missing
are not on either system? (One OS Sensor on Exchange Server other on Web
Server, both NT)

Thanks for your help,


Jeff Owens, CCSE
Security Engineer
[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> 
FishNet Security
Ph: 816-421-6611
www.fishnetsecurity.com <http://www.fishnetsecurity.com/> 

"2000 Top 10 Kansas City Small Business"
"2000 Deloitte & Touche Fast 50 Rising Star"
"2000 Check Point Fastest Central Region Revenue Growth Award Winners"
"1999 Check Point Fastest Central Region Revenue Growth Award Winners"
"1998 Check Point Excellence Award Winners"

__________________________________________________________

The information transmitted in this e-mail is intended only for the 
addressee and may contain confidential and/or privileged material. 
Any interception, review, retransmission, dissemination, or other use 
of, or taking of any action upon this information by persons or entities
other than the intended recipient is prohibited by law and may subject 
them to criminal or civil liability. If you received this communication 
in error, please contact us immediately at 816.421.6611, and delete 
the communication from any computer or network system.
__________________________________________________________







DISCLAIMER: Any e-mail messages from the Bank for International Settlements are sent 
in good faith, but shall not be binding nor construed as constituting any obligation 
on the part of the Bank.

CONFIDENTIALITY NOTICE: This e-mail contains confidential information, which is 
intended only for the use of the recipient(s) named above. If you have received this 
communication in error, please notify the sender immediately via e-mail and return the 
entire message. Thank you for your assistance.


Reply via email to