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

The quickest way to determine what is going on with the Server Sensor is to
attempt to telnet to port 2998 and 902 (902=Server Sensor, 901 Network
Sensor, 903 EC).  You should receive a cryptic message about the installed
encryption providers.  

If this does not work, than the sensor is not started or not installed.  You
can also check out the technical support knowledgebase for additional ideas:
http://www.iss.net/support/knowledgebase/

-----Original Message-----
From: Mellor, Steve [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 02, 2002 10:02 AM
To: '[EMAIL PROTECTED]'
Subject: Server Sensor 6.5 on Windows 2000



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

I have installed Server Sensor 6.5 on a Windows 2000 Server and did not have
any problems. However, when I try to add the daemon & Sensor via the
Workgroup Manager to the Event Collector, it cannot connect/initialise the
Sensor. The error I get on the Workgroup Manager Console is "the
current.policy file does not exist etc, etc" and the Event log on the W2K
server says "Couldn't get 'engport' from engine
'CorrectServerSensorNameHere', assuming 901". I have tried stopping/starting
the issDaemon service and rebooting the W2K server. It is as if the Sensor
is not being initialised ?!

I know that the IDS system is working as there are other servers with Server
Sensors running smoothly.

I'd appreciate any help.

Steve



**********************************************************************
This email is privileged, confidential and subject to copyright.
Any unauthorised use or disclosure of its content is prohibited.
The views expressed in this communication may not necessarily
be the views held by Scottish Borders Council
**********************************************************************




Reply via email to