Log in locally to the box. At that point go to the <DRIVE LETTER>\Program files\ISS\SERVER SENSOR\SENSOR NAME\ and delete the current.policy file. This will restore a default policy on the machine for you. If you are running this on a Linux / Unix box got to where you installed Server sensor and delete the file. Stop and restart the ISSDAEMON service on windows or run a ./realsecure stop then ./RealSecure start on the *NIX machine. This will trick the system into reloading a default policy you will have access and change the policy within WGM or SP to fix the issue.
Daniel Sergile, CISSP Information Security Engineer Cox Communications Atlanta � -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of kashif Sent: Tuesday, March 30, 2004 1:12 AM To: [EMAIL PROTECTED] Subject: [ISSForum] LOCK myself out hi, I configured a few FIRECELL signatures , now the SERVER SENSOR has taken up port 80 on the server and we cannot access the server sensor it gives the Sensor STATUS as NOT RESPONDING and has locked us out , any SOLUTIONS ?? kashif _______________________________________________ ISSForum mailing list [EMAIL PROTECTED] TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to https://atla-mm1.iss.net/mailman/listinfo/issforum To contact the ISSForum Moderator, send email to [EMAIL PROTECTED] The ISSForum mailing list is hosted and managed by Internet Security Systems, 6303 Barfield Road, Atlanta, Georgia, USA 30328. _______________________________________________ ISSForum mailing list [EMAIL PROTECTED] TO UNSUBSCRIBE OR CHANGE YOUR SUBSCRIPTION, go to https://atla-mm1.iss.net/mailman/listinfo/issforum To contact the ISSForum Moderator, send email to [EMAIL PROTECTED] The ISSForum mailing list is hosted and managed by Internet Security Systems, 6303 Barfield Road, Atlanta, Georgia, USA 30328.
