Solution: (The following content for my personal practice of original)
To sum up, the number of connections should be a problem, then the number of connections on the server:
1, the IIS Web site server in each site has "connection timeout", "Session timeout";
2, other programs occupy the number of server connections (such as the SMTP service in the letter out of the time may have many connections)
3, the server itself the number of TCP/IP connections, such as XP system has a limit, but the Server 2003 system does not seem to this limit.
Resolution Action:
1, my server has several sites, including a website has an automatic letter to the function, with "Netstat-na >>a.xls" command to see the server 25 port and the number of connections to the client unexpectedly there are 4,077, asked the programmer, Write the program when allowing a client IP to initiate 10 connections, which consumes the server's connection resources, the programmer changed the connection to an IP only allowed to launch 5 connections, now there is no problem to see again, only 2,312 connected, do not know whether this is the credit?
2, in IIS to use the MySQL database site settings: the "Connection timeout" time from the default 120s to 60s; Another place is "home directory"-"Configuration"-the session timeout is changed from 20 minutes to 2 minutes.
The server is running successfully for over 2 nights without problems.