IIS cannot find the server, and a large number of Connections_Refused error messages cannot be accessed on static pages.

In Windows 2003, when the IIS server is accessed, the webpage cannot be displayed, and the webpage title bar prompts that the server cannot be found. Check that the IIS server is running normally and the IIS service is running normally. This problem still occurs when you restart IIS. Access to the Intranet 127.0.0.1 still fails to display webpages, dynamic pages cannot be accessed, and even html static pages cannot be accessed. It is estimated that the server is under a Denial-of-Service attack, which causes the server to reject any connection.

For more information, see the http Error Log (C: \ WINDOWS \ system32 \ LogFiles \ HTTPERR ).
Sure enough, many Number_Connections_refused errors are found in the http Error Log,

Solution:

1. Run regedit to open the Registry. Back up the Registry first.
2. Find HKEY_LOCAL_MACHINE \ SYSTEM \ CurrentControlSet \ Services \ HTTP \ Parameters.
3. Point to new on the editing menu, and click DWORD Value.
4. Type EnableAggressiveMemoryUsage and press Enter.
5. On the editing menu, click Modify.
6. Type 1 in the value data box and click OK.
7. Exit the Registry Editor.
8. Restart the HTTP service. Click Start, click Run, Type cmd in the displayed box, and click OK.
9. Type net stop http/y at the command prompt and press ENTER.
10. Type iisreset/restart in the command prompt and press ENTER.

OK. If the problem persists, restart the server.

However, when we solve the problem, we found that the request queue in the application pool where the website is located is limited to 1000. Based on the website traffic, we set it, the default 1000 is indeed a little missing