64.233.160.0 – 64.233.191.255
66.102.0.0 – 66.102.15.255
66.249.64.0 – 66.249.95.255
72.14.192.0 – 72.14.255.255
74.125.0.0 – 74.125.255.255
209.85.128.0 – 209.85.255.255
216.239.32.0 – 216.239.63.255

以上文字为转载，再记一下自己的发现过程：

在ipad上下载一个软件，在网关抓包，发现它是通过a623.phobos.apple.com下载的ipa。然后搜索phobos.apple.com，找到该文，

不过文中的IP　173.223.52.163　速度并不好。于是找来一堆香港台湾的dns服务器：

202.60.252.8
202.45.84.58
168.95.1.1
139.175.252.16
61.10.1.130
203.80.96.10
210.200.211.225
208.67.220.220
61.10.0.130
61.56.211.185
168.95.192.1
168.95.192.2
139.175.10.20
139.175.55.244
139.175.150.20
202.45.84.59
211.78.130.2
202.14.67.14
202.14.67.4
208.67.222.222
210.200.211.193

用这堆服务器来解析a1.phobos.apple.com

得到一堆这样的结果IP和ping值：

选中最快的　203.186.47.56

大功告成。

As the virtual machine is connected to a private network internal to VirtualBox and invisible to the host, network services on the guest are not accessible to the host machine or to other computers on the same network. However, like a physical router, VirtualBox can make selected services available to the world outside the guest through port forwarding. This means that VirtualBox listens to certain ports on the host and resends all packets which arrive there to the guest, on the same or a different port.

To an application on the host or other physical (or virtual) machines on the network, it looks as though the service being proxied is actually running on the host. This also means that you cannot run the same service on the same ports on the host. However, you still gain the advantages of running the service in a virtual machine — for example, services on the host machine or on other virtual machines cannot be compromised or crashed by a vulnerability or a bug in the service, and the service can run in a different operating system than the host system.

You can set up a guest service which you wish to proxy using the command line tool VBoxManage; for details, please refer to the section called “VBoxManage modifyvm”.

You will need to know which ports on the guest the service uses and to decide which ports to use on the host (often but not always you will want to use the same ports on the guest and on the host). You can use any ports on the host which are not already in use by a service. For example, to set up incoming NAT connections to an ssh server in the guest, use the following command:

VBoxManage modifyvm "VM name" --natpf1 "guestssh,tcp,,2222,,22"

With the above example, all TCP traffic arriving on port 2222 on any host interface will be forwarded to port 22 in the guest. The protocol name tcp is a mandatory attribute defining which protocol should be used for forwarding (udp could also be used). The name guestssh is purely descriptive and will be auto-generated if omitted. The number after --natpf denotes the network card, like in other parts of VBoxManage.

To remove this forwarding rule again, use the following command:

VBoxManage modifyvm "VM name" --natpf1 delete "guestssh"

If for some reason the guest uses a static assigned IP address not leased from the built-in DHCP server, it is required to specify the guest IP when registering the forwarding rule:

VBoxManage modifyvm "VM name" --natpf1 "guestssh,tcp,,2222,10.0.2.19,22"

This example is identical to the previous one, except that the NAT engine is being told that the guest can be found at the 10.0.2.19 address.

To forward all incoming traffic from a specific host interface to the guest, specify the IP of that host interface like this:

VBoxManage modifyvm "VM name" --natpf1 "guestssh,tcp,127.0.0.1,2222,,22"

This forwards all TCP traffic arriving on the localhost interface (127.0.0.1) via port 2222 to port 22 in the guest.

It is not possible to configure incoming NAT connections while the VM is running. However, you can change the settings for a VM which is currently saved (or powered off at a snapshot).

2. intelppm。intel CPU的驱动。换到amd下时，它会引发蓝屏。解决办法：sc config intelppm start= demand 。 设为手动启动。

此外，遇到一个问题，系统设置的分辨率太高，启动的显示器提示分辩率太高，看不到任何东西。这样也无法修改分辨率。。。解决办法：启动到PE，挂接注册表。删除相关的硬件配置：
\SYSTEM\ControlSet001\Control\Video
\SYSTEM\ControlSet001\Hardware Profiles\000?\System\CurrentControlSet\Control\VIDEO

于是对比注册表，注册表太大，只对比了开启ICS前后的Current Control Set，也没有发现本质区别，换句话说，改注册表可能不能启用ICS，或者很难，不知道信息存在哪里。（我猜是不在注册表里的）

没办法了，使出万能法宝，一定可以成功的调试器。ollydbg威武出场，调试了一下，通过网卡属性设置ICS时，调用了hnetcfg里的COM接口。用oleview一看，嘿，这dll还提供了比较不错的idl信息，还是基于IDispatch接口的，也就是说，可以用脚本调用。于是改换方向，用这个IDL里面的关键字，继续google。这下就找到了。

用起来还挺简单： cscript  /nologo ics.vbs “private interface name” “public interface name”

key word: CONNECTION_PUBLIC  CONNECTION_PRIVATE  EnableSharing

经验教训：

1. 搜命令行或Command line 之类的关键词找不到结果时，要试一下script, vbs之类的关键字。
2. 搜这种词的时候，google还是挺垃圾的，我是用google.com/ncr搜的，还是难以找到。
3. 互联网上的垃圾信息越来越多了，想要的有深度的内容会越来越不好找。
4. 一边研究一边google的做法，目前还是比较好用的。想当年为了把windows（不是WINPE)装到移动硬盘上，并且可以在任意一台电脑上启动系统并使用系统，就是用研究再加搜索的方法，研究到80%，知道了一堆的keyword，也就容易找到相同的问题和解决方案了，否则找到的都是垃圾。

ics.vbs 下载

再也不怕丢失自己的修改了。

2. 得到当前的time_t秒数，这在程序中很容易，在linux命令下，可以用 data +%s 命令得到。

3. 在linux命令行下把数值转化为时间： 设目前秒数是1260796354，则命令为：
data -d @1260796354

当然，这些都是命令行或软件使用中的。在程序中，那是非常方便的转换。

sc config wpsdrvnt start= disabled

重启即可。

这样不会影响他的产品的其它功能。

还能创建宽带拨号连接，但不能和之前创建的重名，创建后也看不到。

查了不少时间，才想起做了这一改动，改回去重启，果然又出现了。

微软真搞笑，还有检查这一名字的。

同时发现，创建的这些宽带拨号连接，都保存在 C:\Documents and Settings\All Users\Application Data\Microsoft\Network\Connections\Pbk 下的 rasphone.pbk 里。而不是在注册表。

有一种暴力的方式是，直接让windows不去读取 autorun.ini, 这样光盘自定义的图标都不会显示出来，只显示默认光驱图标的。其原理是，利用windows已经有的重定向ini的技术，把ini重定向到注册表中的一个不存在的分支，从而破坏自动运行机制。

实现步骤：把以下内容存成 anti-autorun.reg ，导入到注册表即可。或者简单一点，直接点此下载运行。

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\IniFileMapping\autorun.inf]
@=”#USR:Software\\Microsoft\\Non_exist_node”