<?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: Unsuccesfull TCP session does not time out in Operating System - Linux</title>
    <link>https://community.hpe.com/t5/operating-system-linux/unsuccesfull-tcp-session-does-not-time-out/m-p/3414993#M14762</link>
    <description>You can try setting tcp_syn_retries parameter to a lower value with&lt;BR /&gt;&lt;BR /&gt;# echo 3 &amp;gt; /proc/sys/net/ipv4/tcp_syn_retries&lt;BR /&gt;&lt;BR /&gt;Now telnet to unreachable host should take about 45 seconds.&lt;BR /&gt;&lt;BR /&gt;If you want to make it permanent put an entry in /etc/sysctl.conf.</description>
    <pubDate>Thu, 04 Nov 2004 22:28:02 GMT</pubDate>
    <dc:creator>Ermin Borovac</dc:creator>
    <dc:date>2004-11-04T22:28:02Z</dc:date>
    <item>
      <title>Unsuccesfull TCP session does not time out</title>
      <link>https://community.hpe.com/t5/operating-system-linux/unsuccesfull-tcp-session-does-not-time-out/m-p/3414989#M14758</link>
      <description>I am seeing a problem with my TCP stack in which  I try to connect to a machine which is listed on DNS but is not "pinagble" and&lt;BR /&gt;the port is not active. The problem is that the connection doesn't time-out. If I do it from windows, the connection times out. &lt;BR /&gt;&lt;BR /&gt;Here is an example:&lt;BR /&gt;&lt;BR /&gt;[root@xxxxxxxx root]# telnet nyxxxxxadm3&lt;BR /&gt;Trying 10.221.7.135...&lt;BR /&gt;&lt;BR /&gt;***On Linux it just sits there forever.&lt;BR /&gt;&lt;BR /&gt;H:\&amp;gt;telnet nyxxxxxadm3&lt;BR /&gt;Connecting To nyxxxxxadm3...Could not open a connection to host on port 23 : Conn&lt;BR /&gt;ect failed&lt;BR /&gt;&lt;BR /&gt;******On windows it disconnects after a while. &lt;BR /&gt;&lt;BR /&gt;Any clues why, and how it can be fixed on Linux so it times out??&lt;BR /&gt;&lt;BR /&gt;thanks,&lt;BR /&gt;paul</description>
      <pubDate>Thu, 04 Nov 2004 10:38:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/unsuccesfull-tcp-session-does-not-time-out/m-p/3414989#M14758</guid>
      <dc:creator>Paul Ambro</dc:creator>
      <dc:date>2004-11-04T10:38:35Z</dc:date>
    </item>
    <item>
      <title>Re: Unsuccesfull TCP session does not time out</title>
      <link>https://community.hpe.com/t5/operating-system-linux/unsuccesfull-tcp-session-does-not-time-out/m-p/3414990#M14759</link>
      <description>You have no network connectivity.&lt;BR /&gt;&lt;BR /&gt;On the console, look at the /var/log/messages file.&lt;BR /&gt;&lt;BR /&gt;Check your network for a duplicate IP address. If found, change your linux configuration.&lt;BR /&gt;&lt;BR /&gt;SEP</description>
      <pubDate>Thu, 04 Nov 2004 11:05:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/unsuccesfull-tcp-session-does-not-time-out/m-p/3414990#M14759</guid>
      <dc:creator>Steven E. Protter</dc:creator>
      <dc:date>2004-11-04T11:05:40Z</dc:date>
    </item>
    <item>
      <title>Re: Unsuccesfull TCP session does not time out</title>
      <link>https://community.hpe.com/t5/operating-system-linux/unsuccesfull-tcp-session-does-not-time-out/m-p/3414991#M14760</link>
      <description>I am not concerned about the network connectivity. The issue is why Linux does not times-out a TCP connection (e.g telnet) if it is not able establish a session. Windows sends me a message and returns to the prompt, Linux hangs until I have to manually intervene with crtl-C.</description>
      <pubDate>Thu, 04 Nov 2004 11:22:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/unsuccesfull-tcp-session-does-not-time-out/m-p/3414991#M14760</guid>
      <dc:creator>Paul Ambro</dc:creator>
      <dc:date>2004-11-04T11:22:08Z</dc:date>
    </item>
    <item>
      <title>Re: Unsuccesfull TCP session does not time out</title>
      <link>https://community.hpe.com/t5/operating-system-linux/unsuccesfull-tcp-session-does-not-time-out/m-p/3414992#M14761</link>
      <description>Hi Paul,&lt;BR /&gt;&lt;BR /&gt;I just tried telnet, ssh and ftp on nonexisting address and after cca 5 min got message Connection timed out&lt;BR /&gt;I know it isn't exactly same case, but you can try it also.&lt;BR /&gt;&lt;BR /&gt;without developer's knowledge of TCP/IP stack and telnet aplication is hard to say, maybe you have  longer timeout or some kind of philosophy on your Linux distro ;-)&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Jan</description>
      <pubDate>Thu, 04 Nov 2004 14:16:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/unsuccesfull-tcp-session-does-not-time-out/m-p/3414992#M14761</guid>
      <dc:creator>Jan Sladky</dc:creator>
      <dc:date>2004-11-04T14:16:23Z</dc:date>
    </item>
    <item>
      <title>Re: Unsuccesfull TCP session does not time out</title>
      <link>https://community.hpe.com/t5/operating-system-linux/unsuccesfull-tcp-session-does-not-time-out/m-p/3414993#M14762</link>
      <description>You can try setting tcp_syn_retries parameter to a lower value with&lt;BR /&gt;&lt;BR /&gt;# echo 3 &amp;gt; /proc/sys/net/ipv4/tcp_syn_retries&lt;BR /&gt;&lt;BR /&gt;Now telnet to unreachable host should take about 45 seconds.&lt;BR /&gt;&lt;BR /&gt;If you want to make it permanent put an entry in /etc/sysctl.conf.</description>
      <pubDate>Thu, 04 Nov 2004 22:28:02 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/unsuccesfull-tcp-session-does-not-time-out/m-p/3414993#M14762</guid>
      <dc:creator>Ermin Borovac</dc:creator>
      <dc:date>2004-11-04T22:28:02Z</dc:date>
    </item>
    <item>
      <title>Re: Unsuccesfull TCP session does not time out</title>
      <link>https://community.hpe.com/t5/operating-system-linux/unsuccesfull-tcp-session-does-not-time-out/m-p/3414994#M14763</link>
      <description>Ermin,&lt;BR /&gt;&lt;BR /&gt;You suggestion seems to solve the issue. I also found some documentation on Microsoft explaining the TCP stack differences and it mentions the retry limit.&lt;BR /&gt;&lt;BR /&gt;Thanks for your help&lt;BR /&gt;&lt;BR /&gt;pa</description>
      <pubDate>Fri, 05 Nov 2004 09:42:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-linux/unsuccesfull-tcp-session-does-not-time-out/m-p/3414994#M14763</guid>
      <dc:creator>Paul Ambro</dc:creator>
      <dc:date>2004-11-05T09:42:17Z</dc:date>
    </item>
  </channel>
</rss>

