<?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: Can't Access IPS Webserver  in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/can-t-access-ips-webserver/m-p/514434#M98433</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;2 main things to check:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) Are you using the correct web server port and using SSL/TLS?&lt;/P&gt;&lt;P&gt;By default the sensor is configured with SSL/TLS enabled, with the webserver running on port 443.&lt;/P&gt;&lt;P&gt;In the web brower you will use "&lt;A class="jive-link-custom" href="https://" target="_blank"&gt;https://&lt;/A&gt;&lt;SENSORIP&gt;" as the URL.  Not the "s" after http.  When "https" is used it will use SSL/TLS and connect to the default port 443.&lt;/SENSORIP&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) Is your web client's IP Address in the Sensor's Access List (use the "setup" command to modify the access-list)&lt;/P&gt;&lt;P&gt;Either the web client's network space, or the client's individual ip address must be in the access-list in order to be allowed to connect to the web-server.&lt;/P&gt;&lt;P&gt;If you are entering just the client's ip address and not the entire subnet then do NOT use the normal netmask, instead use /32 (or 255.255.255.255) to designate it as a single IP.  &lt;/P&gt;&lt;P&gt;For example,&lt;/P&gt;&lt;P&gt;Let's say your web client has IP 10.1.1.1 on the 10.1.1.0 network.&lt;/P&gt;&lt;P&gt;You could permit the entire 10.1.1.0 network by putting 10.1.1.0 255.255.255.0 (/24) in the access list.&lt;/P&gt;&lt;P&gt;OR you could permit just the 10.1.1.1 address by putting 10.1.1.1 255.255.255.255 (/32) in the access list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BUT if you pu 10.1.1.1 255.255.255.0 (/24) in the access list then the sensor gets confused and will not permit you to access the sensor.  (Version 4.x gets confused, in version 5.x it gives you an error and won't accept the entry).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Marco&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 19 May 2006 20:52:44 GMT</pubDate>
    <dc:creator>marcabal</dc:creator>
    <dc:date>2006-05-19T20:52:44Z</dc:date>
    <item>
      <title>Can't Access IPS Webserver</title>
      <link>https://community.cisco.com/t5/network-security/can-t-access-ips-webserver/m-p/514432#M98427</link>
      <description>&lt;P&gt;After I setup a Cisco 4240 IPS, I tried to access the appliance's IDM web portal.  Unfortunately it would not connect.  I read through all the troubleshooting documents and even read through these forums and none of the proposed solutions worked.  The connecting computer and the IPS are on the same LAN, so it's not connection.  The following is the output of the show version command:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cisco Systems Intrusion Detection Sensor, Version 4.1(5)S225&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;OS Version 2.4.18-5smpbigphys &lt;/P&gt;&lt;P&gt;Platform: IDS-4235 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Using 647368704 out of 921522176 bytes of available memory (70% usage) &lt;/P&gt;&lt;P&gt;Using 5.2G out of 15G bytes of available disk space (37% usage) &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;MainApp             2005_Sep_01_21.30   (Release)   2005-09-01T21:30:35-0500   Running    &lt;/P&gt;&lt;P&gt;AnalysisEngine      2005_Sep_01_21.30   (Release)   2005-09-01T21:30:35-0500   Running    &lt;/P&gt;&lt;P&gt;Authentication      2005_Sep_01_21.30   (Release)   2005-09-01T21:30:35-0500   Running    &lt;/P&gt;&lt;P&gt;Logger              2005_Sep_01_21.30   (Release)   2005-09-01T21:30:35-0500   Running    &lt;/P&gt;&lt;P&gt;NetworkAccess       2005_Sep_01_21.30   (Release)   2005-09-01T21:30:35-0500   Running    &lt;/P&gt;&lt;P&gt;TransactionSource   2005_Sep_01_21.30   (Release)   2005-09-01T21:30:35-0500   Running    &lt;/P&gt;&lt;P&gt;WebServer           2005_Sep_01_21.30   (Release)   2005-09-01T21:30:35-0500   Running    &lt;/P&gt;&lt;P&gt;CLI                 2005_Aug_02_10.53   (Release)   2005-08-02T10:25:35-0500              &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Upgrade History: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;* IDS-sig-4.1-5-S222           14:24:47 UTC Wed Mar 22 2006    &lt;/P&gt;&lt;P&gt;  IDS-sig-4.1-5-S225.rpm.pkg   11:01:08 UTC Tue May 09 2006    &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Recovery Partition Version 1.2 - 4.1(1)S47&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The webserver is running.  I did a packet capture when connecting to the IDM and I saw that the browser connects to the server.  The browser then tries to setup the SSL connection by sending a Client Hello.  The IDM webserver sends back an acknowledgement followed by a TCP reset.  So for some odd reason the IDM webserver sends a TCP reset during the SSL connection creation phase.  I don't know how to fix that on the IPS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help would be much appreciated.&lt;/P&gt;</description>
      <pubDate>Sun, 10 Mar 2019 10:01:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/can-t-access-ips-webserver/m-p/514432#M98427</guid>
      <dc:creator>thetick642</dc:creator>
      <dc:date>2019-03-10T10:01:31Z</dc:date>
    </item>
    <item>
      <title>Re: Can't Access IPS Webserver</title>
      <link>https://community.cisco.com/t5/network-security/can-t-access-ips-webserver/m-p/514433#M98431</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;the interface configured as the (reset) interface should connect to the same network(VLAN   etc)as the interface used for monitoring. Sounds like you have the (reset) interface configured on the management interface.....the management interface is the one you used to access with the webBrowser......&lt;/P&gt;&lt;P&gt;gprice&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 May 2006 19:24:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/can-t-access-ips-webserver/m-p/514433#M98431</guid>
      <dc:creator>garyprice</dc:creator>
      <dc:date>2006-05-19T19:24:21Z</dc:date>
    </item>
    <item>
      <title>Re: Can't Access IPS Webserver</title>
      <link>https://community.cisco.com/t5/network-security/can-t-access-ips-webserver/m-p/514434#M98433</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;2 main things to check:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1) Are you using the correct web server port and using SSL/TLS?&lt;/P&gt;&lt;P&gt;By default the sensor is configured with SSL/TLS enabled, with the webserver running on port 443.&lt;/P&gt;&lt;P&gt;In the web brower you will use "&lt;A class="jive-link-custom" href="https://" target="_blank"&gt;https://&lt;/A&gt;&lt;SENSORIP&gt;" as the URL.  Not the "s" after http.  When "https" is used it will use SSL/TLS and connect to the default port 443.&lt;/SENSORIP&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2) Is your web client's IP Address in the Sensor's Access List (use the "setup" command to modify the access-list)&lt;/P&gt;&lt;P&gt;Either the web client's network space, or the client's individual ip address must be in the access-list in order to be allowed to connect to the web-server.&lt;/P&gt;&lt;P&gt;If you are entering just the client's ip address and not the entire subnet then do NOT use the normal netmask, instead use /32 (or 255.255.255.255) to designate it as a single IP.  &lt;/P&gt;&lt;P&gt;For example,&lt;/P&gt;&lt;P&gt;Let's say your web client has IP 10.1.1.1 on the 10.1.1.0 network.&lt;/P&gt;&lt;P&gt;You could permit the entire 10.1.1.0 network by putting 10.1.1.0 255.255.255.0 (/24) in the access list.&lt;/P&gt;&lt;P&gt;OR you could permit just the 10.1.1.1 address by putting 10.1.1.1 255.255.255.255 (/32) in the access list.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;BUT if you pu 10.1.1.1 255.255.255.0 (/24) in the access list then the sensor gets confused and will not permit you to access the sensor.  (Version 4.x gets confused, in version 5.x it gives you an error and won't accept the entry).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Marco&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 19 May 2006 20:52:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/can-t-access-ips-webserver/m-p/514434#M98433</guid>
      <dc:creator>marcabal</dc:creator>
      <dc:date>2006-05-19T20:52:44Z</dc:date>
    </item>
    <item>
      <title>Re: Can't Access IPS Webserver</title>
      <link>https://community.cisco.com/t5/network-security/can-t-access-ips-webserver/m-p/514435#M98435</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks Marco for your response.  Unfortuantely those two options have been addressed without success.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 22 May 2006 17:53:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/can-t-access-ips-webserver/m-p/514435#M98435</guid>
      <dc:creator>thetick642</dc:creator>
      <dc:date>2006-05-22T17:53:22Z</dc:date>
    </item>
  </channel>
</rss>

