Issue with airprint from ipad and global http proxy setting pushed out by Meraki MDM

eevans33
Conversationalist

Issue with airprint from ipad and global http proxy setting pushed out by Meraki MDM

 

Hi
Since the ipads that I manage in a school environment have updated to iOS 17, Airprint is not working, and I have pinpointed it to something to do with the way the global http proxy is applied by the Meraki MDM.

With the proxy setting pushed out by Meraki as the global http proxy, the ipad cannot connect to the airprint printers. They appear in the list of found printers, but when one is selected it goes straight back to the print screen with "No printer selected" as the printer.

If I remove the global proxy setting pushed out from Meraki, and apply the same proxy settings manually, it works absolutely fine (as it has always done in the past).

Has anyone else seen this issue, or have any idea how to pursue a fix?

 

Many thanks, Emma

3 Replies 3
ConnorL
Meraki Employee
Meraki Employee

Hey @eevans33 ,

 

Does this happen on all devices or a small subset? Curious if it's only on a certain iOS release too, e.g. broken on 17.1 but works on 17.0. I'd recommend opening a Support case as we may need to loop Apple into this one.

 

Cheers,

 

Connor

eevans33
Conversationalist

Hi

It happens on all ipads on ios 17. I have just tried updating one of the ipads to 17.1.2 (the latest available) and still the same issue. I have also re-tested on one that is on 17.0.3 and it is the same.

 

When digging around online about this issue, I  found quite a few people reporting the same Airprint problem with ios 17 when they use a VPN on their ipad or iphone, and when the VPN is turned off it is ok. Could be a similar scenario to the global proxy?:

iOS17 seems to have blown Airprint - Apple Community

 

How do I open a support case? I am using the free version of Meraki Systems Manager as it was a historical implementation.

 

Many thanks

frostluke
New here

Hi @eevans33,

 

We are having the exact same issue - narrowed down to it being the proxy that is set via Meraki MDM.

 

Turn off the proxy and the printers work fine.

 

Did you find a solution to this? As we of course, need to keep the proxy in place for our filtering/monitoring solution.

Get notified when there are additional replies to this discussion.
Welcome to the Meraki Community!
To start contributing, simply sign in with your Cisco account. If you don't yet have a Cisco account, you can sign up.