# 10 minute socket timeout?

**URL:** <https://forums.digi.com/t/10-minute-socket-timeout/4431>\
**Category:** NET+OS\
**Tags:** socket\
**Created:** [November 5, 2009, 12:38am UTC](https://forums.digi.com/t/10-minute-socket-timeout/4431 "2009-11-05T00:38:06Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![egawtry](https://avatars.discourse-cdn.com/v4/letter/e/8e8cbc/32.png) [@egawtry](https://forums.digi.com/u/egawtry)\
**Post date:** [November 5, 2009, 12:38am UTC](https://forums.digi.com/t/10-minute-socket-timeout/4431/1 "2009-11-05T00:38:06Z")

</div>

I am getting a 10 minute (actually 9:59) timeout on a socket connection. Is this something built into NetOS or some other issue? Has anyone seen this before?

I do not get this on listening sockets, only active sockets.

-Erik

---

<div class="post-metadata">

**Author:** ![charliek](https://avatars.discourse-cdn.com/v4/letter/c/94ad74/32.png) [@charliek](https://forums.digi.com/u/charliek)\
**Post date:** [November 16, 2009, 11:58pm UTC](https://forums.digi.com/t/10-minute-socket-timeout/4431/2 "2009-11-16T23:58:10Z")

</div>

Do you mean on a connect or just trying to send data after the connection has already been established?

If a connect, it sounds long, and I’d look at modifying the retransmission timeouts socket options for that socket.

If when sending data, it also sounds long, I’d look at keep alives and retransmission timeout socket options.

---

<div class="post-metadata">

**Author:** ![egawtry](https://avatars.discourse-cdn.com/v4/letter/e/8e8cbc/32.png) [@egawtry](https://forums.digi.com/u/egawtry)\
**Post date:** [November 17, 2009, 3:11pm UTC](https://forums.digi.com/t/10-minute-socket-timeout/4431/3 "2009-11-17T15:11:59Z")

</div>

After a connect, while sending data, it arbitrarily disconnects and reconnects every 9:59 minutes.

What is interesting after some testing is that it does it over the local LAN, but not when connected to a internet WAN.

Any ideas?

---

<div class="post-metadata">

**Author:** ![charliek](https://avatars.discourse-cdn.com/v4/letter/c/94ad74/32.png) [@charliek](https://forums.digi.com/u/charliek)\
**Post date:** [November 17, 2009, 8:29pm UTC](https://forums.digi.com/t/10-minute-socket-timeout/4431/4 "2009-11-17T20:29:35Z")

</div>

Maybe it’s tied to a DHCP lease that is expiring? Normally the way DHCP works is renew half way through, but if the DHCP server doesn’t respond until the Connect ME has lost it’s IP and is trying to get a new DHCP lease from anyone (versus renewing), that might cause the problem.

Otherwise do you have a wireshark network trace of the problem? It might reveal some addtional clues…

---

<div class="post-metadata">

**Author:** ![egawtry](https://avatars.discourse-cdn.com/v4/letter/e/8e8cbc/32.png) [@egawtry](https://forums.digi.com/u/egawtry)\
**Post date:** [November 18, 2009, 5:13pm UTC](https://forums.digi.com/t/10-minute-socket-timeout/4431/5 "2009-11-18T17:13:31Z")

</div>

No DHCP. I will look up wireshark.