I want to hide a printer that's connected to a Centos 6 printer server to prevent it showing up on some of the other computers on the local network.
Using system-config-printer, putting the IP address of the computer that I want to hide the printer from into the Access Control window for that printer doesn't work since it apparently wants a user name, not an IP address.
How can I specify that the printer can be seen only by certain IP addresses but not others?
On 10/13/2014 2:28 PM, Frank Cox wrote:
I want to hide a printer that's connected to a Centos 6 printer server to prevent it showing up on some of the other computers on the local network.
Using system-config-printer, putting the IP address of the computer that I want to hide the printer from into the Access Control window for that printer doesn't work since it apparently wants a user name, not an IP address.
How can I specify that the printer can be seen only by certain IP addresses but not others?
what protocol(s) is this print sharing using?
On Mon, 13 Oct 2014 14:37:25 -0700 John R Pierce wrote:
what protocol(s) is this print sharing using?
Whatever the "sharing - enabled" checkbox gives me. The printer is connected to the print server with a USB cable so there's nothing special on that end.
On 10/13/2014 2:53 PM, Frank Cox wrote:
On Mon, 13 Oct 2014 14:37:25 -0700 John R Pierce wrote:
what protocol(s) is this print sharing using?
Whatever the "sharing - enabled" checkbox gives me. The printer is connected to the print server with a USB cable so there's nothing special on that end.
not having ever used anything on linux thats enabled with a checkbox, its hard to say. are the printer clients MS Windows or Unix/Linux ? If they are Linux do they connect with CUPS or LPR or what?
On Mon, 13 Oct 2014 15:04:10 -0700 John R Pierce wrote:
not having ever used anything on linux thats enabled with a checkbox,
Type "system-config-printer" at a root prompt.
Then right-click on the printer that you want to look at, click on "Properties" - "Policies"
State: Enabled <check> Accepting jobs <check> Shared <check>
The Shared checkbox is what allows the other machines on the network to see that printer.
its hard to say. are the printer clients MS Windows or Unix/Linux ?
Both client and server run Centos 6.
If they are Linux do they connect with CUPS or LPR or what?
The Centos default printer setup is cups.
All of the shared printers that are connected to the print server machine just show up by magic when I run the system-config-printer command on the client machines.
My objective is to make one of those printers disappear on some of the client machines, without making it disappear on the other client machines.
On 10/13/2014 3:15 PM, Frank Cox wrote:
If they are Linux do they connect with CUPS or LPR or what?
The Centos default printer setup is cups.
All of the shared printers that are connected to the print server machine just show up by magic when I run the system-config-printer command on the client machines.
My objective is to make one of those printers disappear on some of the client machines, without making it disappear on the other client machines.
ok, thats probably via the CUPS Browsing protocol, https://www.cups.org/documentation.php/doc-1.4/spec-browsing.html
ouch. CUPS printers are announced with UDP broadcasts. thats no fun to filter, since the one packet is sent to ALL stations at the same time. you could filter it at the client, but not at the server. its udp port 631 by default.
On Mon, Oct 13, 2014 at 03:28:33PM -0600, Frank Cox wrote:
I want to hide a printer that's connected to a Centos 6 printer server to prevent it showing up on some of the other computers on the local network.
Using system-config-printer, putting the IP address of the computer that I want to hide the printer from into the Access Control window for that printer doesn't work since it apparently wants a user name, not an IP address.
How can I specify that the printer can be seen only by certain IP addresses but not others?
you can choose to share it or not, but that's probabaly all or nuttin.
If you're smarter than I am (not to say, more ambitious) you could probably add some firewall rules to do the trick.