To the network administrator or the user, the occurrence “the IP address conflict” not the matter which welcome, because in a network, each main engine (strict is network interface) should have an only IP address, if presents 2 or two above main engine use same IP address, these use same IP address's main engine screen can spring the dialog box to report the IP address conflict (the following chart):
This will cause these use same IP the machine not to be able the normal access network. But, the author actually used this to have like the weak function couple days ago to help very busy. Is how the identical? Listens to me to say nothing of slowly.
ˇˇˇˇThis month 12 that day, I am sent to take to the month world building guest the department to process the network breakdown. After the preliminary diagnosis, discovers the network intermittent, restarts gateway's words, can normal long period of time, after period of time, does not work. This is a very simple network: An outside net mesh wire comes, to turn on one to move the FreeBSD gateway (to make NAT to use), the net close-down's other network interface meets the switchboard, the client side meets 2 completely on the switchboard, simultaneously, the net close-down provides the DHCP service, all clients use DHCP to gain IP automatically. First, I must determine that the breakdown occurs in there; Restarts the gateway, discovered that the customer function accesses the net normally, but the gateway prompts the DHCP request overtime immediately the warning, what clue except for this can'tsee, goes to the client side to look up IP, discovered that the gain the IP address is normal, therefore is also the suspicion the switchboard has the question, waits a while, discovered that the breakdown appeared, restarted the switchboard, the network has been also normal the question in where? A commit fainted.
ˇˇReorganized the mentality, then has looked for a client (client is windows), ping the gateway, discovered first ping does not pass unexpectedly, in ping net's other machine is normal, restarts the gateway to use the client ping gateway to be normal again, without a doubt, the network has hit the ARP deceit virus. Enters the system directory, discovers c: Next has several unusual documents, this some document, does not let the operation, run command arp - a discover that unexpectedly many line of arp requested, looks like is the network jamming breakdown which the virus causes. Cannot fall all machines with the network section, the urgent matter is discovers the main engine which does honors then to isolate processing presently first.
ˇˇˇˇHow distinguishes is in the network that main engine poison is fierce? On-line already had the good means. Some people suggested that with grasps a package of tool, then the analysis catches the package information confirms toxicant the main engine, however in my hand any has not grasped a package of tool, looked like has to want to incur. After tried to find out that summarized under some effective means that for everybody reference!
Other pages: : 1 * 2 * Next>>
|
You are here: hacking technology
> network management
> Content
Category: Home
> network management
