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

Five, wireless LAN problems

1, can not log in to the wireless router to set up

Hardware failures are mostly loose connectors, network cable breaks, hub damage and computer system failure. It is generally possible to help locate by observing the indicator light. In addition, voltage is not normal, temperature is too high, lightning strikes, etc. are also prone to failure.

Method 1: Check the data signal indicator on the router. The intermittent flashing of the power light is normal. If it is not normal, first check the connected broadband line. You can re-plug it with different network cables. Check the network connection on the computer, reset the IP address, if you do not succeed in obtaining the IP address automatically, manually set the IP and disable the network firewall function used by the system.

Method 2: Select "Never dial a connection" in the connection settings of the system IE, and click "OK" to end. Clear all options after entering "LAN Settings". Then open the IE input router address to connect.

Method 3: Restore the router to factory settings, reinstall the driver and login account and password.

If the above solution is still not resolved, please contact the manufacturer and check the conflict between the hardware.

2, can access MSN but can not open the webpage

The router is an address translation device, when you or the person communicating with you is behind a firewall or router, it prevents the two parties from directly connecting to the Internet. . At this time, the network address translation device used by both parties is required to support UPnP technology. For information about router support for this technology, please refer to the router manual you are using and consult the vendor technical support.

Method 1: Individual routers need to set UPnP to "Enable" in the LAN settings.

Method 2: It may be caused by a virus. You can open the resource manager to check the resource usage and CPU usage. If the occupancy rate is high, it is likely to be infected with a virus, and it can be detected by using anti-virus software.

Method 3: IE file is damaged. Download the new IE for installation or repair it with the operating system.

3. Networking Interruption

General wireless routers will provide three or more connection methods. Most wireless routers will be set to "on-demand connection". The data is automatically connected when it is connected. That is to say, it will detect the presence of no line load at regular intervals. Once there is no data interaction after the connection, it will automatically disconnect.

Method 1: Enter the wireless router setting interface, select “Automatic connection, automatic connection after power on and disconnection” in the connection mode.

Method 2: Check the network for network virus attacks, most likely ARP network attacks. Enter the NIC properties, manually set the IP, and replace the new IP address. If you continue to drop the cable, use professional anti-attack software to defend.

4, the network speed is too slow

First of all, it may be caused by the busy WEB server, and secondly it may be caused by the weak wireless signal.

Method 1: If the WEB server is busy, it is not solved by our users. You can try again after a while.

Method 2: In the use of wireless LANs in enterprises and SOHOs, the location of wireless routers is often overlooked. Improper placement of the wireless router is a direct cause of weak signals. The solution is simple:

First, placed in a relatively high position;

Second, the placement and receiving end should not be separated by more cement walls.

Third, try to place it in the center of the use end.

5, the status is shown to be able to send packets, but can not receive data

First make sure your physical connection is correct. Log in to the router. Use the router to ping the dns address of the access provider. If the ping is successful, the connection from the router to the internet is unblocked. Otherwise, check the configuration of the router. Then, use any PC in the internal network to ping the gateway (that is, the internal interface address of the router). If it can be pinged, the internal network connection is unblocked. Otherwise, check whether the router configuration and PC configuration are correct and whether they are related. meets the. If the above two steps can be pinged, but still can't get online, follow the steps below.

1) Check whether the configuration of the internal pc's gateway and dns is correct. After confirming the error, proceed to the next step.

2) Check the router's settings on nat and see if the configuration is normal. If the router configuration does not check for errors, it is best to check the NAT address translation table (do not know if your router supports this feature). Look at the address translation of the internal network for the corresponding entry. If you have not proved that your nat configuration must be wrong, then correct it.

6. Hardware failure

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

1), hardware troubleshooting

In a large wireless network environment, if there is a user unable to connect to the network, and other customers have no problems, then it is likely that many access points Someone has a fault. In general, by looking at the physical location of a client with a network problem, you can roughly determine which access point has a problem.

When all customers are unable to connect to the network, the problem can come from many sources. If your network uses only one access point, then the access point may have hardware problems or configuration errors. In addition, there may be problems due to excessive radio interference or a connection between the wireless access point and the wired network.

2), check the connectivity of the access point

To determine the cause of the problem of network failure, you first need to check whether the computer in the network environment can connect to the wireless access point. The simple detection method is to open the command line mode on a 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 proved. Connect to the wireless access point normally. If the wireless access point does not respond, 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 IP address of the wireless access point from the wireless client. If it succeeds, it may indicate that the network connection part of the computer may have a problem, such as the network cable is damaged.

If the wireless client cannot ping the wireless access point, then the wireless access point itself is working abnormally. You can reboot it and wait about five minutes before going through the computer and wireless client on the wired network and using the ping command to see its connectivity.

If the ping wireless access point still does not respond from these two aspects, then the wireless access point is proven to be damaged or misconfigured. At this point you can connect this potentially damaged wireless access point to a working network via an available network cable, and you will also need to check its TCP/IP configuration. After that, the wireless access point is pinged again on the wired network client. If it still fails, it indicates that the wireless access point has been damaged. At this point you should replace the new wireless access point.

3), configuration problems

The quality of the wireless network device itself can still be trusted, so the biggest problem is usually from the configuration of the device, not the hardware itself, so if the above two If the problem does not exist, please check if it is your configuration problem.

4), test signal strength

If you can ping directly to the wireless access point through the network cable, but can not ping it wirelessly, then you can basically identify the failure of the wireless access point Just temporary. If the problem has not been solved after debugging, then you can check the signal strength of the access point.

5), try changing the channel

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

6), verify WEP key

Check WEP encryption settings. If the WEP is set incorrectly, you will not be able to ping the wireless access point from the wireless terminal. Different vendors' wireless network cards and access points require you to specify different WEP keys.

7), DHCP Configuration Issues

Another reason why you can't successfully access the wireless network may be caused by a DHCP configuration error. The DHCP server in the network can be said to be a key factor in your normal use of the wireless network.

There are two solutions:

Disable the DHCP service of the access point and let the wireless client obtain the IP address from the standard DHCP server in the network.

Modify the address range of the DHCP service to make it suitable for your existing network.

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

8), multiple access point problems

Imagine if two wireless access points work at the same time by default. In this case, each access point assigns a wireless client a 192.168.0.X IP address. The resulting problem is that two wireless access points cannot distinguish which IP is assigned by itself and which is assigned by another access point. Therefore, the IP address conflict will occur in the network sooner or later. To solve this problem, you should set a different IP address allocation range on each access point to prevent address overlap.