Hi Sid, Sid Boyce wrote:
Hylton Conacher (ZR1HPC) wrote: [snip]
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.. No fear, I like the way you said it. I know that by rebooting the server it would accomplish the same as rccups restart.
[snip]
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). On the client and server: # tcpdump -i eth0 16:58:12.950181 Spy.home.net.za.netbios-ns > 192.168.0.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST (DF) 16:58:14.950102 Spy.home.net.za.netbios-ns > 192.168.0.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST (DF) 16:58:14.950223 Spy.home.net.za.netbios-ns > 192.168.0.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST (DF) 16:58:16.950089 Spy.home.net.za.netbios-ns > 192.168.0.255.netbios-ns: NBT UDP PACKET(137): QUERY; REQUEST; BROADCAST (DF) 16:58:16.950257 Spy.home.net.za.netbios-dgm > 192.168.0.255.netbios-dgm: NBT UDP PACKET(138) (DF) 16:59:16.950106 Spy.home.net.za.netbios-dgm > 192.168.0.255.netbios-dgm: NBT UDP PACKET(138) (DF)
In /etc/cups/client.conf on the client, you should have a line "ServerName
" Under #ServerName myhost.domain.com in the client.conf I have: "ServerName 192.168.0.1 .." #sans quotes of course. :)
I'm thinking the '..' needs to be removed?
On the server /etc/cups/cupsd.conf "Browsing On". It is on on the server.
"rccups restart" on both boxes. Any particular order like M$? ie server first.
I'll do the server first jic.
"tail -f /var/log/messages" on both to see what requests and errors are being generated I rebooted the server, didn't log in, rebooted the client, didn't log in.
Server: Ran 'tail..' on server and repeated the 'tail' every 10 secs for approx 2 mins. Saw nothing to do with cups or communication. Did notice a message in /var/log/messages saying: 18:51 Umalusi kernel: alps.c : E7 REPORT 10 00 64 18:51 Umalusi kernel: alps.c : E6 REPORT 00 00 64 As I didn't see anything about CUPS. as well as not knowing what it means, I left it, unhappily I might add, as it mentions kernel. I ran the 'tail command on tee client after stopping the server 'tail'. Saw nothing and refreshed a few times. It would seem to my unknowledgable ass that you are trying to determine if there are broadcasts from the printer server but not from the client as if there was any from the client it would mean it also thought it was a print server. Correct? Regards -- ======================================================================== Hylton Conacher - Linux user # 229959 at http://counter.li.org Currently using SuSE 9.0 Professional with KDE 3.1 ========================================================================