TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to [EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems! ----------------------------------------------------------------------------
Responses inline. Randy Bartels Senior Security Consultant Internet Security Systems X-Force Professional Security Services 9601 W. Tonopah Drive Peoria, AZ 85382 Desk/VM/Cell: 623-566-3543 Fax: 253-323-9172 ISS: The Power to Protect -----Original Message----- From: Lim Bee Eng [mailto:[EMAIL PROTECTED]] Sent: Monday, May 06, 2002 4:07 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: ISS Server Sensor Problem TO UNSUBSCRIBE: email "unsubscribe issforum" in the body of your message to [EMAIL PROTECTED] Contact [EMAIL PROTECTED] for help with any problems! ---------------------------------------------------------------------------- hi, After i installed the ISS server sensor with the maximum policy enabled. However, i could not performance the veritas backup on the server sensor. At the console there, it came out alert something "riched32.dll...". After that i unblocked this signature, it still unable to do the backup. Only when i stopped the ISS server sensor daemon, the backup can proceed? Does anybody encounter this? Could you please give me some advice? I don't have access to the Veritas software, so I can't help out much there. The second weird thing i found when the ISSserver daemon is running is that, the port 12345 is found listening on all of the sensor? Is ISS server sensor using this port? Use "FPORT" (search the Internet for it) to determine what program is listening on port 12345. As mentioned in another post, enabling the "Suspect_Netbus" signature in the ServerSensor policy will make a listener on port 12345. FPORT will list what programs are listening on what port numbers. Thanks. Regards Bee Eng
