IPP when I thought it should be SOCKETS?

Mike Murray michael.n.murray at census.gov
Fri Mar 9 12:46:13 PST 2007


It appears client.conf got clobbered, and the cups server (ServerName) was missing.  I thought cupsd.conf BrowsePoll was the pointer, learning the hard way I guess. :(

> Hi,
>   I've been having very strange printing problems and thrashing around trying to understand and correct.  The problem appears that printing from some clients does not format the ouput properly ALL the time.  e.g. landscape sometimes is or is not landscape.  I have a number of clients, some of which seem to work fine.  I've cloned the /etc/cups directory from good clients to those who don't to no avail (with appropriate mods).
>
> These systems have been running fine for a couple years, the software has not been updated lately. The problem surfaced after implemeting instances.
>
> In my thrashing around I noticed that an 'lpstat -t' returns:
>
> On problem systems:
>
>         device for queue ipp://server.xx.xx.xx:631/printers/queue
>
> and on the good systems it's:
>
> 	device for queue-name socket://queue-name.xx.xx.xx:9100
>
> The printers are indeed setup for sockets.
>
> I use BrowsePoll with IP address to the CUPS server from the client.
>
> cups-SUSE-ppds-dat-1.1.20-104.1
> cups-client-1.1.20-108.22
> cups-drivers-1.1.20-66.6
> cups-libs-1.1.20-108.22
> cups-devel-1.1.20-108.22
> cups-drivers-stp-1.1.20-66.6
> cups-1.1.20-108.22
>
> Mike M.





More information about the cups mailing list