The IP address automatically obtained by the LAN always conflicts, what should I do?

Let’s first isolate the client computer from the network. For computers with illegal IP addresses, let’s just allow it to run, so that we can have a chance to find it. Then do some simple tests on the network. The main commands are the ping command and the arp command. Use the ping command, assuming the conflicting IP address is 146.127.35.3, in the msdos window.

The command format is as follows:

C:\WIDOWS\〉ping 146.127.35.3

Request timed out

Reply from 146.127.35.3 ： bytes=32 time〈1ms TTL=128 〉

Reply from 146.127.35.3 ： bytes=32 time〈1ms TTL=128 〉

Reply from 146.127.35.3 ： bytes=32 time<1ms TTL=128>

In fact, I initially planned to use "Start"-"Run" to execute the ping command (in actual operation, I am more accustomed to using this method), but it didn't work It was too fast and I couldn't see it, so I had to turn to msdos for help.

IP conflicts occur mainly for the following reasons. Some people may not know much about TCP/IP and how to set the parameters such as "IP address", "Subnet mask" and "Default gateway" (don't laugh at them, after all, we did it step by step), there are The parameter information they get may not be what the administrator told them, or it may be correct at the beginning but then unintentionally and accidentally modify the information. Even if the administrator gives the correct parameter data, when the machine is repaired and debugged, the maintenance personnel may use some temporary IP addresses. If they forget to change them, conflicts may occur.

After receiving the conflict report, there are several things to do. First, determine the VLAN where the conflict occurs. Through the VLAN definition of IP planning and the conflicting IP address, you can find the network segment where the conflicting address is located. This is very critical to successfully find the MAC address of the network card, because some network commands cannot be accessed across network segments.