Since the website service was migrated to the cloud, the physical machines of the replaced servers have been idle. Although some of the machines are still running some basic services, some of them are really idle.
Recently, the technical director wanted to build a local git repository, so I asked me to choose the most idle server to build it. Just a few words, one of them has no service running, it's it. I was ready to start, and found out that I couldn't access the Internet, which started this long investigation journey.
First, make sure that the ip address, subnet mask, and dns are not misconfigured. The ip address does not conflict with other machines, I promise, there is no conflict. The dns address is the same as the addresses of other machines (machines that can normally access the Internet), and there is definitely no problem.
Ping Baidu, it returns "General failure of ping transmission".
Ping one's own ip, return "ping transmission failure general failure".
Ping the gateway ip, and it returns "ping transmission failure general failure".
The gateway does not work, indicating that there must be a problem with the LAN, but I obviously connected via remote desktop. The opposing situation, at the same time, is right before my eyes. I was dumbfounded.
Ping 127.0.0.1 and it works. It shows that there is no problem with the tcp/ip protocol.
The essence can only be seen through the phenomenon.
Check the general failure of ping transmission failure. Some people say that the firewall has disabled icmp echo, so try to disable the firewall first.
Check the reasons for the restriction of the Widows network, most of which are changing the dynamic ip to the fixed ip, or setting the dns. Think about other hosts on the same network that can access the Internet. Is the ip restricted? Try another ip, it is useless, check the routing ip mac binding, there is no limit.
Look at the local security policy, there are no restrictions.
Try to get an IP dynamically, it works. At this time the problem has entered a state of no solution.
I saw someone suggesting to update the driver, but the network card driver is no better than other hardware drivers. Without a network, it means that you have to copy a USB flash drive to the host to update. Moreover, it is normal for all the parameters of the network card to be displayed. The key is that I am still using the remote desktop to operate it. The network card is working.
When I have time every day, I will sum up the various reasons in bits and pieces. In the past two or three days, the network card is disabled and enabled, and I have tried all netsh winsock reset. Finally, I had no choice but to uninstall the network card from the device manager, then scan for hardware changes and reload it back . What a big surprise, well, it's actually good.
After this painful investigation, I also summarized a lot of experience. When the network is restricted, you can start the investigation from the ip and dns configuration, then check the firewall settings, local security policies, and finally update the network card driver, uninstall and reload the network card, percent Ninety-nine problems can be solved.
There is another possible reason for the general failure of ping transmission failure. It looks like you have configured the ip, but the actual ip may not be obtained by the network card. Try any method you know that you can implement to solve the problem, and don't let experience restrict your hands-on ability.