There are a number of reasons that this might fail.  For the most part,
these reasons fall into the category of either transport related or
transformation related.  Other problems can occur, but there isn't
enough information in your mail to tell.  In the Windows remote printing
world, generally, print client systems generate printer ready output and
send the data on to the system with the printer so that it can forward
it to the device.  To determine if the transport to the printer is
working you can check it by hand using smbclient and smbspool. Ex:

    # smbclient -L 192.168.0.7
    Password:

    Domain=[TERMINATOR] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]

            Sharename       Type      Comment
            ---------       ----      -------
            E$              Disk      Default share
            term-hp4650     Printer   HP CLJ 4650DTN PCL 6
            IPC$            IPC       Remote IPC
            SharedDocs      Disk
            print$          Disk      Printer Drivers
            ADMIN$          Disk      Remote Admin
            C$              Disk      Default share
    session request to 192.168.0.7 failed (Called name not present)
    session request to 192 failed (Called name not present)
    Domain=[TERMINATOR] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]

            Server               Comment
            ---------            -------

            Workgroup            Master
            ---------            -------
    # smbspool smb://192.168.0.7/term-hp4650 test-1 me "title" 1 ""
    /etc/motd
    ERROR Can not get me uid
    # smbspool smb://192.168.0.7/term-hp4650 test-1 root "title" 1 ""
    /etc/motd
    ERROR: No ticket cache found for userid=0
    ERROR: Can not get the ticket cache for root
    #

The printer I printed to is "connected" to a PC running Windows XP at
192.168.0.7 and shared as "term-hp4650".  The printer handles ASCII
text, so I was able to print /etc/motd.  In spite of the error messages
generated by smbspool, it still prints just fine (both times).

As far as the transformation part goes, you will need to find a PPD
files that works with your printer.  Solaris 10 ships with a couple
thousand different PPD files and you can find more at
http://linuxprinting.org/database.html.

You might try directly connecting the printer to the Solaris host
temporarily while trying to find the best PPD file for it.

    -Norm


Eric jean wrote:
> Hello
>
> I'm on Solaris 10 and I followed the instructions written in 
> http://www.opensolaris.org/os/community/printing/faq/sol2win.htm
>
>
> but nothing is printed when I request a print job. The printed is connected 
> to a Windows PC and is shared.
> My samba sharing files works fine.
>
> Why can't I access this printer form S10?
>  
>  
> This message posted from opensolaris.org
> _______________________________________________
> printing-discuss mailing list
> printing-discuss at opensolaris.org
>   


Reply via email to