Today, I encountered a fun problem. Some of my colleagues' Machine Applications encountered exceptions and were uncertain. I finally found that he accidentally used the firewall to prevent ws2_32.dll from accessing the network;
What did ws2_32.dll do? The previous concept was just to know that ws2_32.dll is an important module of the system. I did not know what to do. So I took this opportunity to learn more and record it:
Ws2_32.dll is a Windows Sockets application interface that supports Internet and network applications.
The following statement is displayed: "The program that accesses the network automatically calls "Ws2_32.dll" File, "Ws2_32.dll" Is a dynamic link library file, which is located in the system folder. When Windows searches for dynamic link library files, it first searches the current directory of the application, if the directory of Windows is not found, the system 32 and system directories will be searched. The created "Ws2_32.dll" Files are not truly "Ws2_32.dll" Files, so the program cannot run ." I tried to find the program under Windows 7. If the program fails, all the files under system32 can be found in the experiment. The logic should be in the 2000 and xp versions. The principles in this statement are easily exploited, such as virus programs, to create a falseWs2_32.dllThe program cannot run, which is very simple and bad;