• Introducing Dark Mode! Switch by clicking on the lightbulb icon next to Search or by clicking on Default style at the bottom left of the page!

IP based printing

mx5

Member
This is a multi-part message in MIME format.

------=_NextPart_000_0043_01C05F08.C7561B20
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Has anyone set up printing in an NT only environment where the printers =
are ALL HP JetDirect based and the IS Dept does not want to use NT based =
print Queues or Printer Shares? All printing is done directly to the =
printers based on IP addresses. New JDE installation.

Vic Harder
Calgary, Alberta, Canada
W2Ksp1, SQL2000, JDE XE


------=_NextPart_000_0043_01C05F08.C7561B20
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Diso-8859-1" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.2919.6307" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT color=3D#008000 face=3DArial size=3D2>Has anyone set up =
printing in an NT=20
only environment where the printers are ALL HP JetDirect based and the =
IS Dept=20
does not want to use NT based print Queues or Printer Shares? All =
printing=20
is done directly to the printers based on IP addresses. New JDE=20
installation.</FONT></DIV>
<DIV></DIV>
<DIV><FONT color=3D#008000 face=3DArial size=3D2>Vic Harder</FONT></DIV>
<DIV><FONT color=3D#008000 face=3DArial size=3D2>Calgary, Alberta, =
Canada</FONT></DIV>
<DIV><FONT color=3D#008000 face=3DArial size=3D2>W2Ksp1, SQL2000, JDE =
XE</FONT></DIV>
<DIV></DIV></BODY></HTML>

------=_NextPart_000_0043_01C05F08.C7561B20--
 
Vic,

this might not answer your question but it could be an argument to convince your IS dept to agree to NT queues.

We're printing IP based but use NT print queues. In fact we had problems printing from OW to a remote NT print queues. After a traffic peak in the WAN OW seemed to time out and just 'forgets' about the print job and all following ones. No error message or anything. As a solution we are now spooling the print jobs in a local NT print queue that sends the spool to the remote queue.

2nd point was that we couldn't live with the standard UBE printouts and are using an overlay software that I believe requires a queue.

What are the reasons for the IS dept not to use NT print queues and shares?

Good luck

Frank

Frank Eckelmann
B733 SP11.3; AS/400; NT; Citrix 6; pcAnywhere 8; CreatePrint
 
Top