printing options

[Geert Janssens]

Hello John,

thank you for your information. Unfortunatly, I still haven't figured it 
out.

See the original message below for my interleaved reply.

John M Phillips wrote:
> First, when running under Linux, is you computers network card
> configured to the same subnet?  Type 
> 
>    /sbin/ifconfig eth0
> 
> and look for the line "inet addr: ", the address should be 
> something like 192.168.0.xxx to be on the same logical 
> subnet as the printer. If not you will need to move either the
> printer or the computers address. Most private networks
> us the subnet 192.168.1.xxx.
> 
The linux box has IP address 192.168.0.4. Definitly on the same subnet.


> Second, once you are sure that the both are on the same subnet
> try
>    ping 192.168.0.11
> 
> If ping works, then try addressing the printer using a browser 
> (mozilla, firefox, etc) with the URL 192.168.0.11.
> 
This works nicely, it gets me into a web interface to configure the 
attached print server.

> Third, as root, configure the printer with "cupsconfig".  The
> URI for the printer function may not be "http://" but
> more likely on of the following
> 	lpd://192.168.0.11/... 
> 	ipp://192.168.0.11/ipp ...        
>         socket://192.168.0.11:9100
> 
It's either a bug in CUPS or a protocol thing, but when I enter 
ipp://192.168.0.11/... CUPS automatically changes this to 
http://192.168.0.11:631/... on the printer status pages. I have tried 
both though, with the same results.

> You should be able to get the type of network printer service
> from the browser access in step 2 above.
> 
The print server is capable of dealing with several kinds of protocols:
Netware (which I disabled)
TCP/IP (which I currently use for my windows boxes, and works perfectly)
NetBEUI (which I disabled)
IPP (which I try to use in Linux)

The configuration webpage for IPP only lets me enter a printer name. If 
I set "EPSON950_IPP" as printer name, the webpages tells me the IPP URL 
is http://192.168.0.11:631/EPSON950_IPP



BUT,...

I should say, I tried several times again with different combinations, 
and there is one change: with the URI set to 
ipp://192.168.0.11/EPSON950_IPP, I no longer get the error message 
client-error-not-found. Instead each new job gets aborted immediatly. 
The status line in the cups interface indicates "No pages found". This 
happens for test pages in the cupsconfig utility as well as for a simple 
text printed from within Kate.

Trying to restart any of the aborted jobs gives an error: 
client-error-not-possible.

... Am I one step closer to or further from solving this matter ?

I don't know. Do you ?


Thanks,


Geert