Solutions and some Google image IP addresses

When searching in Google.com, you will often encounter the prompt "this page cannot be displayed", and you will not be able to connect to Google for more than 10 minutes. Here are some methods, it can solve most problems that Google cannot access or access.

1. If a prompt "this page cannot be displayed" appears during the search process and Google cannot be accessed, you can try to disconnect the network and then dial up the Internet again, in this way, your IP address changes and you can access Google normally. (The principle is that the firewall only blocks IP users, not independent computers)

2. If you cannot access Google from the beginning, put the following line:

216.239.63.104 www.google.com

Add it to the: C:/Windows/system32/Drivers/etc/hosts file and access Google to see if it is normal. (The principle is to provide less-used Google image access)

3. Use the image IP address of Google in the Appendix to access Google. So many IP addresses should not be all blocked.

4. Use google.cn to access Google. However, note that the google.cn server is also in the United States. Therefore, when searching for words, "This page cannot be displayed.

5. If you encounter a DNS hijacking blocking method, you need to select the correct DNS server, set the primary DNS to the DNS of the foreign root server, and then set the secondary DNS to the foreign DNS. Specific practice: Set the primary DNS to 202.12.27.33 In the dial-up network or Nic attribute, and the secondary DNS to 202.216. 228.18 (Japanese DNS). You can also find some overseas DNS by yourself. (The principle is that DNS hijacking can only control domestic DNS servers, but it is powerless for foreign DNS servers. Therefore, as long as you do not use domestic DNS servers)

6. For Gmail, it is best not to select "Standard view with chat function" for HTTP access, otherwise it will be easily blocked.

7. Try to use https://mail.google.com to access Gmail, which will greatly improve access stability and Gtalk In Gmail will not be blocked. (The firewall is powerless for encrypted https)

8. Use the encrypted proxy server software to access Google. Of course, the current encrypted proxy servers are not very stable and the speed is not ideal.

Of course, the above method may sometimes be effective. I think the simplest method should be from Google, which is to provide a Google search that supports the HTTPS version, this can solve almost all of the current problems once and for all, and I know that adding this version should be a task for Google, and Gmail has already provided, so why do we not provide more Web searches? HTTPS is an important method for secure website access. Currently, no firewall can be seen to intercept HTTPS encrypted data. Therefore, it is better to provide an HTTPS Google service than providing google.cn.

Of course, in most countries, there are a lot of accesses to Google via https, but Google is expected to understand the importance of HTTPS for Chinese users, and HTTPS implementation is also a breeze.

Appendix: Google IP address list:

Http: // 216.239.37.103	Http: // 216.239.57.99	Http: // 64.233.187.107
Http: // 216.239.37.105	Http: // 216.239.59.103	Http: // 64.233.187.89
Http: // 216.239.37.106	Http: // 216.239.59.104	Http: // 64.233.187.99
Http: // 216.239.37.107	Http: // 216.239.59.105	Http: // 66.102.11.104
Http: // 216.239.39.100	Http: // 216.239.59.106	Http: // 66.102.11.105
Http: // 216.239.39.102	Http: // 216.239.59.107	Http: // 66.102.11.106
Http: // 216.239.39.103	Http: // 216.239.59.147	Http: // 66.102.11.107
Http: // 216.239.39.106	Http: // 216.239.59.98	Http: // 66.102.11.99
Http: // 216.239.39.107	Http: // 216.239.59.99	Http: // 66.102.7.104
Http: // 216.239.51.100	Http: // 216.239.63.104	Http: // 66.102.7.105
Http: // 216.239.51.103	Http: // 216.239.63.91	Http: // 66.102.7.106
Http: // 216.239.53.102	Http: // 216.239.63.93	Http: // 66.102.7.107
Http: // 216.239.53.103	Http: // 216.239.63.99	Http: // 66.102.7.147
Http: // 216.239.53.104	Http: // 64.233.161.104	Http: // 66.102.7.18
Http: // 216.239.53.106	Http: // 64.233.161.105	Http: // 66.102.7.19
Http: // 216.239.53.107	Http: // 64.233.161.106	Http: // 66.102.7.89
Http: // 216.239.53.99	Http: // 64.233.161.107	Http: // 66.102.7.91
Http: // 216.239.55.102	Http: // 64.233.161.89	Http: // 66.102.7.95
Http: // 216.239.57.103	Http: // 64.233.163.104	Http: // 66.102.7.99
Http: // 216.239.57.104	Http: // 64.233.163.106	Http: // 66.102.9.104
Http: // 216.239.57.105	Http: // 64.233.163.99	Http: // 66.102.9.105
Http: // 216.239.57.106	Http: // 64.233.183.91	Http: // 66.102.9.106
Http: // 216.239.57.107	Http: // 64.233.183.93	Http: // 66.102.9.107
Http: // 216.239.57.147	Http: // 64.233.183.99	Http: // 66.102.9.147
Http: // 216.239.57.98	Http: // 64.233.187.104	Http: // 66.102.9.99