Looking at the list of net connections using 'Netstat –ban' from the command prompt, I noticed that explorer.exe permanently lists two connections, which are for the Weather app (the only live tiles I have on the Start Screen are weather ones).
It seems as though explorer.exe establishes a connection with Akamai (hosted on my ISP’s servers), downloads a png weather icon and text for the current weather conditions (cloudy, rain, temp, etc), but doesn’t actually close the connection afterwards. The connections stay in ESTABLISHED status for a long time, after which they eventually change to CLOSE_WAIT status and stay in this state indefinitely.
After receiving the weather data, it seems as though my PC sends a ACK+FIN (Acknowledge, Finish) message to the server, and the server just responds with RST (Reset), they do this a few times until the server just stops replying. I’m not a TCP expert, so does anyone know why the connection isn’t being closed after it’s received the weather data?
It seems as though explorer.exe establishes a connection with Akamai (hosted on my ISP’s servers), downloads a png weather icon and text for the current weather conditions (cloudy, rain, temp, etc), but doesn’t actually close the connection afterwards. The connections stay in ESTABLISHED status for a long time, after which they eventually change to CLOSE_WAIT status and stay in this state indefinitely.
After receiving the weather data, it seems as though my PC sends a ACK+FIN (Acknowledge, Finish) message to the server, and the server just responds with RST (Reset), they do this a few times until the server just stops replying. I’m not a TCP expert, so does anyone know why the connection isn’t being closed after it’s received the weather data?
My Computer
System One
-
- OS
- Win 8 64-bit