Conference 7.286::postscript_printing

    Anyone using the lat via unix or ultrix? I've experienced soem of the
    same problems listed although I get no data/connection to the ln17ps
    at all. I can connect via ncp to the ln17 and check out port info
    etc... Which suggests its on the net. But from unix/ultrix AND VMS
    nothing is connecting to the printer.
    
    I've verified setup, groups codes (set to 0 on the ln17) etc..
    still nothing even attempts to connect.
    
    I can include more info but my setup has been verified by several
    people and since I'm not getting *anything* on the printer display
    other than ready/idle its seems that the LAT protocal on the ln17
    isn't even functioning.
    
    I reallyt need some UNIX advice since VMS is not relevant for this
    printer.
    
    Thanks for any help
    -Dave
    

    Dave,
    
    	Have you  gone through the normal troubleshooting steps listed in
    the LN17ps manual? Starting on page 6-3 in the LN17ps DNIC
    configuration guide is the lat setup for the printer.
    
    1.) ncp>connect via <circuit> phys addr 00-00-c9-xx-xx-xx (address of
    	printer)
    2.) at the # prompt, type "access" then enter.
    3.) enter your user name
    4.) at the Local> prompt type "su"
    5.) enter the password, which is "system"
    6.) issue the following commands at the local prompt:
    Local> change server groups 0-255 enabled
    Local> change port 1 authorize groups 0-255
    
    7.) hit <control-D> to exit.
    
    
    Then to set up a LAT port to the printer, do the following:
    
    $ run sys$system:latcp
    
    Latcp> create port lta###: /log     (where ### is a lat device number
    not used)
    
    Latcp> set port lta###: /application /node=DNExxxxxx /port=PORT_1
    
            (where xxxxxx is the last 6 char of the printer hardware
    	     address)
            (also case sensitive on the /node and /port)
    
    Latcp>exit
    
    Then verify that the port is actually talking to the printer by
    copying a simple postscript file to the  lat port number.
    
    	$ copy simple.ps lat###:
    
    If the copy command works without any errors then the lat port is
    communicating with the printer. If you get a comm error then check all
    the above. This would be simular to lat under UNIX.
    
    Renis

Also note that sometimes the printer's node name does not begin with DNE, but
XNE.  You can see what your printer's name is by printing a configuration sheet
and checking the Novell PSERVER name.

Paul

    Renis,
    
      Setting the groups 0-255 seems to have done the trick! I was
    under the impression that groups set to 0 meant ALL groups, but
    apparently not. However, curiously enough, from VMS I get output
    but the data is corrupted somehow. I get a single number on the printed
    out page. I have seen that discussed in a previous note and will
    go back and implement the fix (maybe).
    
     But from DUNIX and Ultrix it works just fine! With NO tweaking
    of software. Since VMS is not relevant in the UNIX enviorment, I'm
    up and running now.
    
    THANK YOU VERY MUCH for your help, I really appreciate it!!
    
    -Dave
    

    Dave,
    
    	If you are using DCPS on the VMS side and don't have the printer
    language set to postscript, ie automatic mode. Then you will need to
    set the following logical on the VMS system:
    
    $ define/system dcps$queue-name_no_sync 1
    
    This will allow DCPS to print to the printer with the language in
    autosense mode.
    
    Renis