Conference jamin::pathworks32

209.0. "pwprint & dig_unix" by INTONE::BUMPUS () Mon Apr 07 1997 09:29

The following are my personal crib-notes for setting up PWPRINT
on Digital UNIX.  These notes tend to fill in alot of the missing
information from the online help and the Administrator's Guide(s).

A great deal of this comes from the PATHWORKS Information Shelf
(online) that comes with PATHWORKS 32 (v7.0).  What I've added is
some testing and troubleshooting info that came from experience.

   * What is PWPRINT and why do I need it?
   * Prepare the "Print Server" (Win95 or NT Workstation v4)
   * Prepare the Digital UNIX system
   * Test Printing
   * Troubleshooting


    PWPRINT - What does it do and why do I need it?
    ===============================================
    PWPRINT gives you, the network and unix system user, the ability
    to print a file on a printer that is attached to someone's 
    Windows95 or NT Workstation v4 computer.

    One reason to use PWPRINT is security....printing payroll checks
    or sensitive information from a Unix application to your local
    printer.  Another reason is flexibility for those PATHWORKS users
    who also use Unix and want to print files directly to their offices.


    Prepare the "Print Server" (Win95 or NT Workstation v4)
    =======================================================
    Attach a printer to the lpt1: printer port.
    Run the printer setup program (start -> settings -> printers
	-> Add Printer) and answer the questions for your printer.
    Install PATHWORKS 32 software (if you haven't already & reboot).

    On Windows95 systems:
	To ensure that the pwprint sw is running on your pc go to a 
	DOS prompt and type c:\pwprint -install  (yes, it would be
	nice if it was -start but it isn't...same thing though).
	To stop pwprint... c:\pwprint -remove  (yep, -stop ain't it).

    On NT Workstation v4 systems:
	To ensure that the pwprint sw is running on your pc go to a
	DOS prompt and type c:\net start pwprint
	To stop pwprint... c:\net stop pwprint

    By default, TCP/IP is the transport.  Yes, you can change this
	to DECnet if you want IF you installed DECnet when you
	installed PATHWORKS 32.
    Ensure that the TCP/IP transport is properly configured on your
	PC.  Check in the Network Control Panel so that there is an
	appropriate IP address set (for your pc).

    Test the local printing ability! .....
	Bring up the Notepad and enter a couple lines of characters
	then print it to the attached printer.  You must get output
	at this point before moving to the next step.


    Prepare the Digital UNIX system
    ===============================
    There are three main steps to installing and configuring pwprint
    on your Digital UNIX system.  These are... copying the required
    software to the Unix system, installing the software, and then
    configuring the software.

    Copy the required software to the Digital UNIX system from the
    PATHWORKS 32 kit location (on CD ........).
	There are three methods you can use to copy these files.  They
	are FTP, NFT, and Pathworks share.  I'll quickly explain FTP.
	Go to a DOS Prompt and type FTP.
	   c:\ftp
	   ftp> open 16.120.160.206   #enter your unix server ip address
	   ftp> binary		      #make it binary mode for the copy
	   ftp> lcd d:\????	      #cd to the correct dir on the CD
	   ftp> cd /usr/anyarea	      #cd to a temporary dir on unix syst.
	   ftp> put pwprt700.tar      #send or "put" the file to unix

    Install:
	% tar xvf pwprt700.tar  #un-tar the tar file
	% setld -l PWPBASE700	#PW Print install
	% setld -l PWPMAN700	#man pages for PW Print

    Configure:
	% pwpsetup <enter>	#starts our script for pwprint setup

	The things that tripped me up during the pwpsetup were:
	   * I entered "pwsetup" but it's "pwpsetup".  Don't forget
		  that pwp...
	   * pwpsetup:

	     To Printer Name accept default <pwp0> if you want.

	     To Transport enter either TCP or DECNET.

	     To Print Server you need to enter the name of the 
	     Windows95 or NT Workstation computer. Do NOT accept the
	     default (prtsrvr)!

	     To Connection Type do not accept the default of "network".
	     In most cases this should be set to "direct"!
	
	     To Network location enter the path where your printer is...
	     such as \\win95\HPJET.  Where "win95" is the NAME of your
	     computer that the "HPJET" printer is attached to.

	     You can pretty much enter defaults for the rest of the
	     queries.


    Test Printing
    =============
    % lpr -Ppwp0 /etc/hosts	#print the hosts file to que pwp0

    If the hosts printout does not print go on to the troubleshooting
    section below.


    Troubleshooting
    ===============
    On the Unix side you can check around to see what's happening.
    Be sure to verify your settings in pwpsetup!  This is where you
    could be going wrong.  If these settings are not exactly correct
    it ain't gonna work.  See the suggestions in the above section
    called "Prepare the "Print Server"...".

    % pwpsetup -> #3	#display current settings for pwprint

    % lpq -Ppwp0	#queue status for queue pwp0

    % more /var/adm/pwp0.err	#check the log for queue pwp0

    % ps ax | grep lp	#check to see if print daemon is running

    % more /var/adm/syslog_dated/DD-MMM-TT:TT/lpr.log  #unix log

    % more /etc/printcap	#this should have an entry for the
				pwprint printer which defaults to
				a queue called pwp0.

    If you are still having difficulties you can take a sniffer trace
    to see if the Unix server is even sending anything out on the wire.
    If it is not sending any packets at all I suggest you re-verify
    your entries to PWPSETUP....especially regarding "connection type"
    and "print server".  Remember in most cases "connection type"
    will be DIRECT not NETWORK....and "print server" will be the NAME
    of your Windows95 computer or NT Workstation computer (start ->
    settings -> control panel -> network -> identification ->
    computer name).

Dave, make sure documentation gets an update!

Jeff

    Hello all. Two questions
    
    (1) Does the Pathworks 32 Print Services Client for UNIX 4.0
    support ASCII/TEXT files ?  I have a Windows NT 4.0
    server and LPS17 printers.  Postscript files print fine, text files
    appear to go through all the motions (the banner pages print) but do 
    not show up on the printer.  I read 60.12 to say text is not supported
    on VMS but should work on Unix. Correct ?  Has anyone had experience 
    sending text jobs to HP printers ? Will the same situation exist as the
    LPS17 ?
    
    (2) Print jobs coming from UNIX do not seem to be passing user or
    filename information.  Can the UNIX client be configured to pass file
    and user information to the NT Print Server ? 
    
    Thanks,
    Patrick.
    
    
    

    Hello Patrick,
    
    Actually, when I did my tests, I was sending text files (/etc/hosts)
    to an HP LaserJet IIP.  I think this printer will do both ascii stuff
    and postscript....anyway the /etc/hosts came out fine.  I didn't do
    anything special, or outside of the stuff I pointed out in 209.0 .
    
    Wish I could say more......
    
    Good luck,
    Dave_B

    From my understanding (gleaned from other notes in the conference),
    whatever file you send must be directly readable by the printer --
    there's no processing done on the PC.  If the printer's PS only, you
    can only send PS.  If the printer's text only, you can only send text.
    If the printer can autosence, it should do so unless it's already been
    told not to by some other process.