<?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 Bad protocol version identification in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/bad-protocol-version-identification/m-p/4625799#M378024</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;My system is running on HP-UX 11.23&lt;BR /&gt;Once or twice a month, syslog is reporting the following messages:&lt;BR /&gt;&lt;BR /&gt;Mar 30 01:26:57 PPCN01 sshd[11654]: Bad protocol version identification '\377\373\037\377\373 \377\373\030\377\373'\377\375\001\377\373\003\377\375\003sysops' from UNKNOWN&lt;BR /&gt;&lt;BR /&gt;Apr 25 03:18:13 PPCN01 sshd[824]: Bad protocol version identification '\377\373\037\377\373 \377\373\030\377\373'\377\375\001\377\373\003\377\375\003' from UNKNOWN&lt;BR /&gt;&lt;BR /&gt;Based on my initial investigation, user sysops that is being used by our systems operator, and via secure CRT as console connecting to the system&lt;BR /&gt;&lt;BR /&gt;Questions:&lt;BR /&gt;1.) Is this critical?&lt;BR /&gt;2.) Is this normal when using secure CRT?&lt;BR /&gt;3.) Any recommendation(s) on how to resolve this?&lt;BR /&gt;&lt;BR /&gt;We sysads are using putty as console. &lt;BR /&gt;&lt;BR /&gt;Any standard or recommended software to be use as console?&lt;BR /&gt;&lt;BR /&gt;Thanks in advance!</description>
    <pubDate>Thu, 29 Apr 2010 04:20:03 GMT</pubDate>
    <dc:creator>Jojo Castro</dc:creator>
    <dc:date>2010-04-29T04:20:03Z</dc:date>
    <item>
      <title>Bad protocol version identification</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bad-protocol-version-identification/m-p/4625799#M378024</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;My system is running on HP-UX 11.23&lt;BR /&gt;Once or twice a month, syslog is reporting the following messages:&lt;BR /&gt;&lt;BR /&gt;Mar 30 01:26:57 PPCN01 sshd[11654]: Bad protocol version identification '\377\373\037\377\373 \377\373\030\377\373'\377\375\001\377\373\003\377\375\003sysops' from UNKNOWN&lt;BR /&gt;&lt;BR /&gt;Apr 25 03:18:13 PPCN01 sshd[824]: Bad protocol version identification '\377\373\037\377\373 \377\373\030\377\373'\377\375\001\377\373\003\377\375\003' from UNKNOWN&lt;BR /&gt;&lt;BR /&gt;Based on my initial investigation, user sysops that is being used by our systems operator, and via secure CRT as console connecting to the system&lt;BR /&gt;&lt;BR /&gt;Questions:&lt;BR /&gt;1.) Is this critical?&lt;BR /&gt;2.) Is this normal when using secure CRT?&lt;BR /&gt;3.) Any recommendation(s) on how to resolve this?&lt;BR /&gt;&lt;BR /&gt;We sysads are using putty as console. &lt;BR /&gt;&lt;BR /&gt;Any standard or recommended software to be use as console?&lt;BR /&gt;&lt;BR /&gt;Thanks in advance!</description>
      <pubDate>Thu, 29 Apr 2010 04:20:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bad-protocol-version-identification/m-p/4625799#M378024</guid>
      <dc:creator>Jojo Castro</dc:creator>
      <dc:date>2010-04-29T04:20:03Z</dc:date>
    </item>
    <item>
      <title>Re: Bad protocol version identification</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/bad-protocol-version-identification/m-p/4625800#M378025</link>
      <description>Hi,&lt;BR /&gt;I think its not critical.&lt;BR /&gt;&lt;BR /&gt;Suraj</description>
      <pubDate>Thu, 29 Apr 2010 04:28:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/bad-protocol-version-identification/m-p/4625800#M378025</guid>
      <dc:creator>Suraj K Sankari</dc:creator>
      <dc:date>2010-04-29T04:28:56Z</dc:date>
    </item>
  </channel>
</rss>

