Zabbix monitoring Windows Server monitoring Flash Zabbix_get [12577]: Timeout while executing operatio

Phenomenon due to:

650) this.width=650; "title=" 1.png "style=" Float:none; "src=" http://s5.51cto.com/wyfs02/M02/75/DD/ Wkiol1zedwwat4lpaagrs7796e0472.png "alt=" Wkiol1zedwwat4lpaagrs7796e0472.png "/>

Windows bug because the trigger TCP connection cannot be released after 497 days of booting causes the number of connections to be full, always wait

10050 Connection 28230

80 takes 79530.

650) this.width=650; "title=" 2.png "style=" Float:none; "src=" http://s1.51cto.com/wyfs02/M01/75/DF/ Wkiom1zedrudnsryaaaxd479rmg720.png "alt=" Wkiom1zedrudnsryaaaxd479rmg720.png "/>

You experience the following issues in Windows Vista,windows 7,windows Server 2008 that is running on the computer, or in Windows Server R2.
650) this.width=650; "title=" 3.png "style=" Float:none; "src=" http://s1.51cto.com/wyfs02/M01/75/DD/ Wkiol1zedwwy3ivkaaaf_qpa5nq281.png "alt=" Wkiol1zedwwy3ivkaaaf_qpa5nq281.png "/>

Question 1

All TCP/IP ports in the time_wait state will not be closed after 497 days at system boot time. Therefore, the TCP/IP port may be exhausted and a new TCP/IP session cannot be created.

Note: Some network-related operations on this computer may be affected by this issue. For example, you try to use some remote administration tools to manage a Windows Server 2008-based domain controller that has been running for more than 497 days. In this example, the Remote administration tool cannot connect to the domain controller.

Question 2

The TCP/IP chimney will be uninstalled after 248.5 days of failure. Therefore, the system stops responding after 248.5 days if the connection is in use.

Update Patches

https://support.microsoft.com/zh-cn/kb/2553549?spid=11737&sid=156

This article is from the "Operation and maintenance of the Road" blog, please be sure to keep this source http://net592.blog.51cto.com/2136730/1712094

Zabbix monitoring Windows Server monitoring Flash Zabbix_get [12577]: Timeout while executing operatio