cups server on lenny system no accessible

2008-01-01 Thread Rainer Dorsch
Hello,

I recently replace an etch system with a cups server running with a lenny 
system. In the cupsd.conf I modified this part:

# Show shared printers on the local network.
Browsing On
BrowseProtocols cups
BrowseAddress 192.168.1.255
BrowseAllow 192.168.1.*
BrowseInterval 30
BrowsePort 631
BrowseOrder allow,deny
#BrowseAllow all

# Default authentication type, when authentication is required...
DefaultAuthType Basic

# Restrict access to the server...
Location /
  Order allow,deny
  Allow localhost
  Allow @LOCAL
  # rd, 20080101
  Allow 192.168.1.*
/Location


A Debian etch system is a cups client only and uses the directive

ServerName 192.168.1.10

in its client.conf. The 192.168.1.10 is the server IP and works well e.g. with 
a standard ssh connection (i.e I have no basic networking problem).

The client cannot access the server and there is not even a message in the 
server logfile. The client gets an Unable to connect to server. None of the 
systems has a firewall running.

In the server logfile I see the line

I [01/Jan/2008:23:39:05 +0100] Listening to 127.0.0.1:631 (IPv4)

but I miss that the server is listening to the network interface.

Does anybody understand what is going wrong?

Thanks,
Rainer

The server /var/log/cups/error.log:

I [01/Jan/2008:23:39:05 +0100] Scheduler shutting down normally.
D [01/Jan/2008:23:39:05 +0100] Saving remote.cache...
I [01/Jan/2008:23:39:05 +0100] Saving job cache 
file /var/cache/cups/job.cache...
I [01/Jan/2008:23:39:05 +0100] Listening to 127.0.0.1:631 (IPv4)
I [01/Jan/2008:23:39:05 +0100] Listening to /var/run/cups/cups.sock (Domain)
I [01/Jan/2008:23:39:05 +0100] Sending browsing info to 192.168.1.255:631 
(IPv4)
D [01/Jan/2008:23:39:05 +0100] cupsdDenyIP(loc=0x80b0f50(/), address=0:0:0:0, 
netmask=0:0:0:0)
I [01/Jan/2008:23:39:05 +0100] Loaded configuration 
file /etc/cups/cupsd.conf
I [01/Jan/2008:23:39:05 +0100] Using default TempDir of /var/spool/cups/tmp...
I [01/Jan/2008:23:39:05 +0100] Configured for up to 100 clients.
I [01/Jan/2008:23:39:05 +0100] Allowing up to 100 client connections per host.
I [01/Jan/2008:23:39:05 +0100] Using policy default as the default!
I [01/Jan/2008:23:39:05 +0100] Full reload is required.
I [01/Jan/2008:23:39:05 +0100] Loaded MIME database 
from '/usr/share/cups/mime:/etc/cups': 36 types, 40 filters...
D [01/Jan/2008:23:39:05 +0100] Loading printer hplj6p...
I [01/Jan/2008:23:39:05 +0100] Loading job cache 
file /var/cache/cups/job.cache...
D [01/Jan/2008:23:39:05 +0100] [Job 3] Loading from cache...
D [01/Jan/2008:23:39:05 +0100] [Job 4] Loading from cache...
D [01/Jan/2008:23:39:05 +0100] [Job 5] Loading from cache...
D [01/Jan/2008:23:39:05 +0100] [Job 6] Loading from cache...
D [01/Jan/2008:23:39:05 +0100] [Job 7] Loading from cache...
D [01/Jan/2008:23:39:05 +0100] [Job 8] Loading from cache...
D [01/Jan/2008:23:39:05 +0100] [Job 9] Loading from cache...
D [01/Jan/2008:23:39:05 +0100] [Job 10] Loading from cache...
D [01/Jan/2008:23:39:05 +0100] [Job 11] Loading from cache...
D [01/Jan/2008:23:39:05 +0100] [Job 12] Loading from cache...
D [01/Jan/2008:23:39:05 +0100] [Job 13] Loading from cache...
D [01/Jan/2008:23:39:05 +0100] [Job 14] Loading from cache...
D [01/Jan/2008:23:39:05 +0100] [Job 15] Loading from cache...
D [01/Jan/2008:23:39:05 +0100] [Job 16] Loading from cache...
D [01/Jan/2008:23:39:05 +0100] [Job 17] Loading from cache...
D [01/Jan/2008:23:39:05 +0100] [Job 18] Loading from cache...
D [01/Jan/2008:23:39:05 +0100] [Job 19] Loading from cache...
D [01/Jan/2008:23:39:05 +0100] [Job 20] Loading from cache...
D [01/Jan/2008:23:39:05 +0100] [Job 21] Loading from cache...
D [01/Jan/2008:23:39:05 +0100] [Job 22] Loading from cache...
D [01/Jan/2008:23:39:05 +0100] [Job 23] Loading from cache...
I [01/Jan/2008:23:39:05 +0100] Full reload complete.
I [01/Jan/2008:23:39:05 +0100] Cleaning out old temporary files 
in /var/spool/cups/tmp...
I [01/Jan/2008:23:39:05 +0100] Listening to 127.0.0.1:631 on fd 3...
I [01/Jan/2008:23:39:05 +0100] Listening to /var/run/cups/cups.sock on fd 4...
I [01/Jan/2008:23:39:05 +0100] Resuming new connection processing...

