|
|
|
Thanks Jeff,
Found the file and the problem.
"connection was forcibly closed by the remote host"
Now to find out why all of a sudden this is a problem. :)
|
|
|
|
 | |
|
|
|
Remove deleted rules has been fixed. sometimes the smallest things are the problem.. also, the option you requested to check/uncheck selected and checkl/uncheck all rows for policies and sensors has been added in beta 2 which was just put online.
Cheers,
Jeff
PS. if you liked the status page before.. try double clicking on a row in Beta 2. :) |
|
|
|
| |
|
|
|
Jeff,
Remove rules works..... :) So far looks great.
|
|
|
|
| |
|
|
|
OMG...... The status page is fantastic..... Very nice to be able to bring up the rules from there.
|
|
|
|
| |
|
|
|
Jeff,
few things I noticed that need tweaking. (IDSPM 2.1 BETA 2)
On the update Server Policies page the uncheck all check all only works for the Update column not the Fast column.
I also noticied that there are sensors that are using the wrong policies and they can not be changed back to the correct ones.
|
|
|
|
| |
|
|
|
Sniffty wrote
On the update Server Policies page the uncheck all check all only works for the Update column not the Fast column.
|
yea.. the menu items are for checking the update checkbox only, not changing if you want to enable fast or not. I will add a couple of menu items to set fast or not on the selected rows.
Sniffty wrote
I also noticied that there are sensors that are using the wrong policies and they can not be changed back to the correct ones.
|
I am not sure what you mean by this. Can you explain a little more? You can't change the policy on the sensor? |
|
|
|
| |
|
|
|
Jeff,
Certain sensors have the wrong policy assigned to it and IDSPM ignores my repeated requests to change it back to the correct policy. :)
|
|
|
|
| |
|
|
|
What is it doing or not doing? Can you see a dropdown list of your other policies? if so, can you select one of them? if so, does it save? where is it going wrong?
I tested it and having no problems.
Thanks,
Jeff |
|
|
|
| |
|
|
|
Jeff,
I do have a fully populated list of policies to choose from, it just does not stick. I also now notice that I can set the sensor to use just about any policy I want other than the correct one. :) When I select the correct one it uses the same wrong policy over and over again.
|
|
|
|
| |
|
|
|
This is the same for mulitple sensors that have the problem. They always revert back to the same wrong policy if I try to select the correct policy, but I can select other policies fine.
|
|
|
|
| |
|
|
|
I know the problem... I am willing to bet you have over 10 policies? This will be fixed in a build that will hopefully be released later today, or Monday.
Thanks for the details.
Jeff |
|
|
|
| |
|
|
|
Jeff,
Correct, I have over 10.
|
|
|
|
| |
|
|
|
Please try the latest build and see if this problem still exists. While you are at it.. checkout the change log. I think you will find a lot of new useful features.
Cheers,
Jeff |
|
|
|
| |
|
|
|
Jeff,
I just installed BETA 3 and still no go. I can not change certain sensors to the correct policy. I am still working through the rest of the changes.
|
|
|
|
| |
|
|
|
ok, I am still unable to re-create the problem. I will keep trying to figure out why it is failing for you, but working for me.
Cheers,
Jeff
|
|
|
|
| |
|
|
|
I don't know if this makes any sense or sheds some light for you but I had 4 policies that I could not change before this update. Now I only have 2 that are wrong. Also note that I did not change them to the correct policies. They automagically changed. :)
|
|
|
|
| |
|
|
|
The correct policy is saving for the sensor when you close the form. The problem is the sensor form wasn't setting the policy correctly when it loaded. Did you try to re-set it, save the sensor and re-open the form?
Cheers,
Jeff |
|
|
|
| |
|
|
|
OK, I originally noticed this while in the upload policies form. That form seems to be correct now. The problem still exists in the edit sensor form. When I edit each sensor and view the policy it is using, it is worng on four of them. I just checked and it was two, now its back to four.
I am going to the eye doctor after work. :)
|
|
|
|
| |
|
|
|
Jeff,
I noticed that the Last Updated timestamp in the edit sensor form does NOT show the date on the sensors that are wrong.
|
|
|
|