Jump to content

Recommended Posts

Posted

Just testing out mobility print for onsite printing. We don't even need to enable the cloud printing option, just need to be able to print internally.

 

From a Windows client, when I run the installer it errors with, Failed to retrieve printer list

 

After playing about I just realized that if I disable the proxy settings on the Windows 11 device, the Mobility Print installer runs fine.

 

So then I thought, I could enter the IP and name of the print server into the proxy settings on the device as an exception, but that doesn't help.

 

This is similar to what I have entered into the proxy (user a proxy server, except for theses addresses....)

ip.ip.ip.*;nameofserver*

 

I also have 'Don't use proxy server for local addresses' ticked.

 

I would have thought that telling the client not to go through the proxy server for the print server, would be the same as disabling proxy completely, but apparently not.

 

Any ideas?

Posted

This is from their website, are you using mDNS?

PaperCut Mobility Print and proxy support

At the moment proxy configurations are not supported with PaperCut Mobility Print. This is not a problem if you are using the mDNS or DNS-SD discovery methods, but is a problem if you are configuring the Known Host discovery method which requires an internet connection to get the latest installers and sign profiles for iOS clients. If this is a requirement for your organization, please reach out to the support team and mention “MOB-1752” which is the code we use to track demand for this feature.

Posted

OK thanks. The thing is I am using mDNS, so should work, but also I am not trying to use the cloud option of Mobility print, which I have not enabled, which I am guessing would have issues with the Proxy, just the internal section of mobility print.

 

Currently, I am not trying to get it to work with a proxy, but now trying to workout what needs to be disabled in the proxy for it to work, if that makes sense.

 

Posted

Just read the following....

Quote

Additionally, there's a known issue with the Windows on-network Mobility Print client (version 1.0.329) that will fail to discover printers in mDNS or DNS mode if there is a local proxy detected on the client, such as the Zscaler Client Connector. The workarounds for this issue are:

Temporarily disable the proxy to complete printer discovery
Use an older version (1.0.317 and below) of the on-network Windows client

Which I will look into next week.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...