-- 
Rainer Dorsch
Lärchenstr. 6
D-72135 Dettenhausen
07157-734133
email: [EMAIL PROTECTED]
jabber: [EMAIL PROTECTED]
GPG Fingerprint: 5966 C54C 2B3C 42CC 1F4F  8F59 E3A8 C538 7519 141E
Full GPG key: http://pgp.mit.edu/



Re: cups server on lenny system no accessible

2008-01-01 Thread Florian Kulzer
On Tue, Jan 01, 2008 at 23:50:28 +0100, Rainer Dorsch wrote:
 Hello,
 
 I recently replace an etch system with a cups server running with a lenny 
 system. In the cupsd.conf I modified this part:
 
 # Show shared printers on the local network.
 Browsing On
 BrowseProtocols cups
 BrowseAddress 192.168.1.255
 BrowseAllow 192.168.1.*
  ^^^
Does the * wildcard work in IP addresses? (I only know about its use
in hostnames, e.g. *.example.tld.)

I would try 192.168.1.0/8 or 192.168.1.0/255.255.255.0. In fact, as
a first test I would check if it works with BrowseAllow all.

 BrowseInterval 30
 BrowsePort 631
 BrowseOrder allow,deny
 #BrowseAllow all
 
 # Default authentication type, when authentication is required...
 DefaultAuthType Basic
 
 # Restrict access to the server...
 Location /
   Order allow,deny
   Allow localhost
   Allow @LOCAL
   # rd, 20080101
   Allow 192.168.1.*
  ^^^
  same here

 /Location
 
 
 A Debian etch system is a cups client only and uses the directive
 
 ServerName 192.168.1.10
 
 in its client.conf. The 192.168.1.10 is the server IP and works well e.g. 
 with 
 a standard ssh connection (i.e I have no basic networking problem).
 
 The client cannot access the server and there is not even a message in the 
 server logfile. The client gets an Unable to connect to server. None of the 
 systems has a firewall running.

[...]

-- 
Regards,| http://users.icfo.es/Florian.Kulzer
  Florian   |


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]



Re: cups server on lenny system no accessible

2008-01-01 Thread Florian Kulzer
On Wed, Jan 02, 2008 at 00:55:04 +0100, Florian Kulzer wrote:
 On Tue, Jan 01, 2008 at 23:50:28 +0100, Rainer Dorsch wrote:

[...]

  BrowseAllow 192.168.1.*
   ^^^
 Does the * wildcard work in IP addresses? (I only know about its use
 in hostnames, e.g. *.example.tld.)
 
 I would try 192.168.1.0/8 or 192.168.1.0/255.255.255.0. In fact, as
  ^^^
This should be 192.168.1.0/24.

 a first test I would check if it works with BrowseAllow all.

[...]

-- 
Regards,| http://users.icfo.es/Florian.Kulzer
  Florian   |


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED] 
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]