TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to [EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems! ----------------------------------------------------------------------------
Hi, I am facing the same problem with MU3.4. After some testing, I found it was caused by DHCP_Discover and DHCP_Request. The sensor is working after disable this two new signatures. I already check with ISS Tech, they have no idea and give the following advice: "please try reinstalling the sensor if the error persists after reinstalling, Please send the following files opt/ISS/sensors/sensor_name/isscsf.core and Var/adm/messages files." May be you can try their advice. But I haven't try yet.Is there any one know the solution? Regards, Gan "Otto Peltomaa" <[EMAIL PROTECTED]>@iss.net on 01-02-2002 02:40:46 Sent by: [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: Sensor�s event status won�t stay active TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to [EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems! ---------------------------------------------------------------------------- Hi Anyone has an idea why this is happening? Sensor version 6.0 I noticed, that after installation of MU 3.4, the network sensor switches status from "Active" to "Stopped" with no reason. If I start the sensor again from Managed Assets -window, the console pulls the cached events from the sensor, stays up and running (Active) about 20 sec. then switches to status "Stopped". An error message "Disconnected from network_sensor_1@IP_address event source. The session has been slosed by the peer. [ID=0x47200401] Code 30900304" and "Error trying to connect to network_sensor_!@IP_address event source: WSAECONNREFUSED- Connection refused. No connection could be made because the target machine actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host - there is no server application running. [ID=10061] code 30915168 so.. I had to unisnstall MU 3.4 back to 3.3 -> it started to work. Has anyone notices same thing? thanks. oTTo.
