<?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 I'm running 9.6(1) with no in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ssh-issue-after-9-6/m-p/2873920#M913095</link>
    <description>&lt;P&gt;I'm running 9.6(1) with no issues. &amp;nbsp;I note compared to your config mine is configured to only allows SSHv2.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;PRE class="prettyprint"&gt;ssh stricthostkeycheck&lt;BR /&gt;ssh timeout 5&lt;BR /&gt;ssh version 2&lt;BR /&gt;ssh key-exchange group dh-group14-sha1&lt;/PRE&gt;</description>
    <pubDate>Thu, 05 May 2016 00:41:00 GMT</pubDate>
    <dc:creator>Philip D'Ath</dc:creator>
    <dc:date>2016-05-05T00:41:00Z</dc:date>
    <item>
      <title>SSH Issue after 9.6</title>
      <link>https://community.cisco.com/t5/network-security/ssh-issue-after-9-6/m-p/2873919#M913093</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;i have issue after upgrade to 9.6 , i am not able to access ssh with the same ip anymore , as show in the attached photo i can do ssh from any&amp;nbsp; interface , and from any ip behind that interface.&lt;/P&gt;
&lt;P&gt;that happen only when i upgraded , also&amp;nbsp; after i upgraded all was working normal i notice it today only, i upgraded at the site so maybe that is why i didnt note.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;now i am connected by VPN ,&amp;nbsp; but the ASA gateway is the same with no issues , same ip to access&lt;/P&gt;
&lt;P&gt;its only the DC&amp;nbsp; ASA that have this issue&lt;/P&gt;
&lt;P&gt;Note : they both in the same range&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;Muhammad&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 13:48:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssh-issue-after-9-6/m-p/2873919#M913093</guid>
      <dc:creator>Muhammad.Eissa</dc:creator>
      <dc:date>2020-02-21T13:48:47Z</dc:date>
    </item>
    <item>
      <title>I'm running 9.6(1) with no</title>
      <link>https://community.cisco.com/t5/network-security/ssh-issue-after-9-6/m-p/2873920#M913095</link>
      <description>&lt;P&gt;I'm running 9.6(1) with no issues. &amp;nbsp;I note compared to your config mine is configured to only allows SSHv2.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;PRE class="prettyprint"&gt;ssh stricthostkeycheck&lt;BR /&gt;ssh timeout 5&lt;BR /&gt;ssh version 2&lt;BR /&gt;ssh key-exchange group dh-group14-sha1&lt;/PRE&gt;</description>
      <pubDate>Thu, 05 May 2016 00:41:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssh-issue-after-9-6/m-p/2873920#M913095</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2016-05-05T00:41:00Z</dc:date>
    </item>
    <item>
      <title>Failing that, try</title>
      <link>https://community.cisco.com/t5/network-security/ssh-issue-after-9-6/m-p/2873921#M913097</link>
      <description>&lt;P&gt;Failing that, try regenerating the key:&lt;/P&gt;
&lt;PRE class="prettyprint"&gt;crypto key generate rsa general-keys modulus 4096&lt;BR /&gt;crypto key generate ecdsa&lt;/PRE&gt;</description>
      <pubDate>Thu, 05 May 2016 00:46:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssh-issue-after-9-6/m-p/2873921#M913097</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2016-05-05T00:46:22Z</dc:date>
    </item>
    <item>
      <title>Next step to try - use a</title>
      <link>https://community.cisco.com/t5/network-security/ssh-issue-after-9-6/m-p/2873922#M913099</link>
      <description>&lt;P&gt;Next step to try - use a different SSH client and see if it has the same issue.&lt;/P&gt;</description>
      <pubDate>Thu, 05 May 2016 00:46:55 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssh-issue-after-9-6/m-p/2873922#M913099</guid>
      <dc:creator>Philip D'Ath</dc:creator>
      <dc:date>2016-05-05T00:46:55Z</dc:date>
    </item>
    <item>
      <title>thanks for your fast reply ,</title>
      <link>https://community.cisco.com/t5/network-security/ssh-issue-after-9-6/m-p/2873923#M913101</link>
      <description>&lt;P&gt;thanks for your fast reply , i will try to clarify the issue more , sorry if didn`t mention that above.&lt;/P&gt;
&lt;P style="padding-left: 30px;"&gt;i used to connect on 192.168.3.1 , the outside interface ip of the DC-ASA&lt;/P&gt;
&lt;P style="padding-left: 30px;"&gt;also there is 172.16.30.1 and 10.1.127.240 , both are ip of interfaces of it&amp;nbsp; i can ssh&amp;nbsp; to any of them from any&amp;nbsp;&amp;nbsp; as shown in previous photo.&lt;/P&gt;
&lt;P style="padding-left: 30px;"&gt;after the upgrade , i am not able to connect by 192.168.3.1 i only connect&amp;nbsp;&amp;nbsp; by 10.1.127.240 from any behind this interface&lt;/P&gt;
&lt;P style="padding-left: 30px;"&gt;and 172.16.30.1 from any behind this interface&lt;/P&gt;
&lt;P style="padding-left: 30px;"&gt;&lt;/P&gt;
&lt;P style="padding-left: 30px;"&gt;in this case i understand that the issue he cant see coming from his outside interface , but i do&lt;/P&gt;</description>
      <pubDate>Thu, 05 May 2016 01:42:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ssh-issue-after-9-6/m-p/2873923#M913101</guid>
      <dc:creator>Muhammad.Eissa</dc:creator>
      <dc:date>2016-05-05T01:42:29Z</dc:date>
    </item>
  </channel>
</rss>

