Windows XP operating system frequently encounters network failure analysis (4)

Five, Wireless LAN problem

1, unable to login wireless router to set up

Most of the hardware failures are joint loosening, network cable broken, hub damage and computer system failure, and so on. It is generally possible to use the observation LEDs to help locate. In addition, the voltage is not normal, the temperature is too high, lightning, etc. also easy to cause trouble.

Approach One: Check the router above the data signal indicators, power lights intermittent flashing for normal, such as abnormal first check access to the broadband line, you can switch to different network cable plug well. Check the network connection in the computer, reset the IP address, and if the IP address is not successful automatically, set the IP manually and disable the network firewall feature used by the system.

Option two: In the System IE connection settings Select "Never Dial Connection", click "OK" to end. Clear all options after entering LAN settings. Then open IE enter the router address to connect.

Method Three: The router to restore factory settings, reinstall the driver and login account and password.

If the solution is still unresolved please contact the vendor and check the hardware for conflicting issues.

2, can on MSN but cannot open the webpage

A router is an address translation device that prevents both sides from connecting directly to the Internet when you or someone who communicates with you is behind a firewall or router. The network address translation devices used by both parties are required to support UPnP technology. About the router's support for this technology, please look at the router instructions you use, and consult the manufacturer's technical support.

One option: Individual routers need to set UPnP to "Enable" in LAN settings.

Option two: It could be caused by a virus. You can open Explorer to view resource consumption and CPU usage, if the occupancy rate is very high, it is likely to be infected with the virus, the anti-virus software to kill it.

Method Three: IE file damage. Download new IE for installation or repair with the operating system.

3, the networking time is intermittent

A typical wireless router can provide three or more connections of more than three ways, most wireless routers will be set by default to "on-demand connection, when there is access to data automatically to connect" that is, every once in a certain time it will detect whether the line no-load, once connected and no data interaction, will automatically disconnect.

Approach One: Enter the wireless router settings interface, in the connection mode out of the choice of "automatic connection, in the boot and disconnect after automatic connection" can be.

Approach two: Check the network for network virus attacks, most likely an ARP network attack. Enter the network card properties, manually set the IP, replace the new IP address, if continue to drop the line, please use professional anti-attack software for defense.

4, the speed is too slow

The first may be the busy Web server, followed by a faint wireless signal.

One way: If the Web server is busy, it is not what our users can solve, you can try again after a period of time.

Method Two: In the Enterprise and Soho family uses the wireless local area network, the wireless router position placement often is neglected by the people. Improper placement of wireless routers is a direct cause of weak signals. The solution is simple:

First, placed in a relatively high position;

Second, placing and receiving end should not be separated more cement walls.

Third, as far as possible in the use of the central location of the end.

5, the status shown as can send packets, but do not receive the data

First make sure your physical connection is correct. Log on to the router. Ping the access provider's DNS address with a router. If you can ping, the router to the Internet connection is unblocked, otherwise please check the configuration of the router. Then, using any PC in the internal network to ping the gateway (that is, the router's internal interface address), if you can ping, then the internal network connection is unblocked, otherwise, check the router configuration and PC configuration is correct and whether it is consistent. If the above two steps can ping, but still not on the network, then follow the steps to troubleshoot.

1, check the internal PC's gateway and DNS configuration is correct, determined after the next step.

2, check the router about NAT settings to see if the configuration is normal. If the router configuration does not check for errors, it is a good idea to check the NAT address translation table (not knowing if your router supports this feature). See if the address translation for the internal network has a corresponding entry. If there is no proof that your NAT configuration must be wrong, then correct it.

6, hardware failure

When a network failure occurs in a wireless network, you should be able to cause a network error from the hardware problem, and the wrong configuration will cause the network to not function properly.

1), Hardware scheduling error

In a large wireless network environment, if a user is unable to connect to the network while others do not have any problems, it is likely that one of the many access points is faulted. In general, by looking at the physical location of a client with a network problem, you can probably determine which access point is having a problem.

When all customers are unable to connect to the network, the problem may come from many ways. If your network uses only one access point, the access point may have a hardware problem or an incorrect configuration. In addition, it may be due to radio interference is too strong, or the wireless access point and the connection between the wired network problems.

2), check access point connectivity

To determine why you cannot connect to a network problem, first check to see if the computer in your network environment can connect to the wireless access point properly. The simple detection method is to open the command line mode on one computer in your wired network, and then ping the IP address of the wireless access point, if the wireless access point responds to the ping command, then the computer in the wired network can be verified to be connected to the wireless access point properly. If the wireless access point is not responding, there may be a problem with the wireless connection between the computer and the wireless access point, or the wireless access point itself has failed.

You can try to ping the wireless access point IP address from the wireless client, if successful, that the computer's network connection part of the problem may have occurred, such as cable damage.

If the wireless client is unable to ping to the wireless access point, then the wireless access point itself is working abnormally. You can restart it, wait about five minutes, and then use the ping command to see its connectivity through the computers and wireless clients in the wired network.

If the wireless access point is still not responding in both respects, it is proven that the wireless access point is corrupted or misconfigured. At this point, you can connect the potentially corrupted wireless access point to a functioning network via a usable cable, and you will also need to check its TCP/IP configuration. After that, ping the wireless access point again on the wired network client, and if it still fails, the wireless access point is corrupted. Then you should replace the new wireless access point.

3), Configuration issues

The quality of the wireless network device itself is generally trustworthy, so the biggest source of problem is the configuration of the device, not the hardware itself, so if the above two problems do not exist, please check to see if it is your configuration problem.

4), Test signal strength

If you can ping a wireless access point directly through a network cable, and you cannot ping it wirelessly, you can basically assume that the fault of the wireless access point is only temporary. If the problem has not been resolved after debugging, then you can check the signal strength of the access point.

5), try to change the channel

If you have been tested and you find that the signal strength is weak, but have not made any changes recently, you can try to change the channel of the wireless access point and test the signal through a wireless terminal. Since modifying the connection channel on all wireless terminals is not a small project, you should first test on a wireless terminal to prove that it is effective before it can be implemented in large areas.

6), verify the WEP key

Check the WEP encryption settings. If WEP is set incorrectly, you will also not be able to ping wireless access points from the wireless terminal. Wireless adapters and access points for different vendors require you to specify a different WEP key.

7), DHCP configuration issues

Another reason that you cannot successfully access a wireless network may be caused by a DHCP configuration error. A DHCP server in a network can be said to be a key factor in your ability to use your wireless network properly.

There are two ways to fix this:

Disables the DHCP service for the access point and allows the wireless client to obtain an IP address from a standard DHCP server within the network.

Modify the address range of the DHCP service so that it applies to your existing network.

Both of these methods are feasible, but it depends on the firmware features of your wireless access point. Many wireless access points allow you to use one of these methods, and there are few wireless access points that can support both approaches.

8), multiple access points of the problem

Imagine if there are two wireless access points that work in the default way. In this case, each access point assigns a 192.168.0.X IP address to the wireless client. The resulting problem is that two wireless access points do not distinguish which IP is allocated by itself, and which is allocated by another access point. Therefore, the problem of IP address conflict will be generated in the network sooner or later. To solve this problem, you should set a different IP address allocation range at each access point to prevent address duplication.