Stefan Parvu wrote:
> Thanks a lot for answer. Actually my problem was a bit different.
>
> The printer is a resource part of a NT domain. It is however a network printer
> which can be accessed via \\server\printerA name. If I try to enable this on 
> my
> Nevada build40(printmgg + samba) as you have described nothing works.
>   
One thing that may be of some help would be to turn on lpr.debug in
the syslog and take a look at the data generated from the uri interface
script.  You might also try to send a file from your Solaris system using
smbspool directly to see what, if any, problems it is running into.
Ex:

This printer doesn't exist.
> snappy% env DEVICE_URI="smb://192.168.0.145/oops" smbspool "foo-12" 
> "jacobs" "title" 1 "" /etc/motd
> ERROR: No ticket cache found for userid=24656
> ERROR: Can not get the ticket cache for jacobs
> ERROR: Tree connect failed (NT_STATUS_BAD_NETWORK_NAME)
> ERROR: Tree connect failed (NT_STATUS_BAD_NETWORK_NAME)
> ERROR: Unable to connect to CIFS host, will retry in 60 seconds...
> ^C
> snappy%
This one printed
> snappy% env DEVICE_URI="smb://192.168.0.145/hp4650" smbspool "foo-12" 
> "jacobs" "title" 1 "" /etc/motd
> ERROR: No ticket cache found for userid=24656
> ERROR: Can not get the ticket cache for jacobs


> These are my entries in printers.conf after adding a smb:// printer:
>
> canon:\
>         :bsdaddr=localhost,canon,Solaris:
> _default:\
>         :use=canon:
>
>
>
> However to make the things working I would need to fix my printers.conf like:
>
> canon:\
>         :bsdaddr=server,printerA,Solaris:
> _default:\
>         :use=canon:
>
>
> But this way I would say Im printing directly to that server. 
>   
You are correct, this is going directly to the Windows system (via BSD 
protocol),
which will work if the data you are sending the printer is in a printer 
ready
format.  Windows will not take remote print jobs and convert them into a 
printer
ready format for you.  It assumes that the client has done that.  In our 
case, we rely
on the local LP service to do this.  This is why we configure a local 
queue for windows
hosted printers.

       -Norm

Reply via email to