<?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: Cisco ISE Gui access issues in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-ise-gui-access-issues/m-p/3876366#M543694</link>
    <description>&lt;P&gt;To eliminate whether this is a web/browser related issue or not, have you tried the following&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Check if the TCP/443 is listening&lt;/P&gt;
&lt;PRE&gt;ise01/admin# show ports | in 443
     tcp: 169.254.0.228:49, 192.168.0.221:49, 169.254.0.228:50, 192.168.0.221:50, 169.254.0.228:51, 192.168.0.221:51, 169.254.0.228:52, 192.168.0.221:52, 127.0.0.1:8888, 192.16
8.0.221:8443, :::443, 192.168.0.221:8444, 192.168.0.221:8445, :::9085, 192.168.0.221:12001, :::9090, 127.0.0.1:2020, :::9060, :::9061, :::8905, :::8009, :::5514, :::9002, :::10
99, :::8910, :::8911, :::61616, :::80, :::30008, :::9080&lt;/PRE&gt;
&lt;P&gt;And have you tried a telnet to port 443 to see if ISE is accepting the TCP connection?&amp;nbsp; Below shows that the connection is open on port 443&lt;/P&gt;
&lt;PRE&gt;[admin-biera@centos-01 ~]$
[admin-biera@centos-01 ~]$ telnet 192.168.0.221 443
Trying 192.168.0.221...
Connected to 192.168.0.221.
Escape character is '^]'.

&lt;/PRE&gt;
&lt;P&gt;if the above is working then it tells you that TCP connection to ISE Admin portal should work. It means there is no firewall in the way etc.&amp;nbsp; But if the browser is refusing connection then check the browser settings like proxy etc. - disable the proxy (if enabled) and check again.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is the new server on the same IP subnet as the old server, to which you can still access the GUI?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 19 Jun 2019 22:41:38 GMT</pubDate>
    <dc:creator>Arne Bier</dc:creator>
    <dc:date>2019-06-19T22:41:38Z</dc:date>
    <item>
      <title>Cisco ISE Gui access issues</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-gui-access-issues/m-p/3876344#M543670</link>
      <description>&lt;P&gt;OK, I have read many of the discussions in regards to the Cisco ISE GUI access problems. I rebuilt the server using 2.4 and after initial configuration i was able to log into the GUI interface and start the setup of the ISE server. I got to the point of connecting to the Active Directory when i discovered nobody knew the password for the AD service account. I requested the password be reset but while waiting for that I disconnected the ISE servers from the network for troubleshooting purposes related to another issue. After getting the new passwords I reconnected the ISE servers to the network and tried to access the GUI interface. It just timed out. I am able to ping and SSH into the servers. I can log into the GUI interface of the old ICE servers using the same browser just fine.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I check to make sure the Application server was running and it is. I also stop the application service and restarted it in safe mode. Still cannot access the GUI interface. I also changed the password as recommended in other threads and still no luck. Its as if the HTTPS connection is being refused by ISE server. Today I rebuilt the server "again" but still no luck logging into the GUI interface. I have cleared the cache on the browser and I have tried Firefox, IE and Chrome. All the browsers can log into the old ISE servers via https but not the rebuilt servers. Again, after I rebuilt them the first time I WAS able to log into the GUI interface. I am at a loss here.&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jun 2019 21:45:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-gui-access-issues/m-p/3876344#M543670</guid>
      <dc:creator>mhafbnet</dc:creator>
      <dc:date>2019-06-19T21:45:03Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Gui access issues</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-gui-access-issues/m-p/3876366#M543694</link>
      <description>&lt;P&gt;To eliminate whether this is a web/browser related issue or not, have you tried the following&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Check if the TCP/443 is listening&lt;/P&gt;
&lt;PRE&gt;ise01/admin# show ports | in 443
     tcp: 169.254.0.228:49, 192.168.0.221:49, 169.254.0.228:50, 192.168.0.221:50, 169.254.0.228:51, 192.168.0.221:51, 169.254.0.228:52, 192.168.0.221:52, 127.0.0.1:8888, 192.16
8.0.221:8443, :::443, 192.168.0.221:8444, 192.168.0.221:8445, :::9085, 192.168.0.221:12001, :::9090, 127.0.0.1:2020, :::9060, :::9061, :::8905, :::8009, :::5514, :::9002, :::10
99, :::8910, :::8911, :::61616, :::80, :::30008, :::9080&lt;/PRE&gt;
&lt;P&gt;And have you tried a telnet to port 443 to see if ISE is accepting the TCP connection?&amp;nbsp; Below shows that the connection is open on port 443&lt;/P&gt;
&lt;PRE&gt;[admin-biera@centos-01 ~]$
[admin-biera@centos-01 ~]$ telnet 192.168.0.221 443
Trying 192.168.0.221...
Connected to 192.168.0.221.
Escape character is '^]'.

