Hello, On Mar 13 17:05 Rainer Lay wrote (shortened):
Johannes Meixner schrieb:
Try to circumvent it and use plain TCP socket connection, see the Suse Linux 10.0 Administration/Reference Manual file:///usr/share/doc/manual/suselinux-manual_en/manual/sec.drucken.prob.html "Troubleshooting a Network Printer or Print Server Box"
I tried the plain TCP socket connection, with port 35 or port 9100 - nothing happend (YaST).
Did you try out "nmap" which is described in the Suse Linux 10.0 Administration/Reference Manual file:///usr/share/doc/manual/suselinux-manual_en/manual/sec.drucken.prob.html "Troubleshooting a Network Printer or Print Server Box" If you must use the LPD protocol, try out various settings of the CUPS lpd backend, see the "CUPS Software Administrators Manual" "Configuring LPD Printing Options": http://localhost:631/sam.html#LPD_OPTIONS In particular try the "format" options (but the default "format=l" which is raw output should be exactly what you need).
In the manual, there is only a description for windows - without any queue specification.
Good manual ;-)
I also tried echo -e "\004lpt1" | netcat -w 5 -p 722 192.168.2.1 515 with several queue names. All of them returned: lpd: invalid printer even the working queue lpt!
Good LPD implementation ;-) By the way: Those LPD implementations normally accept any queue name and use whatever fallback queue if a non-existent queue name is used. I.e. a DeviceURI lpd://192.168.2.1/foo should also print. Kind Regards Johannes Meixner -- SUSE LINUX Products GmbH, Maxfeldstrasse 5 Mail: jsmeix@suse.de 90409 Nuernberg, Germany WWW: http://www.suse.de/