Troubleshooting Mobility Print

End users can't find any printers or "Failed to retrieve printer list" error...

First, follow these general troubleshooting steps...

- Make sure the Mobility Print server is running. Log on to the server running Mobility Print and ensure that you can log in to the admin interface http://localhost:9164/admin to confirm the service is running. Side note: We know from customer reports that two antivirus software suites disrupt the Mobility Print service. See our known issues: Trend Micro Antivirus causes Mobility Print server to go offline and Cylance Antivirus causes Mobility Print server to go offline.

- Make sure the Mobility Print server has a static IP address assigned. If things were working before and suddenly stopped,

- Unless you're using Cloud Print, ensure the client is connected to the same network as the Mobility Print server. An easy way to verify connectivity is to try navigating to the web interface of the Mobility Print server from a browser on the client (http://<server-name>:9163/setup).

- Confirm that the client meets the minimum Mobility Print system requirements. For example, Android versions earlier than 4.4 are not supported.

- Avoid special characters in printer names. Printer names that include a percentage %, plus +, or apostrophe ' sign can cause issues, so if the printer name includes one or both of these special characters, try renaming it on the server. Keep it to simple ASCII characters. Changes are visible in 5 minutes or after the Mobility Print service is restarted.

- If none of those steps resolve the issue, then you will need to know whether clients are configured to discover printers using Cloud Print or one of the discovery options (mDNS, DNS, or Known Host for the next troubleshooting steps.*

If Cloud Print is being used...

... see Troubleshooting Mobility Cloud Print.

If the discovery option is set to mDNS...

...see Printer discovery problems with mDNS.

If the discovery option is set to DNS...

...see Printer discovery problems with DNS

If the discovery option is set to Known Host...

... see Printer discovery problems with Known Host

For Chromebook troubleshooting specifically...

... see Troubleshooting Chromebook issues.

If this only happens after restricting printer access per subnet...

... see Troubleshooting restricting printer access per subnet.

If this only happens for macOS clients...

... verify that your macOS print queue Name and Description don't include any CUPS forbidden characters.

Some other symptom...

'Invalid username or password' when logging in...

... see "Invalid Username or Password" when users log into Mobility Print .

The Mobility Print server is stuck 'discovering your printers'...

... see Mobility Print not able to discover printers.

For other Chromebook problems...

... see Troubleshooting Chromebook issues.

If the Windows client runs but no printer is visible afterward...

... see Printers disappear after running the Windows Mobility Print installer.

If jobs aren't printing or are being tracked as the wrong user...

... see Troubleshooting missing print jobs.

If Mobility Print is not able to import a large number of printers...

... have a look at this article for some help on how to Troubleshooting large-scale import of printers into PaperCut Mobility Print on Linux.

My problem isn't listed...

... take a screenshot of the error or symptom and follow the steps to collect the Mobility Print logs for troubleshooting to share with your PaperCut support contact.