WiFi server becomes unresponsive if it loses connection to network and reconnects

[cameronwest]

WiFi shield can connect fine, can receive and send packets, and works for a random amount of time - sometimes less than a minute, at most 5 hours. After much debugging, I determined that if the server status ever returned 4 (WL_CONNECT_FAILED), it became unresponsive to clients. Which makes sense.

I then added code where if that status occurs, it would reconnect to the network. The shield is able to reconnect without issue, returns a successful status, however it is still completely unresponsive to clients. The only thing that seems to work is manually pressing the reset button on the WiFi shield.

This has been frustrating since our project needs to have this server running for months or years without any manual intervention. 5 hours simply doesn't cut it for our needs.

I've already applied the latest version of the firmware (and multiple other versions) and this has never been resolved by any of them.

[DonKnowlton]

I have exactly the same problem on three different wifi shields. One has gone as long as 29 days before becoming unresponsive. The others typically fail within a few days. I am using IDE 1.0.5 with the wifi firmware and library that are supplied with that revision.

[derorrim]

Same issues here, is somebody working on this?
I am using a single TCP Socket that is held up all the time.
After random time the connection is dropped by the wifi shield.

[neno76]

Same issues here...

[agdl]

Hi to all. Please can you try to download the latest Arduino IDE version and try it again. Almost surely this issues has been solved.

[rpretolesi]

Hi, I update all (WiFi SHield and IDE) to last release but the problem it's the same. Many comment about this issue but no solution. After many days of test i discovered that the problem is the function:"uint8_t ServerDrv::getClientState(uint8_t sock)" in "server_drv.cpp". In this function the calling: "//Wait the reply elaboration SpiDrv::waitForSlaveReady();" hangs, and nothing to do , you must reset. It happens after a wifi reconnecting. No solution found on the network. I tested many code, but the problem , everytime, come out from here.....

[jb2b38]

Same issue 3 years later. Any news on this?