Re: [SLE] Networking CUPS?
From: Sid Boyce (sboyce_at_blueyonder.co.uk)
Date: 04/30/05
- Previous message: Ken Schneider: "Re: [SLE] Interesting review of SuSE 9.3"
- In reply to: Hylton Conacher (ZR1HPC): "Re: [SLE] Networking CUPS?"
- Next in thread: Graham Smith: "Re: [SLE] Networking CUPS?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 30 Apr 2005 21:31:42 +0100 To: SLE <suse-linux-e@suse.com>
Hylton Conacher (ZR1HPC) wrote:
> Graham Smith wrote:
>
<STUFF DELETED>
> Thank you again Graham for looking at and editing the necessary files. I
> have reverted back to the list in case it helps others.
>
> I know, from Windows days, that the server must be booted first, ten the
> clients. I did this specifically making sure the printer initialized.
>
Dangerous! Render unto Windows what is Windows and render unto Linux
what is Linux. You can make changes to these files and "rccups restart",
please excuse if that's what you were implying..
> I figured now, with the correct conf files, it would a simple matter of
> pressing print on the Mozilla GUI on the client and the page would
> automagically eject from the printer connected to the server. Alas I was
> wrong. :(
>
> I 'checked' the client settings via the Yast printer configuration but
> all was in place. I noticed that the test failed when I tested
> connectivity to the server in Yast. Assuming it was still going to work
> I soldiered on...
>
> ...When I did press 'Print' on the Mozilla GUI I was presented with a
> KPrinter GUI that said it was initialising and that it was connected to
> Umalusi:631. NO amount of clicking on the close option or even looking
> for kprinter under a terminal screen could get the KPrinter dialogs to
> disappear. I also tried the printer manager from the printer icon on the
> task bar with the same result. It actually took 2 reboots to rid myself
> of the Kprinter dialogs.
>
> So, now what needs tweaking? Especially since I get a 100msec ping reply
> from the server when I ping 192.168.0.1 on the client side.
>
> I assume that because I am getting a reply back on the ping that the
> machines are 'talking' to one another. Where should I check error
> messages after I have tried to print?
>
> Where to next?
With "tcpdump -i eth0" or ethereal, you should periodically be seeing
ipp broadcasts for printer connections ---
21:16:46.719311 IP barrabas.site.ipp > 192.168.10.255.ipp: UDP, length: 184
#### barrabas (192.168.10.1) is broadcasting to the local network for
printer connections to port 631 (ipp).
In /etc/cups/client.conf on the client, you should have a line
"ServerName <server_name_for_192.168.0.1>"
On the server /etc/cups/cupsd.conf "Browsing On".
"rccups restart" on both boxes.
"tail -f /var/log/messages" on both to see what requests and errors are
being generated.
Regards
Sid.
-- Sid Boyce ... Hamradio License G3VBV, Keen licensed Private Pilot Retired IBM Mainframes and Sun Servers Tech Support Specialist Microsoft Windows Free Zone - Linux for all Computing Tasks -- 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
- Previous message: Ken Schneider: "Re: [SLE] Interesting review of SuSE 9.3"
- In reply to: Hylton Conacher (ZR1HPC): "Re: [SLE] Networking CUPS?"
- Next in thread: Graham Smith: "Re: [SLE] Networking CUPS?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
