<?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: TCP/IP failure code 2 in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/tcp-ip-failure-code-2/m-p/3948792#M760959</link>
    <description>Unless the error code is documented in the manpage for ssh2 (assuming there is one) you need to look in the source, but then I'm not sure if F-Secure SSH 3.2.3 is open-source.&lt;BR /&gt;&lt;BR /&gt;Might try the F-Secure website.&lt;BR /&gt;&lt;BR /&gt;Might try taking a system call trace to see what the actuall errno values are on the failing socket call(s).  Under HP-UX that would be done with the tusc utility.  Probably want to have tusc follow forks and provide verbose output.&lt;BR /&gt;&lt;BR /&gt;And then make sure a defect is filed against the software for having insufficient information in their error messages.</description>
    <pubDate>Thu, 22 Feb 2007 12:25:18 GMT</pubDate>
    <dc:creator>rick jones</dc:creator>
    <dc:date>2007-02-22T12:25:18Z</dc:date>
    <item>
      <title>TCP/IP failure code 2</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tcp-ip-failure-code-2/m-p/3948788#M760955</link>
      <description>I am trying to sftp2 a file using F-Secure SSH 3.2.3 (build 14) on hppa2.0w-hp-hpux11.00.&lt;BR /&gt;The error message I get is &lt;BR /&gt;warning: connecting to host A failed: TCP/IP failure&lt;BR /&gt;warning: child process (/usr/local/bin/ssh2) exited with code 2.&lt;BR /&gt;&lt;BR /&gt;What does this error message mean and how do I fix my problem?</description>
      <pubDate>Wed, 21 Feb 2007 10:56:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tcp-ip-failure-code-2/m-p/3948788#M760955</guid>
      <dc:creator>Mott Given</dc:creator>
      <dc:date>2007-02-21T10:56:32Z</dc:date>
    </item>
    <item>
      <title>Re: TCP/IP failure code 2</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tcp-ip-failure-code-2/m-p/3948789#M760956</link>
      <description>Hi Mott,&lt;BR /&gt;&lt;BR /&gt;i never use ssh2 but "doing some google search" maybe your error message is something to do with 'access violation' (maybe short path instead absolut path of a file).&lt;BR /&gt;&lt;BR /&gt;hth&lt;BR /&gt;regards&lt;BR /&gt;pg</description>
      <pubDate>Wed, 21 Feb 2007 11:13:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tcp-ip-failure-code-2/m-p/3948789#M760956</guid>
      <dc:creator>Piergiacomo Perini</dc:creator>
      <dc:date>2007-02-21T11:13:57Z</dc:date>
    </item>
    <item>
      <title>Re: TCP/IP failure code 2</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tcp-ip-failure-code-2/m-p/3948790#M760957</link>
      <description>Mott,&lt;BR /&gt;do BOTH machines 'talk' ssh2 ?&lt;BR /&gt;</description>
      <pubDate>Wed, 21 Feb 2007 11:50:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tcp-ip-failure-code-2/m-p/3948790#M760957</guid>
      <dc:creator>Peter Godron</dc:creator>
      <dc:date>2007-02-21T11:50:24Z</dc:date>
    </item>
    <item>
      <title>Re: TCP/IP failure code 2</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tcp-ip-failure-code-2/m-p/3948791#M760958</link>
      <description>Both machines can use ssh2.</description>
      <pubDate>Wed, 21 Feb 2007 14:38:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tcp-ip-failure-code-2/m-p/3948791#M760958</guid>
      <dc:creator>Mott Given</dc:creator>
      <dc:date>2007-02-21T14:38:23Z</dc:date>
    </item>
    <item>
      <title>Re: TCP/IP failure code 2</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/tcp-ip-failure-code-2/m-p/3948792#M760959</link>
      <description>Unless the error code is documented in the manpage for ssh2 (assuming there is one) you need to look in the source, but then I'm not sure if F-Secure SSH 3.2.3 is open-source.&lt;BR /&gt;&lt;BR /&gt;Might try the F-Secure website.&lt;BR /&gt;&lt;BR /&gt;Might try taking a system call trace to see what the actuall errno values are on the failing socket call(s).  Under HP-UX that would be done with the tusc utility.  Probably want to have tusc follow forks and provide verbose output.&lt;BR /&gt;&lt;BR /&gt;And then make sure a defect is filed against the software for having insufficient information in their error messages.</description>
      <pubDate>Thu, 22 Feb 2007 12:25:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/tcp-ip-failure-code-2/m-p/3948792#M760959</guid>
      <dc:creator>rick jones</dc:creator>
      <dc:date>2007-02-22T12:25:18Z</dc:date>
    </item>
  </channel>
</rss>

