The smooth network is manifested in both the delivery package, but also receive packets, only to come and go smoothly only normal. But if only sent, but did not receive, such a failure in the end what is going on? In the author's short two years of network management career, there have been several such failures, but the reasons for their occurrence are different. Today I will put some solutions to everyone.
Generally speaking, when this kind of failure occurs, the network connection is all good, that is, the Red Fork icon will not appear. But this is just a manifestation of the normal, so we must start from the beginning of their own.
Starting from the 1th is to check whether there is any software installed before the failure, there are no changed settings, especially anti-virus software, firewall, such as software, because the improper setting of the machine will be sent only do not receive packets. Next you can use "ping 127.0.0.1" to make a basic judgment on the working status of the local network card, if you can ping the general rules to prove that the network card is normal.
For the sake of insurance, we recommend that you should also reinstall TCP/IP in this case. Open the Properties window for the local area connection, then click the Install button, select the protocol item in the Open Component window and open the Add window, and choose Microsoft TCP/IP version 6 under Microsoft to reinstall TCP/IP.
Another situation is 10/100m Adaptive network card problem, especially the low end of the integrated network card machine, this situation occurs when the net directly set to 10M. Open the Properties window for the local Area connection, click the "Configure" button on the network card in general, switch to the Advanced tab, and set the speed to 10MB.
In general, these are the only reasons why the local machine does not receive the network card data. If all of these questions have been checked and the problem persists, then you will need to continue looking at the next level.
Continue to the next level to find the problem, which is the network and the switch. Because the network cable is still relatively fragile, one of the eight network cable can easily break, but at this time the appearance is still very normal, especially responsible for data received by the network cable break. To do this, you will need to test and replace the network cable so that you can resolve the problem by confirming that there are no problems with this machine.
The fault of the switch can be extended by the failure of the network cable, which occurs when a module or port in the switch fails. Therefore, we do not have the corresponding port for a try, may be able to play a multiplier effect. But for the VLAN-divided network, the arbitrary replacement of the port will also bring data can only be sent out of the situation, so the replacement must be determined before and after the port is in the same VLAN. (www.wzlu.com)
In general, follow the local start check, and then expand outward, so that it is easy to resolve the data can only send the failure to receive. And in dealing with a variety of network failures, you should follow this order. For all kinds of problems, most of them are caused by improper operation of the human body, before processing, it is often an unexpected gain to ask.