&lt;/PRE&gt;
&lt;P&gt;if the above is working then it tells you that TCP connection to ISE Admin portal should work. It means there is no firewall in the way etc.&amp;nbsp; But if the browser is refusing connection then check the browser settings like proxy etc. - disable the proxy (if enabled) and check again.&amp;nbsp;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Is the new server on the same IP subnet as the old server, to which you can still access the GUI?&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Jun 2019 22:41:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-gui-access-issues/m-p/3876366#M543694</guid>
      <dc:creator>Arne Bier</dc:creator>
      <dc:date>2019-06-19T22:41:38Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Gui access issues</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-gui-access-issues/m-p/3876473#M543705</link>
      <description>When you try to get to ISE GUI and its not working, can you confirm that&lt;BR /&gt;ISE URL resolves to the correct IP?&lt;BR /&gt;&lt;BR /&gt;If you connect directly using IP, can you confirm that the ARP of the IP&lt;BR /&gt;points to the mac of the same ISE?&lt;BR /&gt;&lt;BR /&gt;If that is good, do you have a firewall or proxy which might be blocking&lt;BR /&gt;your access.&lt;BR /&gt;&lt;BR /&gt;Finally, check if the certificate of ISE is expired as I have experienced&lt;BR /&gt;the same when admin cert is expired.&lt;BR /&gt;</description>
      <pubDate>Thu, 20 Jun 2019 05:52:32 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-gui-access-issues/m-p/3876473#M543705</guid>
      <dc:creator>Mohammed al Baqari</dc:creator>
      <dc:date>2019-06-20T05:52:32Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Gui access issues</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-gui-access-issues/m-p/3876835#M543719</link>
      <description>Like I said in the original post. This had been working fine, the url does resolve to the correct ip and the ARP does point to the mac of the ISE. I can connect to the ISE server via SSH and i can ping the ISE server. This is not an ARP issue. As far as the certificate goes. I just rebuilt the server from scratch so the certificates having expired is not an issue as well. It cannot be a firewall or proxy issue because I can connect and log into the other ISE servers on the network using the same browser. I have had other admins try and HTTP to the rebuilt servers and they are unable connect as well.</description>
      <pubDate>Thu, 20 Jun 2019 14:45:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-gui-access-issues/m-p/3876835#M543719</guid>
      <dc:creator>mhafbnet</dc:creator>
      <dc:date>2019-06-20T14:45:34Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Gui access issues</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-gui-access-issues/m-p/3876839#M543736</link>
      <description>Thank you very much. I will try this today and let you know how it goes. I did do the show ports on both the ISE server that is no allowing HTTP connections and the ISE server that is allowing connections but I could not see 443 in either of them. I will try it again with the pipe.</description>
      <pubDate>Thu, 20 Jun 2019 14:48:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-gui-access-issues/m-p/3876839#M543736</guid>
      <dc:creator>mhafbnet</dc:creator>
      <dc:date>2019-06-20T14:48:19Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Gui access issues</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-gui-access-issues/m-p/3876860#M543742</link>
      <description>The new server are on the 34 subnet and the old servers are on the 36 subnet.</description>
      <pubDate>Thu, 20 Jun 2019 15:20:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-gui-access-issues/m-p/3876860#M543742</guid>
      <dc:creator>mhafbnet</dc:creator>
      <dc:date>2019-06-20T15:20:41Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ISE Gui access issues</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-gui-access-issues/m-p/3882089#M543750</link>
      <description>&lt;P&gt;I hope you have already engaged Cisco TAC support by now.&lt;/P&gt;
&lt;P&gt;If you are still in the same state and trying to resolving it yourself, then adding to the others..&lt;/P&gt;
&lt;P&gt;You could try this ISE admin CLI command "tech netstat | inc &amp;lt;ISE-Gi0-IP-Address&amp;gt;:443" to check any ESTABLISHED, TIME_WAIT, or CLOSE_WAIT. If that looks ok, then do other checks, such as telnet on port 443 from another system on the same subnet, and do some packet captures.&lt;/P&gt;</description>
      <pubDate>Sun, 30 Jun 2019 04:58:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-gui-access-issues/m-p/3882089#M543750</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2019-06-30T04:58:25Z</dc:date>
    </item>
  </channel>
</rss>

