Symptoms and Resolutions document 17039

X-Apparently-To: yhamza@yahoo.com via mdd901.mail.yahoo.com Received: from ldn2mx5.ebrd.com (193.128.202.104) by mta105.mail.yahoo.com with SMTP; 7 Oct 1999 04:34:53 -0700 Received: from ldn2vs2.ebrd.com (ldn2vs2.ebrd.com [193.128.202.103]) by ldn2mx5.ebrd.com (8.8.5/SCA-6.6) with ESMTP id LAA02929 for ; Thu, 7 Oct 1999 11:32:02 GMT Return-Path: Received: from ldn1exc2.ebrd.com (unverified) by ldn2vs2.ebrd.com (Content Technologies SMTPRS 2.0.15) with ESMTP id for ; Thu, 07 Oct 1999 12:26:51 +0100 Received: by ldn1exc2.ebrd.com with Internet Mail Service (5.5.2448.0) id <4LWHNNXA>; Thu, 7 Oct 1999 12:31:53 +0100 Message-Id: From: robsonk@ebrd.com To: yhamza@yahoo.com Subject: RE: Printing from Solaris to WinNT lpd daemon Date: Thu, 7 Oct 1999 12:31:52 +0100 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2448.0) Content-Type: multipart/mixed; boundary="----_=_NextPart_000_01BF10B7.8D68A6EE" This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. ------_=_NextPart_000_01BF10B7.8D68A6EE Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Please see attached... - -----Original Message----- From: Yasir Hamza [mailto:yhamza@yahoo.com] Sent: 06 October 1999 21:05 To: Sun Managers Email List Subject: Printing from solaris to WinNT lpd daemon Gurus =20 I've succeeded in setting up printing from solaris 2.5.1 to a tcp/ip print server on windows NT, the problem is that the printout is alway required to be to a postscript printer.. while I'm using HP laserJet 5L which is not a PostScript printer, anybody knows any workaround for this problem, can I use my HP LaserJet 5l from my SparcStations running Solaris 2.5.1? =20 =20 Yasir Hamza System Admin Sudanet Khartoum, Sudan -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 6.0.2i iQA/AwUBN/yEqI3++wZnbTGUEQLqDwCglZFHSNsulGBJfyoXEfBx962IOpEAoIVa rKK5YtALK3r29nXibS/ZC5e1 =3Dh1h6 -----END PGP SIGNATURE----- =8D ------_=_NextPart_000_01BF10B7.8D68A6EE Content-Type: application/octet-stream; name="doc2html.htm" Content-Transfer-Encoding: quoted-printable Content-Disposition: attachment; filename="doc2html.htm" =0A= =0A= =0A= Symptoms and Resolutions document 17039=0A= =0A= =0A= =0A= =0A= =0A=

=0A= =0A= Symptoms and Resolutions article 17039=0A=

=0A= [ Notify of = changes ]
[ Edit/Retrieve Marked Documents ] [ = Mark Document ]
=0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A= =0A=

SRDB ID: 17039=0A=
=0A=
SYNOPSIS: Printing PostScript to a Windows NT server=0A=
=0A=
DETAIL DESCRIPTION:=0A=
=0A=
Several customers have reported problems when submitting PostScript =
files=0A=
from a Solaris client toa Windows NT server, in such that the NT =
machine=0A=
fails to interpret the job as Postscript, resulting in the document =
being=0A=
printed as a plain ASCII file.=0A=
=0A=
SOLUTION SUMMARY:=0A=
=0A=
There appears to be some confusion between Solaris and other UNIX =
based=0A=
operating systems that act as print clients to a Windows NT print =
server,=0A=
with respect to compliance of RFC1179.=0A=
=0A=
The RFC states that line 6 of the control file should start with an 'o' =
if the=0A=
data file contains Postscript, but our implementation as well as other =
vendors=0A=
uses an 'f' character instead.  Windows NT on the other hand expects =
the 'o'=0A=
character as their implementation of LPD was written after the RFC=0A=
specification=0A=
had been around for quite some time.=0A=
=0A=
There are a number of workarounds that allow the NT server to print =
files=0A=
correctly:=0A=
=0A=
1) /usr/ucb/lpr -l=0A=
=0A=
   According to the RFC this option alters line 6 of the control file =
