<?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: IP Communicator/ Corporate Directory in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ip-communicator-corporate-directory/m-p/918531#M85298</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My suggestion to you would be this: simply troubleshoot the problem. You can go this path if you like.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Log into the IPS and turn the event override to 0 to 100 for "Produce Alert".  That way you're reporting on all items, denies and allows.  The reason for this is that some signatures might be setup to not produce an alert when it fulfills an action.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. Review your monitoring screen, unknown if you use MARS or something else.  Consistently refresh your screen while attempting the action you require.  You'll want to identify the system you're troubleshooting in the alerts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. If you are still have issues, possibly set the IPS in bypass mode for a few seconds while you attempt the action again.  This will rule out the IPS all together.  If you are still running into a problem.. turn back to the event monitor and look even closer, as a signature is your problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4. You can either decide that the rule is important and serves a purpose or it does not.  With that, you can disable the rule.. or leave it enabled.  My suggestion would be to create an "Event Action Filter."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;5. Event Action Filter - Create an exception for the signature to allow access to a specific IP address or subnet.  The Event Action Filter is pretty self-explanatory, so you shouldn't have a problem creating that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know this doesn't answer your question, but I hope it helps you find what the problem is. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 11 Apr 2008 13:01:32 GMT</pubDate>
    <dc:creator>chickman</dc:creator>
    <dc:date>2008-04-11T13:01:32Z</dc:date>
    <item>
      <title>IP Communicator/ Corporate Directory</title>
      <link>https://community.cisco.com/t5/network-security/ip-communicator-corporate-directory/m-p/918529#M85296</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;We are experiencing problems with some Windows Vista machines running IP Communicator 2.1. When we try to access the Corporate Directory we keep getting a "Host not found" error. Has anyone experinced this? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Zak&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 10:52:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-communicator-corporate-directory/m-p/918529#M85296</guid>
      <dc:creator>Derivco12</dc:creator>
      <dc:date>2019-03-10T10:52:19Z</dc:date>
    </item>
    <item>
      <title>Re: IP Communicator/ Corporate Directory</title>
      <link>https://community.cisco.com/t5/network-security/ip-communicator-corporate-directory/m-p/918530#M85297</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have the same problem but in windows xp CIPC 2.1.2.0 and vista IPC 2.1.3.0 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;DIV&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 10 Apr 2008 21:56:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-communicator-corporate-directory/m-p/918530#M85297</guid>
      <dc:creator>davidislas</dc:creator>
      <dc:date>2008-04-10T21:56:11Z</dc:date>
    </item>
    <item>
      <title>Re: IP Communicator/ Corporate Directory</title>
      <link>https://community.cisco.com/t5/network-security/ip-communicator-corporate-directory/m-p/918531#M85298</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;My suggestion to you would be this: simply troubleshoot the problem. You can go this path if you like.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. Log into the IPS and turn the event override to 0 to 100 for "Produce Alert".  That way you're reporting on all items, denies and allows.  The reason for this is that some signatures might be setup to not produce an alert when it fulfills an action.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. Review your monitoring screen, unknown if you use MARS or something else.  Consistently refresh your screen while attempting the action you require.  You'll want to identify the system you're troubleshooting in the alerts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3. If you are still have issues, possibly set the IPS in bypass mode for a few seconds while you attempt the action again.  This will rule out the IPS all together.  If you are still running into a problem.. turn back to the event monitor and look even closer, as a signature is your problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;4. You can either decide that the rule is important and serves a purpose or it does not.  With that, you can disable the rule.. or leave it enabled.  My suggestion would be to create an "Event Action Filter."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;5. Event Action Filter - Create an exception for the signature to allow access to a specific IP address or subnet.  The Event Action Filter is pretty self-explanatory, so you shouldn't have a problem creating that.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know this doesn't answer your question, but I hope it helps you find what the problem is. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Apr 2008 13:01:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-communicator-corporate-directory/m-p/918531#M85298</guid>
      <dc:creator>chickman</dc:creator>
      <dc:date>2008-04-11T13:01:32Z</dc:date>
    </item>
    <item>
      <title>Re: IP Communicator/ Corporate Directory</title>
      <link>https://community.cisco.com/t5/network-security/ip-communicator-corporate-directory/m-p/918532#M85299</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Did you resolve this issue?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;cheers&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Jun 2008 12:02:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-communicator-corporate-directory/m-p/918532#M85299</guid>
      <dc:creator>m.batts</dc:creator>
      <dc:date>2008-06-18T12:02:33Z</dc:date>
    </item>
    <item>
      <title>Re: IP Communicator/ Corporate Directory</title>
      <link>https://community.cisco.com/t5/network-security/ip-communicator-corporate-directory/m-p/918533#M85300</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Pay special care to the TCP normalization signatures as they are the ones that have deny actions by default. Also look carefully at Service DNS signatures.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Farrukh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 18 Jun 2008 13:38:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-communicator-corporate-directory/m-p/918533#M85300</guid>
      <dc:creator>Farrukh Haroon</dc:creator>
      <dc:date>2008-06-18T13:38:21Z</dc:date>
    </item>
    <item>
      <title>Re: IP Communicator/ Corporate Directory</title>
      <link>https://community.cisco.com/t5/network-security/ip-communicator-corporate-directory/m-p/918534#M85301</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Could you give me abit more information i.e explicitly where to look in vista.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Jun 2008 11:49:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-communicator-corporate-directory/m-p/918534#M85301</guid>
      <dc:creator>m.batts</dc:creator>
      <dc:date>2008-06-23T11:49:15Z</dc:date>
    </item>
    <item>
      <title>Re: IP Communicator/ Corporate Directory</title>
      <link>https://community.cisco.com/t5/network-security/ip-communicator-corporate-directory/m-p/918535#M85302</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is this issue only with the IP communicator + vista combination or for xp etc. even..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What about regular IP phones?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Farrukh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Jun 2008 13:24:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-communicator-corporate-directory/m-p/918535#M85302</guid>
      <dc:creator>Farrukh Haroon</dc:creator>
      <dc:date>2008-06-23T13:24:38Z</dc:date>
    </item>
    <item>
      <title>Re: IP Communicator/ Corporate Directory</title>
      <link>https://community.cisco.com/t5/network-security/ip-communicator-corporate-directory/m-p/918536#M85303</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;i have the same issue just with Vista and ip communicator.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 25 Jun 2008 10:45:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ip-communicator-corporate-directory/m-p/918536#M85303</guid>
      <dc:creator>m.batts</dc:creator>
      <dc:date>2008-06-25T10:45:33Z</dc:date>
    </item>
  </channel>
</rss>

