Andrew Watkins wrote:
> I have installed b57 and I notice client printing does not work correctly.
> I have spotted two problems when talking to my Solaris 10 server.
>
> The following setup works 100% correctly on Solaris 10 & 9 clients.
> (1) Using files display errors but works
>
The information used to determine if a remote queue is accepting doesn't
come across the wire when you query a system using rfc1179. Sometimes,
you can infer it, but not always. In the past we simply lied to the
users and told them that the queue was accepting. Perhaps we should
continue with that lie.
> (2) Using ldap display errors and fails
>
> medusa% lpstat -a
> Failed to get printer info for ps133: can't connect to spooler for ps133: No
> such file or directory
>
> medusa% lpget -n ldap ps133
> ps133:
> dn=printer-uri=ps133,ou=printers,dc=dcs,dc=bbk,dc=ac,dc=uk
> objectClass=top,printerService,printerAbstract,sunPrinter
> bsdaddr=lpserver,ps133,Solaris
> user-equivalence=true
> description=SG printer
> sun-printer-kvp=user-equivalence=true,description=SG printer
> printer-uri=ps133
>
The "printer-uri" in LDAP is likely to be the problem. Solaris Nevada
uses a
"printer-uri-supported" attribute to determine how to communicate with
the print service about a queue. There is some code that converts
"printer-uri" to "printer-uri-supported" that's likely to be causing you
some problems. If you add a "printer-uri-supported" attribute to LDAP,
with a correct printer-uri-supported value, it should work:
Ex:
# lpset -n ldap -a
printer-uri-supported=lpd://lpserver/printers/ps133#Solaris ps133
or
# lpset -n ldap -a
printer-uri-supported=ipp://lpserver/printers/ps133#Solaris ps133
( if your server is configured to accept IPP)
-Norm