by using=0A=
   an 'l' instead of an 'f'.  This tells the remote NT server to print =
the file=0A=
=0A=
   leaving the control characters intact, allowing NT to interpret the =
file as=0A=
   raw instead of text.=0A=
=0A=
   If you have Solaris 2.4 you will need to install patch 101959-06 before =
you=0A=
   can use this functionality.=0A=
   (See SRDB 13597 for the full description of this workaround)=0A=
=0A=
=0A=
Some customers have said that it is not practical to use lpr instead of =
lp, in =0A=
which case we have a problem as there is no way to alter the behaviour =
of lp to=0A=
send compatible control files.=0A=
There are however a couple of workarounds that the customer might wish =
to try:=0A=
=0A=
2) Pass through mode=0A=
=0A=
   According to the Microsoft support article ID Q150930, it is =
possible to=0A=
alter=0A=
   the standard behaviour of the LPD print service under NT so that it =
ignores =0A=
   the format control command from the LPR client and always assigns =
the RAW =0A=
   datatype to the job being printed.=0A=
=0A=
   NOTE: This setting is not available for a single printer. This =
setting=0A=
affects=0A=
   all printers on the Windows NT Server that are receiving print jobs =
from LPR=0A=
=0A=
   clients. Print jobs from non-LPR clients are not affected by this =
setting. =0A=
=0A=
   The method for altering the behavior of LPD for NT 4 is given below, =
but you=0A=
   should check out the support pages at Microsoft=0A=
(http://support.microsoft.com)=0A=
   for the full description and solution.  =0A=
   This is quoted direct from article Q150930:=0A=
=0A=
=0A=
   QUOTE=0A=
   "Configuring SimulatePassThrough In Windows NT 4.0=0A=
=0A=
     For Windows NT 4.0 to assign the RAW datatype, regardless of the =
control =0A=
     file contents, do the following: =0A=
=0A=
     WARNING: Using Registry Editor incorrectly can cause serious, =
system- wide=0A=
=0A=
     problems that may require you to reinstall Windows NT to correct =
them. =0A=
     Microsoft cannot guarantee that any problems resulting from the =
use of =0A=
     Registry Editor can be solved. Use this tool at your own risk. =0A=
=0A=
        1.Run Registry Editor (REGEDT32.EXE). =0A=
=0A=
        2.From the HKEY_LOCAL_MACHINE subtree, go to the following key: =
=0A=
=0A=
                 =
\SYSTEM\CurrentControlSet\Services\LPDSVC\Parameters=0A=
=0A=
        3.On the Edit menu, click Add Value. =0A=
=0A=
        4.Add the following: =0A=
=0A=
                 Value Name: SimulatePassThrough=0A=
                 Data Type: REG_DWORD=0A=
                 Data: 1=0A=
=0A=
           NOTE: The default value is 0, which informs LPD to assign =
datatypes =0A=
           according to the control commands. =0A=
   ENDQUOTE=0A=
=0A=
   Be aware though that you might need to setup two print queues per =
printer on=0A=
   the Windows NT server - one for plain text, one for Postscript.=0A=
=0A=
=0A=
3) Replace Windows NT LPD print service=0A=
=0A=
   There is a company that provides a complete replacement for the =
Windows NT=0A=
   LPD print service.  It is called WinLPD and is available from:=0A=
=0A=
   http://www.rabox.com/=0A=
=0A=
   NOTE: This is not a Sun product and is not endorsed or supported.=0A=
   However there have been favourable reports by other customers that =
this =0A=
   solution allows the NT server to print PostScript files =
successfully.=0A=
=0A=
=0A=
At this time there are no other known solutions or workarounds.  It is =
not=0A=
envisioned that behaviour of lp under Solaris will be altered, =
therefore if you=0A=
must use lp to print you should investigate workarounds (2) and (3).=0A=
=0A=
=0A=
PRODUCT AREA: Printers=0A=
PRODUCT: Utilities=0A=
SUNOS RELEASE: Solaris 2.x=0A=
HARDWARE: any=0A=

=0A=

=0A= =0A= =0A= =0A= =0A= =0A=

=0A= =0A= =0A=

=0A=

=0A= =0A= =0A= =0A= ------_=_NextPart_000_01BF10B7.8D68A6EE--