<?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: SYN Timeout in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/syn-timeout/m-p/3198080#M1065755</link>
    <description>&lt;P&gt;I have tried using packet tracer and it seems that the packet is getting dropped due to ACL&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Fri, 13 Oct 2017 01:41:28 GMT</pubDate>
    <dc:creator>rsatjharman</dc:creator>
    <dc:date>2017-10-13T01:41:28Z</dc:date>
    <item>
      <title>SYN Timeout</title>
      <link>https://community.cisco.com/t5/network-security/syn-timeout/m-p/3193160#M1065751</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp;I have an issue where I am sending a Telnet request to a distant server on port 55019 however I get the following response on the ASA5506 log&amp;nbsp;&lt;STRONG&gt;Teardown TCP connection 446446 for outside:Public IP/55019 to inside:192.168.1.10/2639 duration 0:00:30 bytes 0 SYN Timeout&lt;/STRONG&gt;. I have replace the Public IP Address with&amp;nbsp;&lt;STRONG&gt;Public IP&lt;/STRONG&gt;.&amp;nbsp; The response is expected to be sent to 192.168.1.10.&amp;nbsp; Need some assistance on this, I can ping &lt;STRONG&gt;Public IP&lt;/STRONG&gt; however this particular type of traffic is not coming through thus resulting in the SYN Timeout&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 14:25:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/syn-timeout/m-p/3193160#M1065751</guid>
      <dc:creator>rsatjharman</dc:creator>
      <dc:date>2020-02-21T14:25:11Z</dc:date>
    </item>
    <item>
      <title>Re: SYN Timeout</title>
      <link>https://community.cisco.com/t5/network-security/syn-timeout/m-p/3193172#M1065753</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Is your server listening on TCP port 2639? "Teardown TCP connection..." might be because the port is closed on the server.&lt;BR /&gt;&lt;BR /&gt;HTH,&lt;BR /&gt;Meheretab</description>
      <pubDate>Tue, 03 Oct 2017 19:15:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/syn-timeout/m-p/3193172#M1065753</guid>
      <dc:creator>Meheretab Mengistu</dc:creator>
      <dc:date>2017-10-03T19:15:35Z</dc:date>
    </item>
    <item>
      <title>Re: SYN Timeout</title>
      <link>https://community.cisco.com/t5/network-security/syn-timeout/m-p/3193207#M1065754</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp; &amp;nbsp; I am not sure why the Port Number is being changed from 55019 as it is supposed to be returning on 55019 I will need to check since the Server would obviously be listening on Port 55019. Perhaps someone can assist and port us in the direction. I tried the packet tracer app and it is dropping the packet so there would be some issue on the change of port number between the outside and inside interace. Would appreciate some help on this.&lt;/P&gt;</description>
      <pubDate>Tue, 03 Oct 2017 20:24:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/syn-timeout/m-p/3193207#M1065754</guid>
      <dc:creator>rsatjharman</dc:creator>
      <dc:date>2017-10-03T20:24:05Z</dc:date>
    </item>
    <item>
      <title>Re: SYN Timeout</title>
      <link>https://community.cisco.com/t5/network-security/syn-timeout/m-p/3198080#M1065755</link>
      <description>&lt;P&gt;I have tried using packet tracer and it seems that the packet is getting dropped due to ACL&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 13 Oct 2017 01:41:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/syn-timeout/m-p/3198080#M1065755</guid>
      <dc:creator>rsatjharman</dc:creator>
      <dc:date>2017-10-13T01:41:28Z</dc:date>
    </item>
  </channel>
</rss>

