The reason why the sharing system can't browse the webpage and the solution

When we use the Windows system to access the Internet, we often encounter the inability to browse the webpage. How is this caused? Is there any way to solve it better? See this article for you to introduce the common reasons and solutions for Windows can not browse the web.

First, the problem of network settings

This kind of reason is more likely to need to manually specify the IP, gateway, DNS server networking mode, and use a proxy server to access the Internet. Double check your computer's network settings.

Second, the problem of the DNS server

When IE can not browse the web, you can try to use IP address to access, such as http://218.30.80.30 of Bbs.winzheng.com, If it is accessible, it should be a DNS problem. The DNS problem may be caused by DNS error or DNS server itself when connecting to the network. You can manually specify the DNS service (the address can be the DNS server address provided by your local ISP. You can also use the DNS server address in other places.) In the properties of the network, (Control Panel & mdash; Network and Dial-up Connection & mdash; Local Connection & mdash; Right-click Properties & mdash; TCP/IP Protocol & mdash; Properties & mdash; The following DNS server address). Different ISPs have different DNS addresses. Sometimes it is a router or network card problem, and can't connect with the ISP's DNS service. In this case, you can turn the router off for a while or reset the router.

Another possibility is that there is a problem with the local DNS cache. In order to improve the speed of website access, the system will automatically store the website that has accessed and obtained the IP address into the local DNS cache. Once the website is accessed again, the website will be taken out from the local DNS cache without going through the DNS server. The IP address is accessed. Therefore, if there is a problem with the local DNS cache, the website will be inaccessible. You can rebuild the local DNS cache by executing ipconfig /flushdns in "Run".

Third, the problem of the IE browser itself

When the IE browser itself fails, it will naturally affect the browsing; or IE is maliciously modified and destroyed will also lead to the inability to browse the web. At this time, you can try to use the "Huangshan IE repair expert" to repair (recommended to repair in safe mode), or re-IE (such as reloading IE encountered problems can not be renewed, can refer to: attached to solve the problem can not reinstall IE)

Fourth, the problem of network firewall

If the network firewall is not set properly, such as the security level is too high, accidentally put IE into the block access list, wrong firewall policy, etc., you can try to check Strategy, reduce firewall security level or turn it off directly to try to get back to normal.

V. Problems with network protocols and network card drivers

IE cannot browse, it may be a network protocol (especially TCP/IP protocol) Or the NIC driver is damaged, you can try to re-network card driver and network protocol.

Sixth, HOSTS file problem

HOSTS file is modified, it will lead to browsing is not normal, the solution is of course to empty the contents of the HOSTS file.

Seven, system file problems

When the system files related to IE are replaced or damaged, it will affect the normal use of IE, then you can use the SFC command to fix it, WIN98 system SFC can be executed in "Run" and then scanned; WIN2000/XP/2003 is executed in sfc /scannow in "Run"

When only IE can't browse the webpage, and QQ can be used, it is often caused by damage or loss of files such as winsock.dll, wsock32.dll or wsock.vxd (VXD only exists under WIN9X system). Winsock is an important part of the TCP/IP protocol. Generally, the TCP/IP protocol is reinstalled. However, xp starts to integrate with TCP/IP protocol, so it can't be reloaded as easily as 98. You can use the netsh command to reset the TCP/IP protocol to the state it was in when the operating system was first installed. The specific operation is as follows:

Click “Start Run”, enter the “CMD” command in the Run dialog box, pop up the Command Prompt window, and then type "netsh int ip reset c:\ esetlog.txt&rdquo After the command, you can press Enter. The “resetlog.txt” file is the log file used to record the execution result of the command. The parameter option must be specified. The full path of the log file specified here is “c:\ esetlog. Txt”. The result of executing this command has the same effect as deleting and reinstalling the TCP/IP protocol.

Tip: The netsh command is a command-line based scripting tool that you can use to configure and monitor Windows systems. It also provides an interactive network shell interface. The format of the netsh command is available. See the help file (in the prompt window, type “netsh/?”).

The second solution is to repair the above files. WIN9X uses SFC to re-extract the above files. WIN2000/XP/2003 uses the sfc /scannow command to repair files. When sfc /scannow cannot be repaired, try online. WinSockFix, a repair tool for this issue, can be downloaded from the http://zhangyuehong.ys168.com/system patch directory.

Previous 12 Next Total 2 Pages