Mavericks Caching Server Doesn't Work

problem has been solved.

yes...we do use reverse DNS

no...OSX server is not running our DNS, only caching and possibly SUS in the future.

All our mac clients use public IP xxx.xxx.xxx.14, but the public IP for 192.168.4.201(our osx server) was set to xxx.xxx.xxx.8 for a specific reason that I will not get into. Anyways that specific reason is not so relevant, so we changed osx servers public IP to the same as the other clients...now caching works. 🙂

Now back to focusing on our SMB issues...http://macsmbissues.com😟

The Mystery is solved.

I was facing the issue that the caching server was cached updates but unable to cache iOS and Mac Softwares from app store. Actully i was located in Pakistan and my iTunes account was of US store. So when i tried with anpother account which was on pakistan store. It cached each and every thing.

So check your account and your public IP address. Both should be from the same country.

Thanks.

Server 4.1, OS X 10.10.3

The Cache server is an IP4 thingie. If your network router is passing IP6 addresses up the pipe, then the Apple service will never recognize that your iPad (or whatever) can be served the data through the Cache. If you look at the logs, you'll see your Cache server setting up your configuration:

Request for registration from https://lcdn-registration.apple.com/lcdn/register succeeded

Got back public IP xxx.xxx.xxx.xxx

xxx.xxx.xxx.xxx is some nice public IP address.

That means that whenever some device talks to the update toys at Apple, if that device comes from your public IP address (i.e. through your router), the device will be introduced to your cache server so that it can do the work for you.

If you are like me, and you have an AirPort Time Capsule as your router to say HughesNet or any other IP6 WAN, things do not work because your device does not appear to come from your public IP, but from your IP6 address.

To fix this, you need to use the AirPort Utility to change Configure IPv6 to Link-local only. (That's under Internet Options... on the Internet tab)

I'm not sure using IP4 on the part of the Cache service is a great idea in the long run. So I'm guessing that will be changed as soon as Apple can find a better solution.

Hi- I think I'm having a similar problem. I'm running Server 4.1.5 and the logs say everything is running fine (registration successful, etc.). It even works when I download items onto the server machine- it caches app store purchases just fine. However, when I download from any other device on the network, it doesn't work. No messages in the logs, no caching.

When I check my IP address from any of the devices, they all appear to be the same external IP. When I check to see if they might be sending an IPv6 address, the services I use to check (ip6.me) don't seem to think I've got one. So, I'm guessing that's not the case.

Anyone have any ideas about what might be going on? I'm in a bit of a time crunch and any suggestions would be gratefully appreciated.

Thanks!

: jesse

Hey- just wanted to give this a bump- any ideas?

Thanks!

: jesse

I noticed a similar issue on my setup. Running OSX Yosemite Server. The Mac OSX clients on the network uses the caching server immediately, however for the IOS devices to start using the cache server, I had to power cycle them. I tried many other methods such as terminate the AppStore App and disconnect and reconnect wifi, but no luck. I'm not sure if IOS caches the fact that a specific network doesn't have a caching server and doesn't ask again until a reboot.

You can tell if an IOS device goes through the caching server by looking at the debug log at /Library/Server/Caching/Logs/Debug.log. If there is no activity in the Debug log then no caching is occurring while you download an app. You can also monitor the interface transfer bytes using istats or menumeters, if there is no large file transfer from the OS X server during the download of an app, then the connection is direct to the apple servers.

I have not tried to reboot the device while "off" my network and then connect later and see if it will still find the caching server.