<?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: NAC Manager and Server communication issue in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/nac-manager-and-server-communication-issue/m-p/1165719#M742657</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This ended up being a conflict between the dhcpd.conf and the dchp.leases files. Removing those two files resolved the issue.&lt;/P&gt;&lt;P&gt;Strange, but true.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 27 May 2009 19:43:55 GMT</pubDate>
    <dc:creator>kschuerman</dc:creator>
    <dc:date>2009-05-27T19:43:55Z</dc:date>
    <item>
      <title>NAC Manager and Server communication issue</title>
      <link>https://community.cisco.com/t5/network-security/nac-manager-and-server-communication-issue/m-p/1165716#M742610</link>
      <description>&lt;P&gt;I have a Clean Access 4.1.8 RealIP Gateway deployment. I recently went through a domain name change and applied new SSL certificates and now I am having severe communication issues.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I click the manage button for the CAS I often get an error: "Could not connect to the Clean Access Server. This could be due to your network, ssl/authorization or shared secret settings."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Other times when it brings up the CAS management pages I click the DHCP link and get: "DHCP server not started. Invalid DHCP or network settings."&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When it works I can navigate around the management pages a little, attempt to make a change and then I get a message that the server is not connected.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;There is a FWSM and PIX515E between the manager and the server, but until the rename I didn't have any communication issues and the FW configs in regards to those devices haven't changed.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any thoughts?  Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 11:29:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nac-manager-and-server-communication-issue/m-p/1165716#M742610</guid>
      <dc:creator>kschuerman</dc:creator>
      <dc:date>2020-02-21T11:29:04Z</dc:date>
    </item>
    <item>
      <title>Re: NAC Manager and Server communication issue</title>
      <link>https://community.cisco.com/t5/network-security/nac-manager-and-server-communication-issue/m-p/1165717#M742616</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;sounds like broken SSL certs caused by the name changes.  The NAC appliances are very sensitive to these things. I found it best when I have to issue new certs on either the CAM or CAS to break the connection between the two and then importing any certs or root certs, and then re-establish the connection between them.  &lt;/P&gt;&lt;P&gt;otherwise you're asking for trouble.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 May 2009 15:23:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nac-manager-and-server-communication-issue/m-p/1165717#M742616</guid>
      <dc:creator>srue</dc:creator>
      <dc:date>2009-05-27T15:23:50Z</dc:date>
    </item>
    <item>
      <title>Re: NAC Manager and Server communication issue</title>
      <link>https://community.cisco.com/t5/network-security/nac-manager-and-server-communication-issue/m-p/1165718#M742640</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I just broke the connection and attempted to reapply the SSL certificates. The manager completed successfully, but the server responded with "unable to connect to manager.HTTP/1.1 409 reconnect.jsp:no clean access server with 00_18_71_E3_E1_AE_00_18_71_E3_E1_AF"&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 May 2009 15:32:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nac-manager-and-server-communication-issue/m-p/1165718#M742640</guid>
      <dc:creator>kschuerman</dc:creator>
      <dc:date>2009-05-27T15:32:24Z</dc:date>
    </item>
    <item>
      <title>Re: NAC Manager and Server communication issue</title>
      <link>https://community.cisco.com/t5/network-security/nac-manager-and-server-communication-issue/m-p/1165719#M742657</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;This ended up being a conflict between the dhcpd.conf and the dchp.leases files. Removing those two files resolved the issue.&lt;/P&gt;&lt;P&gt;Strange, but true.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 27 May 2009 19:43:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/nac-manager-and-server-communication-issue/m-p/1165719#M742657</guid>
      <dc:creator>kschuerman</dc:creator>
      <dc:date>2009-05-27T19:43:55Z</dc:date>
    </item>
  </channel>
</rss>

