![]() ![]()
If the client cannot communicate with its local Caching server, it automatically downloads the content from servers controlled by Apple on the Internet. #Os x server app store cache downloadWhen a client communicates with Apple servers to download an item, if the client’s public IPv4 address matches your Caching server’s public IPv4 address, the Apple servers instruct the client to get the content from the local Caching server. The Caching server automatically registers its public IPv4 address and local network information with Apple servers. Once the clients leave the local network, they automatically use servers controlled by Apple. The clients in both subnets automatically use one of the Caching servers in their organization’s network (in the figure, one subnet has two servers to illustrate that you don’t need a Caching service for each subnet behind NAT). The clients and the Caching servers in both subnets have the same public IPv4 source address on the public Internet side of the NAT device, even though they are in different subnets. In the following figure, a network device performs NAT, and the organization has two subnets. Otherwise, the client will use servers operated by Apple or a content distribution network partner (just like they did before the Caching service was introduced as a feature). (This applies even if the client and the Caching server are on different subnets, as long as they have the same public IPv4 source address.) Fortunately, this is a common configuration.Įligible clients will automatically use the appropriate Caching server. The key is that your clients and the Caching server(s) must share the same Internet connection behind a NAT device, and their traffic from your network to the Internet must have the same source IPv4 address. #Os x server app store cache update
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |