Caching service help please

[tmoon-mint]

Hi all,

 

I have recently setup the caching service on a Mac Mini running OSX server. I am able to see things being added to the cache if I download them from iTunes on the Mac, however iPads do not utilise the caching service and go out to the internet.

 

The network is on a static IP and as far as I can tell the caching service is as easy as turning it on and having it sit on your network. Can anyone advise where I am going wrong?

[howartp]

Can the iPads access the Mac - no VLANs or firewalls in place between them?

[tmoon-mint]

No VLANs and even with the firewall off I still have the same problem. Is there a tool or a log I can look at to try and get any more information as to whats going on?

[bald_pig]

What's the current configuration for the iPads?

[EvLPhenom]

Have you added the changes to your DNS for the iPads to hit the Mac instead of going off the to the internet to look for Apple?

[howartp]

Have you added the changes to your DNS for the iPads to hit the Mac instead of going off the to the internet to look for Apple?

You don't need to on any normal network layout.

 

The device goes to Apple, detects the external IP address, tells you to go and look for $internal_ip_address_instead and the iPad trundles off to the internal IP.

 

Peter

[Brimstone]

You need a static PUBLIC I.P. for this to work, just turning on the caching service is not the solution..

[ADMaster]

Just turning on the caching service is the solution, you do not need a static public IP either.

 

The only changes I made to the network were to allow the ipads access to the cache server ip on whatever port it is running on (random port at install)

 

Run

sudo serveradmin fullstatus caching

to get the port number.

I have my BYOD devices ACLed from the rest of the network so needed this to make an allow rule.

 

I have a network with many vlans / subnets. However all of the clients have the same public IP address via nat upstream of me.

 

In the gui interface under edit permissions I have

 

cache content from all networks

service clients with public addresses matching the servers network.

 

I also have a DNS entry matching the hostname and IP of the cache server. I'm not sure if it uses IP or hostname.

 

As long as the clients can access the mac on that port and are not firewalled it should work fine. Check the GUI edit permissions see if that does the trick.

[tmoon-mint]

We have a static public IP which was done specifically for this service. iPads are running iOS 9.1 supervised by AC2. Once I verified our public IP was static I just turned on the caching service.

[Brimstone]

Just turning on the caching service is the solution, you do not need a static public IP either.

 

The only changes I made to the network were to allow the ipads access to the cache server ip on whatever port it is running on (random port at install)

 

Run

sudo serveradmin fullstatus caching

to get the port number.

I have my BYOD devices ACLed from the rest of the network so needed this to make an allow rule.

 

I have a network with many vlans / subnets. However all of the clients have the same public IP address via nat upstream of me.

 

In the gui interface under edit permissions I have

 

cache content from all networks

service clients with public addresses matching the servers network.

 

I also have a DNS entry matching the hostname and IP of the cache server. I'm not sure if it uses IP or hostname.

 

As long as the clients can access the mac on that port and are not firewalled it should work fine. Check the GUI edit permissions see if that does the trick.

 

If you are in the UK and your school uses a pool of public I.P.'s from the LA shared between schools then you NEED a static public I.P. address, otherwise whilst your own service may work intermittently when the caching service re-registers itself with Apple you will cause havoc as other schools iPads elsewhere will be trying to contact your caching server for updates and apps.

[ADMaster]

If you are in the UK and your school uses a pool of public I.P.'s from the LA shared between schools then you NEED a static public I.P. address, otherwise whilst your own service may work intermittently when the caching service re-registers itself with Apple you will cause havoc as other schools iPads elsewhere will be trying to contact your caching server for updates and apps.

 

Perhaps a bit of misunderstanding of terms then. We have a similar structure to your LEA called ITC's. My ITC has a pool of public IP's as well. However my school is assigned one for our natted traffic. Then I have a few others assigned to servers such as our website.

 

When it was said there was a static IP, I thought the server had a separate public IP from the clients.

 

Regardless of my misunderstanding, if the clients and the server are behind the same public IP it should work. If the server has the new static IP and the clients are still on the shared pool, then that is where the problem is.