The first two errors will appear when u reboot the sensors/IDS server. If they are not continuously reappearing, then don't worry too much about them. It is not a key related issue.
Reboots from any firewalls/switches/router in the middle will cause the same errors. Jack -----Original Message----- From: Tiong Lee Lan [mailto:[EMAIL PROTECTED] Sent: Tuesday, 14 October 2003 5:59 a.m. To: [EMAIL PROTECTED] Subject: [ISSForum] Server Sensor 6.5 on Solaris 8 error Dear all I have recently upgraded the server sensors on my network from 6.0 to 6.5 on Solaris 8 and 7.0 on Win2k. The console has been upgraded to 6.7. The sensors on the Win2k are working fine. But I keep having problem with the sensor on Solaris. Initially I have got a problem with the MasterStatusManager. This problem disappear after I add in the user in the iss.access file. However, I still got these three main errors: Oct 12 02:45:10 AppSvr ISS[27893]: [ID 782709 user.error] (appsvr_1) - OnError from console: The session has been closed by the peer. [ID=0x47200401] Oct 12 19:04:06 AppSvr ISS[27893]: [ID 102634 user.error] (appsvr_1) - OnError from console: Connection reset by peer [ID=131] Oct 12 23:06:58 AppSvr ISS[27893]: [ID 356857 user.error] (appsvr_1) - OnError from console: Broken pipe [ID=32] I have gone through all the documents and mailing list but still could seem to find anything about this. I am sure that I have put in the keys correctly as I used the same way that I did for the Win2k sensors and I am using Certicom keys. Anyone any ideas? Thanks. regards Lee Lan _______________________________________________ ISSForum mailing list [EMAIL PROTECTED] TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to https://atla-mm1.iss.net/mailman/listinfo _______________________________________________ ISSForum mailing list [EMAIL PROTECTED] TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to https://atla-mm1.iss.net/mailman/listinfo
