<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Hp insight intrusion blocking in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/hp-insight-intrusion-blocking/m-p/4790076#M43752</link>
    <description>are you using global or multiple discovery credentials?&lt;BR /&gt;&lt;BR /&gt;Other causes could be you detection software configuration being set too sensitive. &lt;BR /&gt;&lt;BR /&gt;If you look it the software logs you may find the offending protocol or something to allow you to get more specific such as how far apart are the logged events which could point to a running scheduled task, like daily identification, status polling, etc.</description>
    <pubDate>Fri, 20 May 2011 15:05:31 GMT</pubDate>
    <dc:creator>jim goodman</dc:creator>
    <dc:date>2011-05-20T15:05:31Z</dc:date>
    <item>
      <title>Hp insight intrusion blocking</title>
      <link>https://community.hpe.com/t5/server-management-systems/hp-insight-intrusion-blocking/m-p/4790075#M43751</link>
      <description>I found that if I disable hp systems insight mgnt service on a domain server I do not receive daily intrusion detection error from workstations. I am uncertain why this is so, and wonder if a setting within insight is appropriate so this service can stay running without conflict.</description>
      <pubDate>Thu, 19 May 2011 21:32:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/hp-insight-intrusion-blocking/m-p/4790075#M43751</guid>
      <dc:creator>nmbrian</dc:creator>
      <dc:date>2011-05-19T21:32:10Z</dc:date>
    </item>
    <item>
      <title>Re: Hp insight intrusion blocking</title>
      <link>https://community.hpe.com/t5/server-management-systems/hp-insight-intrusion-blocking/m-p/4790076#M43752</link>
      <description>are you using global or multiple discovery credentials?&lt;BR /&gt;&lt;BR /&gt;Other causes could be you detection software configuration being set too sensitive. &lt;BR /&gt;&lt;BR /&gt;If you look it the software logs you may find the offending protocol or something to allow you to get more specific such as how far apart are the logged events which could point to a running scheduled task, like daily identification, status polling, etc.</description>
      <pubDate>Fri, 20 May 2011 15:05:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/hp-insight-intrusion-blocking/m-p/4790076#M43752</guid>
      <dc:creator>jim goodman</dc:creator>
      <dc:date>2011-05-20T15:05:31Z</dc:date>
    </item>
  </channel>
</rss>

