Alas, my computer tried again the day before yesterday. The symptoms after poisoning were that my online neighbors were available, but they could not access the internet. The more obvious characteristics were:
1. Run Ping 127.0.0.1. Normally:
Pinging 127.0.0.1 with 32 bytes of data:
It is displayed as follows:
Pinging? With 32 bytes of data:
2. Run netstat-An. Normally, the current active connection status is displayed:
PROTO local address foreign address State
TCP 0.0.0.0: 135 0.0.0.0: 0 listening
TCP 0.0.0.0: 445 0.0.0.0: 0 listening
TCP 0.0.0.0: 1025 0.0.0.0: 0 listening
After poisoning, the local address and foreign address are displayed as null or *.*
3. All programs that require port binding for network listening will fail.
XP solution:
Enter netsh in the command line window, enter the shell prompt, execute WinSock, and then execute reset.
Today, my colleague's two computers also experienced the same symptoms, and all of them were resolved using the above methods.