1/22/2024 0 Comments Jamf extension attributes scriptiBoss, Go Guardian, Cylance etc.) or antivirus software on your network? These kinds of software can potentially interfere with the ability of Mobility Print to reliably transmit data between the client and the server. This method was designed with managed Chromebooks in mind and uses a simple method whereby the clients will communicate directly via the Mobility server hostname/IP and can therefore negate any complex firewall restrictions or filters that might be in place on your DNS traffic in order to discover your published printers.Īre you using any kind of packet analyzing/sniffing, content filtering software (e.g. Change discovery method if using mDNS/DNS discoveryĬonsider switching your printer discovery method to Known Host. There are a few potential reasons why this can occur:ġ. If it does not, please refer to the steps here for Managed Chromebook Deployment to ensure the. Mobility server hostname or IP) matches exactly what was configured in Google Admin in the Policy for extensions section for the Mobility Print app. Find the section for Mobility Print and confirm that the policy is in place:.Login to one of the affected Chromebooks then in the browser’s address bar, type chrome://policy.Printer discovery failure with Known HostĪ quick test to verify that the Known Host configuration has been implemented correctly: In the ‘Select a destination’ Chrome print dialog, does the selected queue show with the green PaperCut icon designating a Mobility printer, and does the server in the queue name match the server name of your Mobility Print host? In the example below - DESKTOP-1TQJB6L - is the server hostname:.Confirm that the Mobility Print Chrome App appears listed in the list of Chrome extensions: On one of the affected Chromebooks, type in chrome://extensions. The expected output is a JSON formatted list of all published Mobility printers. See our Firewall rules for Mobility Print page for more detail.Ī good test is to try and access the URL: This will test that the Chromebook can access the Mobility Print server over the network and that port 9163 is accessible.Port 53 inbound and outbound UDP to/from the Mobility Print Server (DNS discovery only).Port 5353 inbound and outbound UDP to/from the Mobility Print Server (mDNS discovery only).Port 9163 (HTTP) inbound TCP to the Mobility Print Server.These are the server ports used for printer discovery by Chrome clients: If not, and those printers are located across multiple subnets, you would need to configure using either the Known Host, DNS discovery or Cloud Print methods (Known Host is the recommended method for managed Chromebooks).Ĭheck and confirm that all required ports are open on your firewall.If so, then mDNS will automatically crawl out across that subnet, find any available printers and advertise them to your Chromebooks.PRODUCTS FEATURED Troubleshooting Chromebook issues Printer discovery failureĪre those printers on the same subnet as your Chromebooks?
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |