<?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 Socket read time out error in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/socket-read-time-out-error/m-p/1724940#M535455</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you Varun,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Its solved. The problem was on idel timeout. I appreciate your great help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;Mulu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 25 Jul 2011 12:12:59 GMT</pubDate>
    <dc:creator>mulugojjam abebe</dc:creator>
    <dc:date>2011-07-25T12:12:59Z</dc:date>
    <item>
      <title>Socket read time out error</title>
      <link>https://community.cisco.com/t5/network-security/socket-read-time-out-error/m-p/1724935#M535417</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I face a problem on timeout. there are two servers one in DMZ and the other on the inside network. Those servers continously communicate and after a long hour, like 10 hrs, socket read time out error occured. When I move the DMZ server to the inside network it works perfectly. Access rule is configured from DMZ server to the inside and vice versa.&lt;/P&gt;&lt;P&gt;So if there is something on timeout that should be configured on the firewall please advice.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you in advance&lt;/P&gt;&lt;P&gt;Mulu&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 21:01:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/socket-read-time-out-error/m-p/1724935#M535417</guid>
      <dc:creator>mulugojjam abebe</dc:creator>
      <dc:date>2019-03-11T21:01:33Z</dc:date>
    </item>
    <item>
      <title>Socket read time out error</title>
      <link>https://community.cisco.com/t5/network-security/socket-read-time-out-error/m-p/1724936#M535419</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;could you just provide an output of show&amp;nbsp; run from the ASA, please also do collect the logs from the time when such a disconnect happensd from the ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Varun&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 21 Jul 2011 11:11:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/socket-read-time-out-error/m-p/1724936#M535419</guid>
      <dc:creator>varrao</dc:creator>
      <dc:date>2011-07-21T11:11:28Z</dc:date>
    </item>
    <item>
      <title>Socket read time out error</title>
      <link>https://community.cisco.com/t5/network-security/socket-read-time-out-error/m-p/1724937#M535441</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you Varun for your fast response.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is the wierd thing. The servers communicate on day time(working hours) perfectly. but the error occurs during night time(off hours). There are no logs on the ASA, may be the problem is due to idel time out connection. Is there any default behaviour on the ASA that will stop when the connection between the servers is idle(no session). The servers are Weblogic and database servers.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Jul 2011 08:50:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/socket-read-time-out-error/m-p/1724937#M535441</guid>
      <dc:creator>mulugojjam abebe</dc:creator>
      <dc:date>2011-07-22T08:50:07Z</dc:date>
    </item>
    <item>
      <title>Socket read time out error</title>
      <link>https://community.cisco.com/t5/network-security/socket-read-time-out-error/m-p/1724938#M535446</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Yes there is a an ideal timeout behavior set on the firewall , but you would need to check the values, for that you can do:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;show run timeout&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;this would tell you all the timeout values set on the firewall for connection timeouts. I would still suggest to check the logs and server setting as well, in the logs if you can see that the built connection was teared down due to timeout and after that the user send a packet for that connection, then the ASA would definitely drop it and hence the error message that you get. On the server you can check if it is sending keepalives for the idle connection so that the connection doesn't time out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps you out.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;Varun&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Jul 2011 09:03:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/socket-read-time-out-error/m-p/1724938#M535446</guid>
      <dc:creator>varrao</dc:creator>
      <dc:date>2011-07-22T09:03:24Z</dc:date>
    </item>
    <item>
      <title>Socket read time out error</title>
      <link>https://community.cisco.com/t5/network-security/socket-read-time-out-error/m-p/1724939#M535451</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank You Varun,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope it will solve it. I will check it today and i will be back to you.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;Mulu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 22 Jul 2011 11:59:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/socket-read-time-out-error/m-p/1724939#M535451</guid>
      <dc:creator>mulugojjam abebe</dc:creator>
      <dc:date>2011-07-22T11:59:03Z</dc:date>
    </item>
    <item>
      <title>Socket read time out error</title>
      <link>https://community.cisco.com/t5/network-security/socket-read-time-out-error/m-p/1724940#M535455</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you Varun,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Its solved. The problem was on idel timeout. I appreciate your great help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;P&gt;Mulu&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Jul 2011 12:12:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/socket-read-time-out-error/m-p/1724940#M535455</guid>
      <dc:creator>mulugojjam abebe</dc:creator>
      <dc:date>2011-07-25T12:12:59Z</dc:date>
    </item>
    <item>
      <title>Socket read time out error</title>
      <link>https://community.cisco.com/t5/network-security/socket-read-time-out-error/m-p/1724941#M535460</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dear Varun,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have faced one problem on the SSL Clientless vpn. It gives me Socket write error when i connect to the server through SSL, but i map the server with public IP and access it directly&amp;nbsp; and at this time the error disappears. Any configuration the i can tune on the SSL configuration.?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 03 Aug 2011 07:52:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/socket-read-time-out-error/m-p/1724941#M535460</guid>
      <dc:creator>mulugojjam abebe</dc:creator>
      <dc:date>2011-08-03T07:52:10Z</dc:date>
    </item>
  </channel>
</rss>

