Solved

Can't discover IPP Printers across subnets

Posted on 2007-04-09
2
991 Views
Last Modified: 2013-12-23
I have setup a Mac OS 10.4.9 Server (PPC) to act as a print server using IPP for our clients.  My main problems is setting up the CUPS server and switch correctly so that the IPP shared printers are easily discoverable across all of our subnets.  For example, the CUPS server is on 10.2.1.1 subnet.  I need it to also broadcast to the 10.1.1.1 subnet.  On our Dell 6024 router, I setup a port 631 UDP relay from 10.2.1.1 as the source IP address, and the destination of 255.255.255.255 so that any IPP discovery broadcast packets would go to all subnets.  

I also configured the cupsd.conf on the print server and added BrowseAddress 255.255.255.255.  On the client I modified the cupsd.conf file to have BrowseAllow 10.2.1.0/255.255.255.0.  I still cannot see any of the IPP shared printers on any other subnet other than 10.2.1.x.  Any help is greatly appreciated.
0
Comment
Question by:SKCCSUPPORT
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
2 Comments
 
LVL 11

Accepted Solution

by:
walkerke earned 500 total points
ID: 18881051
Try changing the BrowseAllow to 10.2.1.0/255.255.0.0. A subnet mask of 255.255.255.0 masks all subnets but the one the printer is a member of (10.2.1.x). A subnet mask of 255.255.0.0 will broaden the range to include 10.2.x.x.
0
 
LVL 2

Author Comment

by:SKCCSUPPORT
ID: 18885748
Walkerke,

I figured it out.  Since my systems on the 10.1.1.x subnet needed to be able to receive UDP port 631 IPP broadcast packets from my print server that is on the 10.2.1.x subnet, I had to have my clients BrowseAllow in /etc/cups/cupsd.conf set to 'BrowseAllow 10.2.1.0/255.255.255.0'.  Otherwise they don't know to look anywhere except their local subnet.  

On my Layer 3 router I needed to set the destination for UDP traffic on that port as 10.1.1.255 (the broadcast IP address for the subnet).  That way all traffic coming from my 10.2.1.1 interface would not only be broadcast to 10.2.1.255, but also 10.1.1.255 so that systems on that subnet could pick it up as well.

While your suggestion wasn't the ultimate solution, it did in a way point me in the right direction, and could help someone else who has their networks configured differently.  Therefore, you get the points.  Thanks!
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
I had an issue with InstallShield not being able to use Computer Browser service on Windows Server 2012. Here is the solution I found.
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor (https://www.paessler.com/prtg). If you're interested in additional methods for monitoring bandwidt…
In this brief tutorial Pawel from AdRem Software explains how you can quickly find out which services are running on your network, or what are the IP addresses of servers responsible for each service. Software used is freeware NetCrunch Tools (https…

729 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question