dhuber@aut.autelca.ascom.ch (Daniel Huber) (02/27/91)
Hello I try to setup remote printing over TCP/IP from HP Workstations (HP9000/835, HP9000/3xx) with HP-UX 7.0 to a SUN Server (SparcServer/490, also to a SUN3) with SunOS4.1.1. This works fine. I only had to specify the option -ob3 on HP's LP-spooling (lpadmin, install the printer) to enable 3 digit BSD requests. The printers print really out, what I send them, but Sun's daemon likes to send me a message: ------------------------------------------ >From daemon Wed Feb 27 12:53:29 1991 >Received: from case1 by aut.autelca.ascom.ch; Wed, 27 Feb 91 12:53:29 mez >Received: from sun3.YP.case1 by case1.YP.case1 (4.1/SMI-4.1) > id AA16374; Wed, 27 Feb 91 12:54:08 +0100 >Date: Wed, 27 Feb 91 12:54:08 +0100 >From: daemon >Message-Id: <9102271154.AA16374@case1.YP.case1> >To: dhuber@aut >Subject: printer job >Status: RO > >Your printer job (ps3-2) >could not be printed > > ------------------------------------------ Again: The printer prints out the file. However I get this message above (or similar :-) each time I print something. This only happens printing from HP to Sun. Aditional informations: - "rs" is NOT defined in Sun's /etc/printcap. ps3:\ lp=:rm=sun3:rp=ps3:sd=/var/spool/lpd:\ :lf=/var/spool/lpd/error_log: - mail notification is NOT defined, wheter in the interface script (HP) nor in the print command. - If I define the -ob3 option, I get the mail, If I do not define the -ob option, the printfile is copied to the spool directory on the Sun, but not printed out! What can I do to stop this mailing? Any help would be greatly appreciated. Daniel -- Daniel Huber AD-KT2.6 VOICE: +41 31 52 96 64 FAX: +41 31 52 97 51 Ascom Autelca AG Network Engineer, Network,Mail and News Manager CH-3073 Guemligen EMAIL: dhuber@autelca.ascom.ch Switzerland UUCP: uunet!chx400!hslrswi!aut!dhuber
franks@hpuamsa.neth.hp.com (Frank Slootweg CRC) (03/06/91)
Get patch "p129" for the Series 300 and/or patch "p128" for the Series 800 from your local HP support organization. The description of the patch is a little bit different than what you described, but I had a customer with the same fault description as you have and p129/p128 did the trick.