Hi all, I have FC4 up and running with cupsd running. A printer is installed and I have added the line 'Allow From 192.168.14.*' just in front of the <location /> section marker of the cupsd.conf file in /etc/cups and restarted cups successfully.
I have disabled the firewall. Yet when trying to print from another FC4 box on the 192.168.14.0 subnet, the connection is refused by the FC4 box hosting the cups server installation.
Any ideas?
TIA
Bob
On 12/23/05, Bob Hartung rwhart@mchsi.com wrote:
Hi all, I have FC4 up and running with cupsd running. A printer is installed and I have added the line 'Allow From 192.168.14.*' just in front of the <location /> section marker of the cupsd.conf file in /etc/cups and restarted cups successfully.
I have disabled the firewall. Yet when trying to print from another FC4 box on the 192.168.14.0 subnet, the connection is refused by the FC4 box hosting the cups server installation.
Any ideas?
TIA
Bob
Have you tried enabling sharing for the printer from Gnome using Desktop->System Settings->Printing ?
Yes, I have.
Bob
Kam Leo wrote:
On 12/23/05, Bob Hartung rwhart@mchsi.com wrote:
Hi all, I have FC4 up and running with cupsd running. A printer is installed and I have added the line 'Allow From 192.168.14.*' just in front of the <location /> section marker of the cupsd.conf file in /etc/cups and restarted cups successfully.
I have disabled the firewall. Yet when trying to print from another FC4 box on the 192.168.14.0 subnet, the connection is refused by the FC4 box hosting the cups server installation.
Any ideas?
TIA
Bob
Have you tried enabling sharing for the printer from Gnome using Desktop->System Settings->Printing ?
On 12/23/05, Bob Hartung rwhart@mchsi.com wrote:
Yes, I have.
Bob
Kam Leo wrote:
On 12/23/05, Bob Hartung rwhart@mchsi.com wrote:
Hi all, I have FC4 up and running with cupsd running. A printer is installed and I have added the line 'Allow From 192.168.14.*' just in front of the <location /> section marker of the cupsd.conf file in /etc/cups and restarted cups successfully.
I have disabled the firewall. Yet when trying to print from another FC4 box on the 192.168.14.0 subnet, the connection is refused by the FC4 box hosting the cups server installation.
Any ideas?
TIA
Bob
Have you tried enabling sharing for the printer from Gnome using Desktop->System Settings->Printing ?
Did you specify a single or a range of addresses for hosts which are allowed to share the printer? And did you save the settings before you exited the utility?
Kam According to the docs I reviewed
Allow From 192.168.14.*
should allow connections from the entire 192.168.14.xxx subnet. The file was saved, and /etc/init.d/cups restart done with [OK] as result. This should work. I will retry with a specific IP address.
Tnx,
Bob
Kam Leo wrote:
On 12/23/05, Bob Hartung rwhart@mchsi.com wrote:
Yes, I have.
Bob
Kam Leo wrote:
On 12/23/05, Bob Hartung rwhart@mchsi.com wrote:
Hi all, I have FC4 up and running with cupsd running. A printer is installed and I have added the line 'Allow From 192.168.14.*' just in front of the <location /> section marker of the cupsd.conf file in /etc/cups and restarted cups successfully.
I have disabled the firewall. Yet when trying to print from another FC4 box on the 192.168.14.0 subnet, the connection is refused by the FC4 box hosting the cups server installation.
Any ideas?
TIA
Bob
Have you tried enabling sharing for the printer from Gnome using Desktop->System Settings->Printing ?
Did you specify a single or a range of addresses for hosts which are allowed to share the printer? And did you save the settings before you exited the utility?
On 12/23/05, Bob Hartung rwhart@mchsi.com wrote:
Kam According to the docs I reviewed
Allow From 192.168.14.*
should allow connections from the entire 192.168.14.xxx subnet. The file was saved, and /etc/init.d/cups restart done with [OK] as result. This should work. I will retry with a specific IP address.
Tnx,
Bob
That is not the way cups wants it specified. I used Desktop->System Settings->Printing and modified the sharing setting for my laserjet4 for the 192.168.1* subnet. Here's the section of /etc/cups/cupsd.conf after I clicked the Apply button:
# sudo cat /etc/cups/cupsd.conf
[snip]
<Location /printers/laserjet4> Order Deny,Allow Deny From All Allow From 127.0.0.1 AuthType None Allow from 192.168.1.0/255.255.255.0
On Fri, 2005-12-23 at 21:15 -0600, Bob Hartung wrote:
I have FC4 up and running with cupsd running. A printer is installed and I have added the line 'Allow From 192.168.14.*' just in front of the <location /> section marker of the cupsd.conf file in /etc/cups and restarted cups successfully.
I'm not sure if you can do IP wildcarding in that style, the example template in the configuration file is a bit vague (using nnn.* etc.), although one example (nnn.nnn.nnn.nnn/nnn.nnn.nnn.nnn) does look like they're talking about numerical IP addresses rather than named addresses (DNS), it doesn't explicitly detail what they mean. There are other ways of mentioning address ranges, or interfaces, as shown in the example configuration file, that may be more practical.
The other thing that springs to mind is that you've said you've done it just in front of the <Location /> marker. Do you really mean inside of it?
Mine looks like:
<Location /> Order Deny,Allow Deny From All Allow From 127.0.0.1 Allow From @LOCAL </Location>
You also need to do something similar with the Listen directive. There's no point allowing connections from your LAN if CUPS isn't listening for connections from it.
On Saturday 24 December 2005 01:24, Tim wrote:
On Fri, 2005-12-23 at 21:15 -0600, Bob Hartung wrote:
I have FC4 up and running with cupsd running. A printer is installed and I have added the line 'Allow From 192.168.14.*' just in front of the <location /> section marker of the cupsd.conf file in /etc/cups and restarted cups successfully.
I'm not sure if you can do IP wildcarding in that style, the example template in the configuration file is a bit vague (using nnn.* etc.), although one example (nnn.nnn.nnn.nnn/nnn.nnn.nnn.nnn) does look like they're talking about numerical IP addresses rather than named addresses (DNS), it doesn't explicitly detail what they mean. There are other ways of mentioning address ranges, or interfaces, as shown in the example configuration file, that may be more practical.
The other thing that springs to mind is that you've said you've done it just in front of the <Location /> marker. Do you really mean inside of it?
Mine looks like:
<Location /> Order Deny,Allow Deny From All Allow From 127.0.0.1 Allow From @LOCAL </Location>
You also need to do something similar with the Listen directive. There's no point allowing connections from your LAN if CUPS isn't listening for connections from it.
-- Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.
You should probably try using 192.168.14.0/24 instead of the wildcard also.
Tom
Got it fixed. Thanks to all who responded.
Bob
Thomas Taylor wrote:
On Saturday 24 December 2005 01:24, Tim wrote:
On Fri, 2005-12-23 at 21:15 -0600, Bob Hartung wrote:
I have FC4 up and running with cupsd running. A printer is installed and I have added the line 'Allow From 192.168.14.*' just in front of the <location /> section marker of the cupsd.conf file in /etc/cups and restarted cups successfully.
I'm not sure if you can do IP wildcarding in that style, the example template in the configuration file is a bit vague (using nnn.* etc.), although one example (nnn.nnn.nnn.nnn/nnn.nnn.nnn.nnn) does look like they're talking about numerical IP addresses rather than named addresses (DNS), it doesn't explicitly detail what they mean. There are other ways of mentioning address ranges, or interfaces, as shown in the example configuration file, that may be more practical.
The other thing that springs to mind is that you've said you've done it just in front of the <Location /> marker. Do you really mean inside of it?
Mine looks like:
<Location /> Order Deny,Allow Deny From All Allow From 127.0.0.1 Allow From @LOCAL </Location>
You also need to do something similar with the Listen directive. There's no point allowing connections from your LAN if CUPS isn't listening for connections from it.
-- Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.
You should probably try using 192.168.14.0/24 instead of the wildcard also.
Tom
On 12/25/05, Bob Hartung rwhart@mchsi.com wrote:
Got it fixed. Thanks to all who responded.
Bob
Thomas Taylor wrote:
On Saturday 24 December 2005 01:24, Tim wrote:
On Fri, 2005-12-23 at 21:15 -0600, Bob Hartung wrote:
I have FC4 up and running with cupsd running. A printer is installed and I have added the line 'Allow From 192.168.14.*' just in front of the <location /> section marker of the cupsd.conf file in /etc/cups and restarted cups successfully.
I'm not sure if you can do IP wildcarding in that style, the example template in the configuration file is a bit vague (using nnn.* etc.), although one example (nnn.nnn.nnn.nnn/nnn.nnn.nnn.nnn) does look like they're talking about numerical IP addresses rather than named addresses (DNS), it doesn't explicitly detail what they mean. There are other ways of mentioning address ranges, or interfaces, as shown in the example configuration file, that may be more practical.
The other thing that springs to mind is that you've said you've done it just in front of the <Location /> marker. Do you really mean inside of it?
Mine looks like:
<Location /> Order Deny,Allow Deny From All Allow From 127.0.0.1 Allow From @LOCAL </Location>
You also need to do something similar with the Listen directive. There's no point allowing connections from your LAN if CUPS isn't listening for connections from it.
-- Don't send private replies to my address, the mailbox is ignored. I read messages from the public lists.
You should probably try using 192.168.14.0/24 instead of the wildcard also.
Tom
For the record: What was the fix that worked for you?
I did it the easy way I deleted the printers that I installed via http://localhost:631 and then went th the graphical installer under system settings->printers.
Set up the printer the server, shared it then used it from the browse window under system settings->printers. Far too easy. I did not use this initially because of a prior experience.
Bob <snip>
For the record: What was the fix that worked for you?
-
Bob Hartung -
Kam Leo -
Thomas Taylor -
Tim