User's Manual

Frequently Asked Questions

I can’t find my printer. What is the problem?

AirPrint requires that devices are discoverable via the Bonjour protocol. Bonjour is mDNS based, and in

some networks mDNS traffic is not allowed to be passed across subnets. In these cases, a device will only

be discoverable if the iOS device and the AirPrint-capable Printer or Multifunction device are on the same

subnet. Currently Apple does not allow for manual entry of IP addresses on the iOS device side to work

around this issue. If your device is not being discovered, check with your IT administrator to ensure that

mDNS traffic is not being filtered.

Does AirPrint require both devices to be wireless capable?

No, wireless is not required on both devices. All iOS devices will be using wireless but there is no requirement

for a printer or MFD to be wirelessly-enabled. What does need to happen, though, is that the wired and

wireless segments of the network need to be bridged and, as noted before, mDNS traffic needs to be

routed between them.

I only see a few printer features in the AirPrint dialog. Why?

The IPP 2.0 specification provides a large list of supported attributes and functions but currently Apple only

provides a limited subset of features from within iOS. As the AirPrint feature grows and evolves, users can

expect to see additional device settings and capability within the print dialogs. For the time being, though,

only a small number is available.

I’m looking for AirPrint jobs in my accounting records, but I don’t see any. Why not?

Job Accounting is not supported by Xerox devices over AirPrint, and Apple devices do not support Job

Accounting at this time. If Job Accounting is enabled at the Xerox device, attempting to send a print job via

AirPrint will fail and generate an error sheet specifying that accounting codes are missing and are required

to print. The only workaround is to set up Job Accounting exceptions via the web UI.

Reference Information

About AutoIP and mDNS

All devices on a TCP/IP network must have a unique address, much as a house on a city street needs a

unique address so that mail and individuals can find it. AutoIP provides a mechanism to allow multiple

devices on the same network to acquire addresses within a specified reachable range (network or subnet)

and to ensure that no two devices have the same address on that network (conflict resolution.) In many

networks there exists infrastructure and services to provide this function (namely DHCP), but for smaller

networks and homes, DHCP servers usually are not present. There is no need to worry, however, if you don’t

have a DHCP server, since Bonjour and AutoIP will take care of this for you.

This brings up the concept of networks and subnets specifically. A subnet is a “group” of devices that all

belong to the same range of addresses, and in networking terms are thought of as “local.” Using our

address and postal service analogy, you can think of subnets as different towns or cities. Devices that exist

in the same network range are considered local to each other and usually are easily found and able to

communicate with each other.