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

More than likely, your hardening included changing
HKLM\SYSTEM\CurrentControlSet\Control\FileSystem\NtfsDisable8dot3NameCreatio
n to a value of "1".

This value needs to be "0" for the installation of the OS Sensor.  The same
applies for the Win31FileSystem.

So, you'll need to uninstall the OS Sensor, make sure those 2 values are "0"
in the registry, reboot, install the OS Sensor, then you're free to return
the values to "1".

This has been escalated and is going to be addressed for RealSecure sensors
in the near future.

-Brian

-----Original Message-----
From: Costas Kolokotronis [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 25, 2001 5:16 AM
To: [EMAIL PROTECTED]
Subject: Problem with RSAgent!!



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

I installed the Real Secure host IDS sensor on a Win2K machine and I
faced the following problem:

While the issdeamon.exe service is running the RSAgent.exe service is
unable to start.

I get two or three error messages on the Windows Event Viewer stating
exactly this thing (that the RSAgent service cannot be started).

I should mention that the specific machine has been OS hardened using
the "HisecWeb.inf" Security Template from microsoft.

If you have any idea or have come up with a similar problem please let
me now.




Reply via email to