Hi. Did that and this: The following are the basics to get you started Add to /etc/cups/cupsd.conf on your Server in the appropiate places ---- BROWSING SECTION----- BrowseAddress 192.168.2.255 BrowseAllow 192.168.2.* ------ SECURITY SECTION ------ <Location /> Order Deny,Allow Deny From All Allow From 127.0.0.1 Allow From 127.0.0.2 Allow From 192.168.2.* </Location> and now the client says that it can see the server but no queue appear in the printer dialogue on the server and there are no errors in /var/log/messages on either box. Any ideas? THanks, Steve. ---------- Forwarded Message ---------- Subject: Re: [SLE] cups network printer Date: Mon, 30 Dec 2002 07:38:28 +0000 From: Linux World 999 <linuxworld999@yahoo.co.uk> To: suse-linux-e@suse.com On Sunday 29 December 2002 20:09, Graham Smith wrote: <snip>
In /etc/cups/client.conf on ALL your client machines add ServerName 192.168.2.1
Even if this modification is not done, the cups printer will be accessible. -- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com -------------------------------------------------------
On Tue, 31 Dec 2002 05:35, fsanta wrote:
Hi. Did that and this: The following are the basics to get you started Add to /etc/cups/cupsd.conf on your Server in the appropiate places ---- BROWSING SECTION----- BrowseAddress 192.168.2.255 BrowseAllow 192.168.2.*
------ SECURITY SECTION ------ <Location /> Order Deny,Allow Deny From All Allow From 127.0.0.1 Allow From 127.0.0.2 Allow From 192.168.2.* </Location>
and now the client says that it can see the server but no queue appear in the printer dialogue on the server and there are no errors in /var/log/messages on either box. Any ideas? THanks, Steve.
Steve, Cups is not setup to send messages to the /var/log/messages fil, it uses its own. Have a look at /var/log/cups/ directory there are a number of log files there for cups. The main two I think off hand to look at are access_log and error_log, on both the server and the client. They will probably give you more info relating to the problem. I've been up all night so forgive me for not providing you with an answer as I can't think of anything off-hand. -- Regards, Graham Smith ---------------------------------------------------------
On Monday 30 December 2002 19:49, Graham Smith wrote:
On Tue, 31 Dec 2002 05:35, fsanta wrote:
Hi. Did that and this: The following are the basics to get you started Add to /etc/cups/cupsd.conf on your Server in the appropiate places ---- BROWSING SECTION----- BrowseAddress 192.168.2.255 BrowseAllow 192.168.2.*
------ SECURITY SECTION ------ <Location /> Order Deny,Allow Deny From All Allow From 127.0.0.1 Allow From 127.0.0.2 Allow From 192.168.2.* </Location>
and now the client says that it can see the server but no queue appear in the printer dialogue on the server and there are no errors in /var/log/messages on either box. Any ideas? THanks, Steve.
Steve,
Cups is not setup to send messages to the /var/log/messages fil, it uses its own.
Have a look at /var/log/cups/ directory there are a number of log files there for cups. The main two I think off hand to look at are access_log and error_log, on both the server and the client. They will probably give you more info relating to the problem.
I've been up all night so forgive me for not providing you with an answer as I can't think of anything off-hand.
Hi No problem. It's for me to thank you for trying to help. Here are the messages from /var/log/cups/access_log after a sucessful print job from the server and an unsuccessful one from the client (the server 192.168.2.1 is called altea1 and the client 192.168.2.2 altea2): altea1 - - [30/Dec/2002:01:40:01 +0100] "POST /printers/ HTTP/1.1" 403 0 altea1 - - [30/Dec/2002:01:40:05 +0100] "POST / HTTP/1.1" 403 0 altea1 - - [30/Dec/2002:01:40:05 +0100] "GET /printers/lp.ppd HTTP/1.1" 403 0 127.0.0.1 - - [30/Dec/2002:01:40:06 +0100] "POST /printers/lp HTTP/1.1" 200 17063 127.0.0.1 - - [30/Dec/2002:01:40:08 +0100] "POST /printers/ HTTP/1.1" 200 224 127.0.0.1 - - [30/Dec/2002:01:40:08 +0100] "POST /classes/ HTTP/1.1" 200 224 127.0.0.1 - - [30/Dec/2002:01:40:08 +0100] "POST /printers/ HTTP/1.1" 200 112 altea1 - - [30/Dec/2002:01:40:09 +0100] "POST / HTTP/1.1" 403 0 192.168.2.2 - - [30/Dec/2002:12:46:44 +0100] "POST / HTTP/1.1" 200 140 192.168.2.2 - - [30/Dec/2002:12:46:45 +0100] "POST / HTTP/1.1" 200 140 192.168.2.2 - - [30/Dec/2002:12:46:45 +0100] "POST /printers/unexistent HTTP/1.1" 200 187 192.168.2.2 - - [30/Dec/2002:13:48:35 +0100] "POST / HTTP/1.1" 200 140 192.168.2.2 - - [30/Dec/2002:13:48:35 +0100] "POST / HTTP/1.1" 200 140 Does this mean anything? Steve.
On Tue, 31 Dec 2002 07:48, fsanta wrote:
On Monday 30 December 2002 19:49, Graham Smith wrote:
On Tue, 31 Dec 2002 05:35, fsanta wrote:
Hi. Did that and this: The following are the basics to get you started Add to /etc/cups/cupsd.conf on your Server in the appropiate places ---- BROWSING SECTION----- BrowseAddress 192.168.2.255 BrowseAllow 192.168.2.*
------ SECURITY SECTION ------ <Location /> Order Deny,Allow Deny From All Allow From 127.0.0.1 Allow From 127.0.0.2 Allow From 192.168.2.* </Location>
and now the client says that it can see the server but no queue appear in the printer dialogue on the server and there are no errors in /var/log/messages on either box. Any ideas? THanks, Steve.
Steve,
Cups is not setup to send messages to the /var/log/messages fil, it uses its own.
Have a look at /var/log/cups/ directory there are a number of log files there for cups. The main two I think off hand to look at are access_log and error_log, on both the server and the client. They will probably give you more info relating to the problem.
I've been up all night so forgive me for not providing you with an answer as I can't think of anything off-hand.
Hi No problem. It's for me to thank you for trying to help. Here are the messages from /var/log/cups/access_log after a sucessful print job from the server and an unsuccessful one from the client (the server 192.168.2.1 is called altea1 and the client 192.168.2.2 altea2):
altea1 - - [30/Dec/2002:01:40:01 +0100] "POST /printers/ HTTP/1.1" 403 0 altea1 - - [30/Dec/2002:01:40:05 +0100] "POST / HTTP/1.1" 403 0 altea1 - - [30/Dec/2002:01:40:05 +0100] "GET /printers/lp.ppd HTTP/1.1" 403 0 127.0.0.1 - - [30/Dec/2002:01:40:06 +0100] "POST /printers/lp HTTP/1.1" 200 17063 127.0.0.1 - - [30/Dec/2002:01:40:08 +0100] "POST /printers/ HTTP/1.1" 200 224 127.0.0.1 - - [30/Dec/2002:01:40:08 +0100] "POST /classes/ HTTP/1.1" 200 224 127.0.0.1 - - [30/Dec/2002:01:40:08 +0100] "POST /printers/ HTTP/1.1" 200 112 altea1 - - [30/Dec/2002:01:40:09 +0100] "POST / HTTP/1.1" 403 0 192.168.2.2 - - [30/Dec/2002:12:46:44 +0100] "POST / HTTP/1.1" 200 140 192.168.2.2 - - [30/Dec/2002:12:46:45 +0100] "POST / HTTP/1.1" 200 140 192.168.2.2 - - [30/Dec/2002:12:46:45 +0100] "POST /printers/unexistent HTTP/1.1" 200 187 192.168.2.2 - - [30/Dec/2002:13:48:35 +0100] "POST / HTTP/1.1" 200 140 192.168.2.2 - - [30/Dec/2002:13:48:35 +0100] "POST / HTTP/1.1" 200 140
Does this mean anything? Steve.
Just a thought, I had a problem with CUPS last night when I was changing Domain names and IP numbers around. On the print manager on KDE Control Centre check the "Configure Manager" (blue square thingy) on the top tool bar (top right hand side). Select it and have a look at the setting for CUPS server. Make sure it is pointing to the correct Host address. On one of the systems it had the wrong domain name in it and refused to print with an error message. This setting is independant of the /etc/cups settings. Had me snookered for a while. THe funny thing was that it would see the printers and print if I set it to a generic UNIX LPD system instead of cups. THe other thing to try is to print a small text file from the command line on the client machine. This sort of works independantly to the KDE printing system. e.g. lpr -P <printer> /etc/hosts You may have to increase the debugging to get any meaningful data in the log files. /etc/cups/cupsd.conf BTW, I'm definately going to bed soon. -- Regards, Graham Smith ---------------------------------------------------------
participants (2)
-
fsanta -
Graham Smith