<?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: Missing NSDB in IPS MC 2.1 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/missing-nsdb-in-ips-mc-2-1/m-p/437129#M99141</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The path is broken for SecMon 2.1, I haven't noticed it broken in IPS MC 2.1.  Anyway, until Cisco fixes it, a simple work around is to create the symbolic link to the web pages.  Or copy the nsdb files to the right path.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Windows 2000 and 2003 Resource Kit contains a program called linkd.exe that allows you to create sym links much like the Unix ln command.  For SecMon, issue:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;linkd C:\CSCOpx\MDC\Apache\htdocs\vms\nsdb\html\nsdb5 C:\CSCOpx\MDC\Apache\htdocs\vms\nsdb5&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now when viewing events in the event viewer, right clicking and selecting explanation will show the appropriate sig explanation html page.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 19 Sep 2005 19:11:27 GMT</pubDate>
    <dc:creator>npham</dc:creator>
    <dc:date>2005-09-19T19:11:27Z</dc:date>
    <item>
      <title>Missing NSDB in IPS MC 2.1</title>
      <link>https://community.cisco.com/t5/network-security/missing-nsdb-in-ips-mc-2-1/m-p/437127#M99116</link>
      <description>&lt;P&gt;After upgrading from IDS MC 2.02 to IPS MC 2.1 I no longer can get to the NSDB.  Whenever I try to pull it up it cannot find the files.  The path it's looking for it is &lt;A class="jive-link-custom" href="https://server/vms/nsdb/html/nsdb/html/signature.html." target="_blank"&gt;https://server/vms/nsdb/html/nsdb/html/signature.html.&lt;/A&gt;  Is this still applicable?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 09:31:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/missing-nsdb-in-ips-mc-2-1/m-p/437127#M99116</guid>
      <dc:creator>mcvosi</dc:creator>
      <dc:date>2019-03-10T09:31:41Z</dc:date>
    </item>
    <item>
      <title>Re: Missing NSDB in IPS MC 2.1</title>
      <link>https://community.cisco.com/t5/network-security/missing-nsdb-in-ips-mc-2-1/m-p/437128#M99131</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The ddts CSCsb29404 has been filled in to take care of this issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The NSDB is still bundled with IPS MC 2.1 but the links have been changed:&lt;/P&gt;&lt;P&gt;Instead of&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="https://" target="_blank"&gt;https://&lt;/A&gt;&lt;IDS mc="" server=""&gt;/vms/nsdb/html/expsig_1000.html&lt;/IDS&gt;&lt;/P&gt;&lt;P&gt;For some reason, this is now &lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="https://" target="_blank"&gt;https://&lt;/A&gt;&lt;IDS mc="" server=""&gt;/vms/nsdb/html/nsdb/html/expsig_1000.html&lt;/IDS&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps,&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 06 Jul 2005 10:44:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/missing-nsdb-in-ips-mc-2-1/m-p/437128#M99131</guid>
      <dc:creator>jdal</dc:creator>
      <dc:date>2005-07-06T10:44:00Z</dc:date>
    </item>
    <item>
      <title>Re: Missing NSDB in IPS MC 2.1</title>
      <link>https://community.cisco.com/t5/network-security/missing-nsdb-in-ips-mc-2-1/m-p/437129#M99141</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The path is broken for SecMon 2.1, I haven't noticed it broken in IPS MC 2.1.  Anyway, until Cisco fixes it, a simple work around is to create the symbolic link to the web pages.  Or copy the nsdb files to the right path.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Windows 2000 and 2003 Resource Kit contains a program called linkd.exe that allows you to create sym links much like the Unix ln command.  For SecMon, issue:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;linkd C:\CSCOpx\MDC\Apache\htdocs\vms\nsdb\html\nsdb5 C:\CSCOpx\MDC\Apache\htdocs\vms\nsdb5&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Now when viewing events in the event viewer, right clicking and selecting explanation will show the appropriate sig explanation html page.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Sep 2005 19:11:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/missing-nsdb-in-ips-mc-2-1/m-p/437129#M99141</guid>
      <dc:creator>npham</dc:creator>
      <dc:date>2005-09-19T19:11:27Z</dc:date>
    </item>
    <item>
      <title>Re: Missing NSDB in IPS MC 2.1</title>
      <link>https://community.cisco.com/t5/network-security/missing-nsdb-in-ips-mc-2-1/m-p/437130#M99158</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;FYI, the broken link to the NSDB was fixed in SP1.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Sep 2005 19:17:49 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/missing-nsdb-in-ips-mc-2-1/m-p/437130#M99158</guid>
      <dc:creator>mcvosi</dc:creator>
      <dc:date>2005-09-19T19:17:49Z</dc:date>
    </item>
    <item>
      <title>Re: Missing NSDB in IPS MC 2.1</title>
      <link>https://community.cisco.com/t5/network-security/missing-nsdb-in-ips-mc-2-1/m-p/437131#M99166</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Our systems have SP1 applied to SecMon and the link is still broken.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Prior to upgrade, our dedicated server that runs SecMon:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Common Services 2.2.2 with SP2&lt;/P&gt;&lt;P&gt;SecMon 1.2.3&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Upgrade procedure followed was:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;upgrade Common Services to 2.2.3 with SP3&lt;/P&gt;&lt;P&gt;install JRE 1.4.08&lt;/P&gt;&lt;P&gt;upgrade SecMon to 2.0.1&lt;/P&gt;&lt;P&gt;upgrade SecMon 2.0.1 to SecMon 2.1&lt;/P&gt;&lt;P&gt;apply IPS MC/SecMon SP1&lt;/P&gt;&lt;P&gt;apply S190 update&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hmmm, I wonder if S190 was suppose to be in place before SP1?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 19 Sep 2005 19:28:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/missing-nsdb-in-ips-mc-2-1/m-p/437131#M99166</guid>
      <dc:creator>npham</dc:creator>
      <dc:date>2005-09-19T19:28:03Z</dc:date>
    </item>
    <item>
      <title>Re: Missing NSDB in IPS MC 2.1</title>
      <link>https://community.cisco.com/t5/network-security/missing-nsdb-in-ips-mc-2-1/m-p/437132#M99173</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Correction on my previous post, the command should be:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;linkd D:\CSCOpx\MDC\Apache\htdocs\vms\nsdb\html\nsdb5 D:\CSCOpx\MDC\Apache\htdocs\vms\nsdb&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Side effect is this will create a circular path; something to take note if you've got a file system backup program or integrity checker (such as Tripwire).  Either limit the depth recursion or don't recursion down the nsdb5 junction.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, if the Windows 2000 Resource Kit isn't available to you, an alternative is Mark Russinovich's junction program.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.sysinternals.com/Utilities/Junction.html" target="_blank"&gt;http://www.sysinternals.com/Utilities/Junction.html&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 11 Nov 2005 18:10:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/missing-nsdb-in-ips-mc-2-1/m-p/437132#M99173</guid>
      <dc:creator>npham</dc:creator>
      <dc:date>2005-11-11T18:10:30Z</dc:date>
    </item>
  </channel>
</rss>

