Enabling native iOS printing over multiple VLANs or subnets - c06617191
PrinterOn provides native iOS printing support in a similar way to traditional AirPrint , via mDNS . The main difference is that the device making the network broadcast is a Windows application called the Print Delivery Gateway (PDG) instead of a real printer. The mDNS broadcast of the printer information is done to the local VLAN where the PDG is deployed, this is no different than how traditional AirPrint works.
To provide access over multiple VLANs or subnets, there are 3 main options, listed in order of preference:
Automatic Printer Discovery
If the preference is to have the printers broadcast to users using just the Print Delivery Gateway application, a PDG would need to be deployed into each VLAN where users would require the printer to be broadcast. The PDG would be configured to route jobs back to the server where the Central Print Services component has been installed so communication from the PDG back to the central server would be required over port 443.
The limitation is in the mDNS broadcast, it is intended for small networks. and what the customer wants to do is not how it’s intended to be used, but there are some options.
If a Mobile Device Management (MDM) solution is in place, they could push an AirPrint configuration to the user’s device which would route their requests to a single PDG inside the customer network. Alternately, they could provide an AirPrint configuration file for users to install manually. There are details on this in the Print Delivery Gateway Administrator Guide at https://printeron.com/support/documentation
Review the section titled “Using the PDG for iOS devices without Bonjour”. HP would support these configurations and help if any assistance was required to get it working.
- mDNS forwarding
It’s possible to do mDNS forwarding through a router or firewall application, but this is not an action that HP supports officially. Some customers have done this in the past and been successful. It's important to note that mDNS was not built to bridge VLANs and therefore the stability of this workaround is unknown. HP can provide some basic information related to ports and resource paths, and the customer would then need to investigate and implement on their own.