
------------------------------------------------------------
NOVPRIN2.DOC -- 19980319 -- Email thread on NetWare Printing
------------------------------------------------------------

	Feel free to add or edit this document and then email
	it back to faq@jelyon.com




Date: Thu, 29 May 1997 12:36:39 +0800
From: Brett Looney <BLooney@COMTECH.COM.AU>
Subject: Re: Multiple servers--Help

>Can anyone help with general guidelines for
>printing on a 2-server 3.12 setup?  Do print
>queues need to be setup on both servers if
>the client is attaching to the second server?

If the client is attaching to both servers, then you only need to have the
queues on one of them - just simply capturing will do the trick, but you
may have to use the "/s=" parameter with capture which specifies what
server the queues is on.

However, there is a smarter way and one that is much nicer if you have two
servers (or more - up to eight) and you don't want clients to be attached
to each server, but still print to both.

What you do is create a print server on both servers with exactly the same
name. On the server where the printer is actually hosted (ie where PSERVER
is going to be loaded) set up the printers and queues as you normally
would. But, in the menu option "Servers to be serviced" add the name of the
second server.

On the second server, once the printer server object has been created, add
the printers as you did on the first server, but instead of specifying what
sort of printer it is (local/remote, parallel/serial, etc), choose "Defined
elsewhere". Then, assign queues on the second server to those printers you
just created. The queue names do NOT have to be the same as those on the
first server.

Now, just load PSERVER on the first server. It will automatically connect
to the second server (because you said to service it) as a print server
with the same name (which is why we did that...).

If everything went to plan, users on the second server can now print to
printers on the first server without attaching to the first server - they
just capture to a local queue.

The only thing you lose is one client license on the second server because
the print server is attached as a sort of user.

------------------------------

Date: Wed, 4 Jun 1997 21:43:52 -0500
From: Scott Rafferty <rafferty@SNOWHILL.COM>
Subject: Print Queue Lockups

There may be many sources to your problem.  I am assuming you have uploaded
the latest firmware to each print server.

1. Check in JetAdmin.  (Using Win 3.1 version, can't remember which)
   Double-click on the print server name, check the status and see if it
   is able to attach to the server.

2. If it is attached to the server, printing irradically, (I know this is
   ludicrous), set up a bindery queue.  (This is the only way I can get my
   HP Printers to retain their settings without going to the front panel.)
   ...I really would appreciate someone telling me another route, thanx in
   advance.

3. If it is not attached to the server, go into configuration, check all
   of the settings.

(forgive me for the next part, I am not at work and don't have pconsole
 to look at)

4. If the settings are ok, Move to PConsole.
   Check the Queue and ensure it has a print server attached. (if not
   attach one) Check the Printer object and ensure that the connection
   is other and has a queue.  Check the print server and ensure it has
   a queue.

5. If all of this is ok, are connected to via NDS I would rebuild the
   printer information in PConsole. (Again, crazy but it has worked.)

6. Check and see if there is another server application (unix, nt or other
   NW) changing your settings. (We have a unix application which downloads
   characteristics to the printers.)

7. Reset the card to its factory defaults and reset it up. (External-unplug
   the power, hold down the test button, plug in the power, let the test
   button go after about 5 seconds or through the advanced settings in
   Jetadmin. Internal-Jetadmin advanced settings, don't remember manual
   way but can take card out of the printer put it back in).

8. If this don't work, check all cabling, hub ports and possibly swap
   cards.

9. Check your bindery queues to ensure that the are attaced to the correct
   printer.

10. Check your client software, Ensure they are getting an NDS connection.
    I don't believe that a bindery client can print to an NDS queue.
    (I may be wrong.)

11. If this don't work, I give up.

One of the main things I look for is a printer to attach to the NDS queue
and things seem to go ok.

We are in a mixed environment, running Novell 3.12, 4.11, NT 3.51, 4.0,
HP-UX, AIX  with most of our clients using Win 3.11 and about 50 Win95.

We are using JetDirects to connect about 200 printers and have found that
Bindery emulation in a 4.11 environment is not the best route.

------------------------------

Date: Thu, 10 Jul 1997 17:25:02 +1000
From: Jean-Marc Annonier <annonierj@AUSTPLANNERS.COM.AU>
Subject: Tip: Run Nprinter without login

For those like me who are using Nptwin95.exe for Windows 95 to share a
printer on the network and who are upset because the login window(s)
must be first cleared before Nptwin95.exe can be run (this is annoying
when users are in vacation), here's a tip to publish the printer
BEFORE the login window.

1 - Copy the files on C:
------------------------
First define a directory containing the necessary files for Nptwin95,
in this case, the directory is C:\Novell\Nprinter and the files are
the following:

BIDS45F  DLL
CW3215   DLL
NPTDRV95 MSG
NPTDRV95 NLM
NPTR95   NLM
NPTWIN95 EXE
NPTWIN95 DLL
NPTWIN95 HLP
NRDDLL95 DLL
NWADLG95 DLL
NWADMR95 DLL
NWCOMN95 DLL
OWL252F  DLL
SH30W32  DLL

from the SYS\PUBLIC\WIN95 directory (got to search a bit).


2 - Configure Nptwin95
----------------------
First, run normally Nptwin95.exe and select the printer(s) to be
serviced, as these settings will retained for the next session.


3 - Modify the registry
-----------------------
Then, using regedit, add in the registry the following string:

My Computer\HKEY_LOCAL_MACHINE\SOFTWARE
\Microsoft\Windows\CurrentVersion\RunServices

Name: Remote Printer
Data: C:\Novell\Nprinter\Nptwin95.exe /exit

Finally, add the line ForceRestore=3D1 in the [Options] section of the

c:\windows\netware.ini file

and restart Windows.


-------------
To deactivate: remove the string.

NB: If the key RunServices doesn't exist, create it.

I hope it will work for you, in my case, it's perfect.

PS: You can run other things in the same way by adding other strings
in the RunServices section of the registry.

For those interested, you can also still use the old good Nwuser
utility under Windows 95 and Novell Client 32.  Do you want to know how?

------------------------------

Date: Thu, 7 Aug 1997 16:53:14 +1000
From: Scott Marshall <esmarshall@USA.NET>
Subject: Re: win95 & rprinter ( is there a replacement)?

nptr95.exe: 870530 bytes
Readme for NPTR95.EXE - C32 Win 95 Nprinter -- 8-2-97/21:46p
This file contains the released IntraNetWare Version of NPRINTER for
Windows 95 (NetWare Nprinter Manager) that is compatible with the
NetWare Client 32 for Windows 95.

------------------------------

Date: Fri, 22 Aug 1997 12:21:53 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: MS Clients & Filesharing

>>	To refresh the minds of those for whom two years ago in this
>>business is prehistoric...
>>
>>	Do NOT use MS file/print sharing over IPX on a NetWare network.
>
>I am  afraid  this  can  cause  a  confusion.  According to the MS
>terminology, one should rather say:  "Do not use 'File and printer
>sharing _for_ Netware Networks'" because 'File and printer sharing
>_for_ Microsoft Networks' is harmless even _on_ a NetWare network.
>
>Or am I missing something ?
>
>Jiri Polach
----------
	The technical part is "over IPX" because that introduces the
fake NetWare part. Using MS file/print sharing over NetBEUI or over
RFC-NetBIOS (NetBIOS over TCP/IP) do not cause difficulties and are the
ways we (USU) recommend folks go about this. NetBEUI, of course, is
not routable; RFC-NetBIOS is fully routable because it uses IP.
	As Jiri says, use "FOR" as appropriate.
	Joe D.

------------------------------

Date: Tue, 02 Sep 1997 09:14:29 -0500
From: George Taylor <GTAYLOR@LHSNET.COM>
To: floyd@DIRECT.CA
Subject: Printer Form Feed Problem in Windows 95/Client32

Symptom:
	Printers send an extra form feed at the end off print jobs for DOS
applications run under Windows 95, Windows applications print fine.
Setting no form feed on the Print Settings Tab under Properties for that
printer makes no change, CAPTURE /SH in a DOS window still show Form
Feed as enabled.

Solution:
	Change the default capture settings on the Novell Client 32
Properties settings to show no form feed.

Steps:
	Right Click the Network Neighborhood
	Choose Properties
	Double Click Novell Netware Client 32
	Click the Default Capture Tab
	Remove the Check from the Form Feed box

These setting are identical to the Printer Settings on the Printer
Properties, however they take precedence when printing from a DOS Window.

------------------------------

Date: Wed, 1 Oct 1997 12:39:05 -0400 (EDT)
From: M Sweger <mikesw@whiterose.net>
To: novell@listserv.syr.edu
Subject: RE:Question on Novell FAQ (NOV_WIN.DOC) THE FIX.

I thought I'd post the solution to my DOS printing problems
when using the DOS print and print screen and using WFW3.11 with vlms,
novell support only (no Msft network support).

Originally, I could only print from Windows once a network printer
was configured within WFW3.11 but couldn't from DOS or a Windows DOS shell.
Mr. Tatet suggested that I set the Cap timeout value from DOS to something
greater than the default of zero. Instead of setting this from DOS, I
checked to see if the netware network configuration s/w had this option.
Yes, it does. I then set the timeout value to 1 (could be higher if needed)
so that it doesn't default to zero. Be aware that if you manually enter
the value zero that on the next activation of this window that it will 
be displayed as a default (null field) on the screen. Moreover, once
you enter this value you must select the default button and which
printer it applies to - the current one on lpt1 or all of them along with
entering the save button. By doing this, it writes these settings to the
netware.ini file for later activation; otherwise it defaults back to the
old setting of zero that was originally set in the ini file.

Thus, the vlm121_1.exe -vlm121_6.exe files have a bug. When
using the default setting of zero or by entering this value, the
print queue according the print manager stays open and spooling for
ever if a print job is input from the DOS command line using the DOS
print, printscreen or for Windows DOS shell followed by the print command.
The spooling works correctly if the print job is done when using a windows
application i.e. Word6 etc. Once the file is printed from a Windows
app, any Dos print jobs that are stuck trying to be spooled are then printed.
The only problem is is that the printouts are one continuous printout since
the files have been appended to each other. This results in some of
your printout appearing on the previous page that you didn't want it to.

------------------------------

Date: Thu, 2 Oct 1997 22:50:03 -0800
From: Gary Hoffman <novell@IRPSBBS.UCSD.EDU>
Subject: Re: ATPS Failure

>>I am getting an annoying bug with ATPS on Intranetware 4.11. This is
>>happening on all my servers, 64 Mb of RAM. The symptom is ATPS will
>>fail to service jobs (the mac clients will try to spool forever).
>>Unloading and >re-loading ATPS fixes it.

This is a PAP problem, according to Novell. The Printer Advertising
Protocol is implemented just a tad differently by each of Novell, Apple,
Lexmark and HP. Sometimes the Netware ATPS process stops "hearing" PAP
packets from your printer, according to that theory.

I had these symptons earlier this year and raised cain with Novell and
Lexmark. I finally got someone at Novell to listen to me and I sent them
packet traces from my netwtork. Then they told me about an APPLETLK.NLM
patch that is in beta. (I'm at home and don't have the version number.)
They let me download it and the problem seems to have gone away. That was
in May. I don't know if the update was ever released.

I recommend that you check patch levels on APPLETLK and ATPS and be sure
you are absolutely current. Maybe we can get Novell to release that
APPLETLK patch.

---------

Date: Fri, 3 Oct 1997 10:50:50 -400
From: Jon Dustin <jdustin@USM.MAINE.EDU>
Subject: Re: ATPS Failure

Novell has released the patch that fixes ATPS not 'hearing' that a
printer is alive. MACPT3D addresses this issue with ATPS.NLM v4.12

However, what we have been noticing is that ATPS will stop responding
to CLIENT requests, and must be unloaded/reloaded. I have been seeing
this behavior for about a year, with varying amounts of run-time
before ATPS stops responding. I have applied all current patches, and
still the problem occurs.

------------------------------

Date: Thu, 9 Oct 1997 14:30:29 -0700
From: Tim Madden <tmadden@ASPENRES.COM>
Subject: Re: Printer disappears?

>I'm using a 3coms 3c90x adapters along with client32
>tried both versions (2.11, 2.12) with win95 on my NW410 network.
>This has been a intermittence challenge since we went to win95 on
>the desktop. I've look at 3coms site and there's several issues involving
>3coms 3c90x family of adapters with client32. But none of this type.
>
>User would print and they would lose their printer which is setup for them
>in win95 for network printing. We have JetDirect cards with the NDS
>capable firmware.
>
>After the users reboot the station the printer comes back.
>
>Microsoft says to make sure you have the latest Shellup.exe file which
>I do.
>
>The win3.1 box has no challenge with this. But I'm in the process of
>converting over 250 wkst. to win95 and the 50 or so I've done are
>having this problem intermittently.

Same issue brought up earlier today.  Go to my FTP site
ftp://ftp.aspenres.com/pub/ and download spoolupd.exe.  This will
upgrade your Spooler Sub System DLL files and should fix the problem.
Might as well download Win 95 Service Pack 1 while you're there,
sp1upd.exe.  Full docs for the Service Pack are at MS, but
spoolupd.exe isn't.

------------------------------

Date: Thu, 16 Oct 1997 09:45:17 -0700
From: Tim Madden <tmadden@ASPENRES.COM>
Subject: Re: Printer disappears?

Please go to ftp://ftp.aspenres.com/pub and download spoolupd.exe
This will upgrade your spoolss.dll and associated files.

------------------------------

Date: Mon, 27 Oct 1997 18:01:37 +0000
From: Richard Letts <r.j.letts@SALFORD.AC.UK>
Subject: Re: HP JetAdmin not showing all printers

>Are you running NT with the Novell INW Client?  I have had peculiar
>behavior with this version of the program.  Printers won't show up on
>the list, new printers won't show up when I goto setup a new printer.
>I have reverted to using the Win 3.1 version.

I have to use both versions; some printers appear in one, but not in the
other; I have to use the 'old' version of the laserjet3's and 4's, and the
new version for the laserjet 5's and 6's. I'd guess HP don't know the
meaning of backwards compatability and there's something in the JETADMIN
protocol which won't work across versions.

This is a real pain.

---------

Date: Mon, 27 Oct 1997 14:44:57 -0700
From: "Steven W. Smith" <SYSSWS@GC.MARICOPA.EDU>
Subject: Re: HP JetAdmin not showing all printers

Sean, I've had that same problem using JetAdmin version 2.4 (and earlier)
under Win95.  I've also had JetAdmin show the same printer with 2 names, or
variations where "XXX" is appended to the name.  You know when you press F5,
the box says "Filtering", it looks like the JetAdmin software is scanning
the network for accurate information?  It's kind of a placebo (IMHO).

JetAdmin maintains (in my case) C:\WINDOWS\SYSTEM\HPCOLA.DAT.  Exit
JetAdmin, locate and delete HPCOLA.DAT (rename if you're squeemish),
restart JetAdmin.  It takes a bit longer to start up, but it will
miraculously have a much better grip on reality.

>I have a netware 3.12 server with 3 NIC's.  Each nic is plugged into a
>different 10Base-T hub (so there are 3 segments)
>
>I have  HP laserjet printers with JetDirect cards sitting on all three
>segments.  When I run JetAdmin form my PC that is on one of the segments, I
>can only see the Jaserjet that is on my segment.... I cant see the other two.
>Its like the server isnt routing the jetdirect traffic from one nic to the
>other... not routing SAP's or something like that.  Of course I can print
>to all three from my PC... but the printing is via the queue's on the
>server.... not directly to the printers themselves.

------------------------------

Date: Mon, 27 Oct 1997 18:28:51 -0500
From: Bud Durland <ndurland@CAPITAL.NET>
Subject: Re: print server

>I would like to know what kind of configuration you do for your
>print servers.  If you use pocket ethernet print server, please
>tell me the product and version?
>(P.S. the version of novell is important.)

We've had good luck with the Intel EtherExpress product; just make
sure you download the latest firmware from Intel.  We've used them
on Netware 3.12, 4.10 and 4.11 without too much trouble, although
they seem to work better in RPRINTER mode, rather than acting as a
PSERVER.

------------------------------

Date: Tue, 28 Oct 1997 11:01:49 MET_DST
From: Ralph Barth <rbarth@AXP602.GSI.DE>
Subject: NW 4.1 & LPR(D) & NT Printing

No longer a question but a solution.

My Problem was:

Netware 4 Server, old Intel Netports speaking IPX only, connected as
rprinter.  Windows NT 4 Server as Printserver for all NT clients to
avoid printer drivers installation on each NT client.
Problem: A printer connected via the NWclient on NT can't be exported
to the NT clients.

Solution:
Install NW Unix Printservices on an NW 4 machine (it's part of
INTRANETWARE, single product for 4.1 but the same).
Export all required print queues.
Install LPR Printing on NT Server (it's part of TCP services).
Install all printer drivers you need. Make them usable by others.
Connect to this printers at the clients.
Works fine as long as for each NT account their is an NW account (Admin vs
Administrator :-)).
Ok. TCP is required at the NW Server (I used the intranet address range
192.168.xx.xx).

Works fine.

------------------------------

Date: Mon, 3 Nov 1997 16:42:47 +0100
From: Gabor Borsodi <bme.eik.thulya@GROUPWISE.EIK.BME.HU>
Subject: Re: Send Print Job from Console -Reply

>Is anyone aware of a mechanism to send/copy/etc. a simple text file
>into a print queue from the Netware console?

There is copy.nlm:
	ftp://ftp.novell.com/pub/updates/nwos/inw411/copynlm3.exe

------------------------------

Date: Tue, 4 Nov 1997 17:08:54 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Print server gremlins!

>To all, I'm having intermittent trouble printing on a Novell 3.12
>50 user network.  I'm having trouble printing large files from Word
>6.0, Excel or that $%#!&*! AutoCAD 13.  The small files seem to be OK
>but the larger ones (8 times out of 10) get sent to the queue ( I can
>see it in pconsole) but never gets released to the print server. After
>that the workstation is usually unable to print at all without
>reboooting. Yet, sometimes from AutoCAD it never gets to the queue
>either.  In Word or Excel I get the following message...LPT3 ! Windows
>cannot write to this file.  The disk may be full....etc.
>
>My capture statement reads /q=108queue /ti=10 /l=3 /nb /nff /noti.
>I lengthened /ti from 3 to 10 seconds but it didn't help.
>I have also done all of the following in the past week...
>Deleted print queues and recreated them.
>Reset printservers to factory defaults.
>Spent the better part of today with Axis tech support (bad experience)
>and upgraded the firmware on the 540 to 5.36.
>My HP Laserjet III has 5Meg or RAM and the latest drivers.
>Printserver buffer size in pconsole/printserver configuration is maxed
>to 20K,  use interrupts=yes, IRQ=7, type=remote parallel, LPT1....
>Does this conflict with my CAPTURE statement's /l=3?
>All patches were done to the server this Summer.
>Running VLM's ver. 1.02 (1993).
>
>Am I missing a trick here?
>Joe D. once posted a note on an E-mail thread implicating cheap NIC's
>in a similar situation.  It's drastic but if I have to I'll change
>them all.
--------
	If Windows 95 then print to NetWare print queues, and Capture will
not be involved, and check the client Windows settings on printer matters.
But I am guessing this is an RPRINTER.EXE (client executable) situation
and in that case may I gracefully bow out.
	VLMs have changed a lot since v1.02 and may I recommend trying
the current release.
	Joe D.

------------------------------

Date: Tue, 4 Nov 1997 17:35:44 +0800
From: Brett Looney <brett@COMTECH.COM.AU>
Subject: Re: Problem With NPRINTER FOR Win95 and ECP Port

>I Have A Compaq Deskpro With A Ecp Port ( Is A Printer Port )
>And Can't Set A Nprinter For Use This Port.
>    The Message Is :
>    " .Xxxxx.xxxxx.xxxxx.xxxxx Esta Configurada Para Que La Use Lpt1.
>      Lpt1 No Es Soportada En Esta Estacion De Trabajo.
>      Seleccione Otra Impresora Que No Use Lpt1"

Sorry for coming in late, but:

This message appears when Nprinter goes looking for the LPT port in the
Win95 registry but can't find it because the entry is in a different place
(because it is an ECP port).

So, instead of getting Nprinter to look for the port, just tell it where
it is by using the NPRINTER.INI file like this:

   [LPT1]
   name=.P1.aordco
   printer=P1
   printServer=PS-AORDCO
   number=0
   port=7
   profile=1

------------------------------

Date: Wed, 5 Nov 1997 10:32:11 +0100
From: Niels Chr Nielsen 5551 <niels.c.nielsen@RISOE.DK>
Subject: Re: Incorrect Identifier on 4.1 Print Banner

>Here's a hint.  Subtact 250 from the connection number that is over 250
>and check which User is logged in at that connection.  You'll find it
>looks suspiciously like the incorrect and random name on the BANNER.

...you're close.
  The problem stems from the fact that all regular Netware 3.x
versions had a maximum of 250 concurrent connections. I those days
memory was expensive and to conserve it, the connection number was
stored as a byte - i.e. 8-bit - value. With Netware 4.0 this changed,
and the max was raised to 1000 concurrent connections. At the same
time, new API definitions with 16-bit connection numbers were
introduced, and by November 1993 (most of?) these new definitions had
made it to the SDK, so developers could make software compatible with
500 an 1000 user versions of NW4.0x.
  The MS Win95 Client (and Services) for Netware Networks still uses
some 8-bit connection number NCP calls for authenticating to printer
ressources, and - I suspect - for Passthru Authentication for
peer-to-peer networking.
  Thus, the correct arithmetic is to take the problem users
connection number modulo 256 to get the number of the user appearing
on the banner. As NW4.1x has additive licensing and thereby a
theoretical max concurrent connection count of several thousands
(2**16 - 1 = 65535 ?), this is equivalent to "keep subtracting 256
from the connection number until you get a result less than 256".

------------------------------

Date: Mon, 17 Nov 1997 18:07:51 -0800
From: Randy Richardson <randy@INTER-CORPORATE.COM>
Subject: Printing with the MS Client

>Long story, but basically a software company blamed all of our
>problems on Client32 so we installed the MS client, in the hope that
>they would have to give us the real answer.
>
>Now none of the windows apps will print to network printers.  Capture
>/sh shows the queue captured to the correct port and dos apps can
>print correctly.  The 95 print driver shows lpt2 mapped to
>\\$NDS\.printer.ou.o.  I can manually change this to \\server\printer,
>but I would prefer not to everytime the print queue needs to be
>changed.  I would prefer that 95 just print to lpt2 and let me capture it
>in the login script.
>
>Is there a way to fix this?

	Upgrade to Client32 version 2.20 (a free download from www.novell.com) and
see if that resolves the problems.  If it doesn't, let us know what
software package you're using, and tell us what some of the problems are.
Maybe someone here on this list is using the same software.

	The Microsoft client has many known problems, which are resolved with
Client32.  If one of the concerns is WinSock.DLL compatibility, Client32
v2.20 uses Microsoft's WinSock.DLL to resolve this.

	If your network must be C2 compliant (secure), then you have to use
Client32 (the Microsoft client is not "NetWare YES" certified).

------------------------------

Date: Tue, 18 Nov 1997 07:58:46 -0500
From: "Philip P. Obbard" <Philip_Obbard@BOSCAT.COM>
Subject: Re: Dropped Printer

I've seen this problem before - the print server on the server console
claims the printer (connected by RPRINTER.EXE) is out of paper, when it
isn't. No matter how often you restart the machine running RPRINTER, the
message remains, or only flickers off briefly.

In my case, it turned out to be the result of corrupt printer drivers on
the PC running RPRINTER. Once I reinstalled the correct drivers, the
problem disappeared as well.

------------------------------

Date: Wed, 19 Nov 1997 12:43:43 -0600
From: Joe Doupnik <JRD@CC.USU.EDU>
Subject: Re: Printer SAPs

>>Our HP Jetdirect cards default to a 60 second SAP broadcast. I want to
>>change it to a longer time period. What is the maximum I can set it
>>without the server purging SAP table of this HP Jetdirect server? Where
>>in 4.11 is the parameter to show the time period to purge these tables?
>>Our network is pretty stable with few additions as far as servers go,
>>but we keep getting broadcast storms.
>
>There is a great set of articles by Laura Chapell in the past three issues
>of "NetWare Connections" on this very topic.  Since Ms. Chapell is the
>proverbial "expert" on the subject, I would like to see if she has the
>answer first.
>
>See http://www.novell.com/nwc for further details.
---------
	We can provide some answers here, however.
	SAPs involve distance from places by the time they appear in routing
tables (what's announced to other servers). If a SAP announcement is missing
then the router software gracefully ages out the SAP entry, by increasing
its network distance by one unit. That way the info is present but apparently
not as reachable. It does this again on the next consequetive miss and so on,
until finally the network distance reaches 16 units. 16 is basically the
edge of the knowable universe, termed "countable infinity." Thus one could
have 15 minute gaps and still barely survive.
	But, there is no free lunch. Changes in network distance can trigger
routing update packets. This is clearly the case when a long lost device,
at distance 13 and growing, suddenly reappears at distance 2. That news
generates a trigger to spread the good word. There is a saying in the routing
work which goes "Good news travels quickly, bad news travels slowly" and we
see it here. Routing changes certainly cause admin busy work in the routing
tables of each router, hear disk drive churn and cpu cycles evaporate when
computing minimal length routes.
	We can readily see these count up to infinity and drop situations.
Use the console and watch the distance to servers. Turn off a server and
keep watching. The distance will go up by one on each one minute cycle
until the object vanishes. Display routers is the normal command.
	Thus, the recommendation is to not tinker with SAP update intervals.
	If there are broadcast storms then certainly solve them. But printer
SAPs are not the cause of nor a serious component of such storms. Braindamaged
hubs may well be, as has happened here massively. Measure what's happening
before twisting the knobs blindly, and similar cautious advice.
	Joe D.

------------------------------

Date: Sat, 29 Nov 1997 02:17:39 +0200
From: Mike Glassman - Admin <admin@IAA.GOV.IL>
Subject: Re: Pserver

>I've only been on this new job for about three days now, and I
>discovered on there Netware server 4.11, and 4.1 they have every
>print queue printer to a different pserver.  In my previous jobs,
>I have always had only "one" pserver, and all my queue's directed
>to that pserver.  It this correct

It's a WASTE of resources !!!!!!

There is absolutely no reason why one print server should not handle
that many queues. 20 is not that many actually.

The question is of course, if you have only 2 servers (if I understand
correctly), how can you have 20 pservers ? There is no pserver.exe
anymore, so either the pservers are built into the printers or are
externall units such as the HP or Intell boxes. If that is the case, you
have no pronblem as it does actually work faster this way. If it isn't
the case, I would move (recreate) all the queues into one main pserver
and handle it from there.

---------

Date: Fri, 28 Nov 1997 22:12:15 -0500
From: Bud Durland <ndurland@CAPITAL.NET>
Subject: Re: Pserver

If you mean they have 20 instances of PSERVER running the server,
you're right;  this isn't normal.  Take the time to correct it.  On
the other hand, the network may have several printers with direct
network connections, such as the Hewlett-Packard JetDirect or the
Intel Netport.  These devices are often configured for "queue server
mode", in which case they will appear to be a PSERVER.

------------------------------

Date: Sat, 29 Nov 1997 16:11:00 -0700
From: Hansang Bae <hbae@PRIMENET.COM>
Subject: Re: Pserver

>If you mean they have 20 instances of PSERVER running the server,
>you're right;  this isn't normal.  Take the time to correct it.  On

You can only load PSERVER once on the server, so it *has* to be external
pserver.exe's or other stand alone print servers running in pserver
mode.

---------

Date: Sun, 30 Nov 1997 08:01:43 -0500
From: Dave <dave@MOSQUITO.COM>
Subject: No PSERVER Loaded

What they have in their printers, are the HP Network Cards.  When I was in
my previous job, we also used these, but when I set up the printers, and
que's in NDS, I always directed these card to print to a certain que, and
the que was directed to THE SAME PSERVER. We have over 18 in the college,
and all of them work with one PSERVER.

NOW, at my present job, they have over 20 printers, 20 que's, and 20
PSERVERS.  When I went to the server console, there no PSERVER load.  How
can this be ?  Can a network printer print directly to printer without a
PSERVER being loaded ?  TO ME THIS IS VERY STRANGE.

---------

Date: Sun, 30 Nov 1997 11:54:43 -0500
From: Bud Durland <ndurland@CAPITAL.NET>
Subject: Re: Pserver

>You can only load PSERVER once on the server, so it *has* to be
>external pserver.exe's or other stand alone print servers running
>in pserver mode.

I always thought that as long as you specified different print server
names, you could load multiple instances of PSERVER.NLM.  To be
honest, though, I've never seens a reason to try it.  Thanks for the
clarification.

---------

Date: Sun, 30 Nov 1997 09:07:11 +0000
From: Randy Richardson <randy@INTER-CORPORATE.COM>
Subject: Re: No PSERVER Loaded

>What they have in their printers, are the HP Network Cards.  When I was in
>my previous job, we also used these, but when I set up the printers, and
>que's in NDS, I always directed these card to print to a certain que, and
>the que was directed to THE SAME PSERVER. We have over 18 in the college,
>and all of them work with one PSERVER.
>
>NOW, at my present job, they have over 20 printers, 20 que's, and 20
>PSERVERS.  When I went to the server console, there no PSERVER load.  How
>can this be ?  Can a network printer print directly to printer without a
>PSERVER being loaded ?  TO ME THIS IS VERY STRANGE.

The documentation for HP JetDirect NICs states that Print Server
mode is faster than Queue mode, and this is also a popular assumption
in the industry.  This is true when you have a slow server (e.g., one
486 CPU in the server with 200 PC, Mac, and Unix clients).

If the utilization on your server rarely goes over 20 or 30 percent,
the HP JetDirect NICs should perform just as well in NDS Queue mode.

The best way to find out is to try it with a few printers and record
the amount of time it takes for print jobs to reach the printer at
both busy and non-busy times.

---------

Date: Sun, 30 Nov 1997 09:10:45 +0000
From: Randy Richardson <randy@INTER-CORPORATE.COM>
Subject: Re: Pserver

>>You can only load PSERVER once on the server, so it *has* to be
>>external pserver.exe's or other stand alone print servers running
>>in pserver mode.
>
>I always thought that as long as you specified different print server
>names, you could load multiple instances of PSERVER.NLM.  To be
>honest, though, I've never seens a reason to try it.  Thanks for the
>clarification.

This would be important for large networks running a NetWare 3.x
server because PServer.NLM for NetWare 3.x only supports up to 16
printers at one time.

I believe that PServer.NLM for NetWare 4.x and IntranetWare support
up to 255 (or 256?) printers.

This shouldn't be an issue for another, what should we guess with
the way this industry grows, two or three years?  ;)

---------

Date: Mon, 1 Dec 1997 19:46:59 +0800
From: "Cordelio C. Sumbillo" <mfp01@MAIL.NETASIA.NET>
Subject: Re: No PSERVER Loaded

>What they have in their printers, are the HP Network Cards.  When I was in
>my previous job, we also used these, but when I set up the printers, and
>que's in NDS, I always directed these card to print to a certain que, and
>the que was directed to THE SAME PSERVER. We have over 18 in the college,
>and all of them work with one PSERVER.

Okay, in this setup of yours you are actually using the printers
with the HP cards as REMOTE printers.  As such, they are being
serviced by PSERVER and thus, do not consume any network connection.
You spare your server licenses, in effect, in your case, 18 license
connections.

>NOW, at my present job, they have over 20 printers, 20 que's, and 20
>PSERVERS.  When I went to the server console, there no PSERVER load.  How
>can this be ?  Can a network printer print directly to printer without a
>PSERVER being loaded ?  tO ME THIS IS VERY STRANGE.

In this setup, the HP cards are acting as PRINT servers servicing a
printer and queue each.  Each one acts as its own "PSERVER".
However, this one uses 20 network connections.

------------------------------

Date: Mon, 1 Dec 1997 15:06:28 -0400
From: Lynn Connors <lynn.connors@ACADIAU.CA>
Subject: Re: NDPS - no ndps objects in nds

>>I've installed (and reinstalled) ndps on a development/test server.
>>It seems to load fine on the server itself but in the tree the
>>broker object comes up labelled with a question mark and when I try
>>to create a manager object, no ndps objects can be found.  Oddly
>>enough though, when I do a search I can choose from NDPS broker/
>>manager/ printer so the schema has been modified somewhat but not
>>enough to create new ndps objects.  I'm running 4.11 with iwsp4a, 1
>>new partition, 1 replica.

>Yes, I've had the exact problem here. I, too, am in a test environment
>and ran into the identical scenario. I got an error at the completion of
>the installation that claimed I needed to manually update (I believe it
>said the schema).
>
>No answers as yet.

After a little experiementing, found out what's going on... Because I
installed NDPS on a test server, and run nwadmin from another server,
it didn't have all the required files.  Files from sys:\public\win95
and sys:\public\win95\nls\english on the test server were required in
the directory from where I run nwadmin to recognize the NDPS support.
Not an issue if you install on the same server you run nwadmin on.

------------------------------

Date: Thu, 11 Dec 1997 12:52:09 -0700
From: Tim Madden <tmadden@ASPENRES.COM>
Subject: Re: C3295D.EXE Patch File Needed

>Would anyone help me by sending me the file called C3295D.EXE? Our
>LAN is composed of serveral NetWare 3.12 servers, and currently we
>have upgraded all workstations to Windows 95 with Novell 32 Client
>loaded.  I just searched Novell Home Page but could not find this
>file.  I need this file to deal with our workstation SPOOL32.DLL
>problem.  Any help is appreciated.

What's the spool32.dll problem you're trying to solve.  There is a
question on this list every few months about users losing their
Win95 printers.  There's a Win95 patch which is very hard to come by,
so I posted it to my FTP site at
ftp://ftp.aspenres.com/pub/spoolupd.exe.  This patch seems to have
fixed everyone's "lost printer" problems, but I'm not sure if this is
the problem you're having.

------------------------------

Date: Thu, 11 Dec 1997 19:37:34 -0500
From: Debbie Becker <dbecker@CLARK.NET>
Subject: Re: Win95 printing and Novell

>I have a Netware 3.11 server and am beginning to install win95 on the
>PC's.  I set up the printers as queues (The ones directly attached to
>the server) and on some machines it works fine and we have no printing
>problems.  On other win95 machines that are set up exactly the same the
>job never reaches the queue and just kind of disappers or the printer
>will quickly flash form feed like its going to print then nothing.
>We have a mixture of IBM PC's and can't seem to relate this to any
>specific type of PC.

I can empathize.  I've had nothing but problems printing from Win95 (I'm
convinced that Bill's strategy is to get us all so frustrated with the
product that we'll jump at the chance to move to NT Workstation just for
the stability!)

I've done such things as going to printer Properties, Details and changed
spooler settings (changed format to RAW, told it to print direct to printer
and bypass the spooler, etc.). What has seemed to be most successful across
the board so far has been to load SPOOL32.EXE when Windows starts (either
the LOAD line in the WIN.INI or in the Startup group seems to work). I've
also heard of a new, improved version of spooler at
	ftp://sft.aspenres.com/pub/
if all else fails, you might want to check that out.

------------------------------

Date: Fri, 12 Dec 1997 04:14:23 -0800
From: "Philip J. Koenig" <pjk@CRL.COM>
Subject: Re: Win95 printing and Novell

>>I have a Netware 3.11 server and am beginning to install win95 on the PC's.
>>I set up the printers as queues (The ones directly attached to the server)
>>and on some machines it works fine and we have no printing problems. On
>>other win95 machines that are set up exactly the same the job never reaches
>>the queue and just kind of disappers or the printer will quickly flash form
>>feed like its going to print then nothing. We have a mixture of IBM PC's and
>>cant seem to relate this to any specific type of PC. Any help would be
>>greatly appreciated.
>
>I can empathize -- I've had nothing but problems printing from Win95 (I'm
>convinced that Bill's strategy is to get us all so frustrated with the
>product that we'll jump at the chance to move to NT Workstation just for
>the stability!)

On my 3.11 server I use here on the test/home LAN, I have had
constant problems printing from Win95 workstations, using either MS's
client or Client32.  The problems are very similiar to what you
report - in my case what usually happens is the print job begins to
spool, then Win95 reports there was an error printing.  Sometimes the
job cancels, but more often it starts to print the first part of the
job and then stops. (I have a Deskjet 520 connected directly to the
server's parallel port using PSERVER.NLM v3.76)

Once upon a time ('95 or '96), David Harris of Pegasus Mail fame
mentioned that Win95 had a habit of often corrupting the first few
bytes of files sent to Netware queues.  I believe this also appeared
in the Win95 netbugs list.

I find that the problem happens very frequently on the first print
job sent to the queue after booting Win95.  After bringing the
printer offline, clearing the queue and printer buffer and
reprinting, it often prints fine.  This has plagued me on this system
ever since I installed the Win95 beta in June 1995.

One thing that helped me somewhat on one of my machines was
installing Superprint v5.0.  It appears to bypass a number of Win95
printer mechanisms when you use their drivers, and solved a problem
with a poorly implemented newsreader client, and substantially
reduced the frequency of spool errors to the 3.11 server.

My understanding is that this issue is primarily on 3.11 servers,
although I haven't done testing myself, other than the fact that I
haven't seen this issue on client LAN's running 4.x. (I don't use
print queues on my 4.11 server)

------------------------------

Date: Fri, 19 Dec 1997 12:45:30 -0500
From: Steve Kurz <skurz@NORFOLK.INFI.NET>
Subject: Re: PSERVER.NLM

>Our office currently has 8 printers; all HP's with JetDirect cards. Each
>printer is configured with its own print server (queue mode). I want to
>add a Deskjet printer that needs to be directly attached to the server.
>Will loading the PSERVER.NLM affect my current setup?  I've made a
>separate print server/printer/queue for the new printer and was hoping
>to load PSERVER only for this printer.  Our other printers have been so
>well-behaved I don't want to change them.

It depends. A lot of the current crop of HP DeskJet printers require that
they be directly connected to the PC that is running the print driver.
This is due to the fact that the driver is using the resources of the
computer to drive the print engine.  This makes most DJ printers unusable
as a network resource.  Unless it it a DJ1200 or higher, which is capable
of using a JetDirect card, it may not be possible to share the DeskJet
using Pserver, either the .exe or the .nlm version.

------------------------------

Date: Fri, 19 Dec 1997 13:16:10 -0500
From: Tom Birkenbach <tbirkenb@EDCEN.EHHS.CMICH.EDU>
Subject: Re: HP JetDirect on Novell Intranetware 4.11

>We are attempting to connect an HP JetDirect with 3 ports to a Novell
>network version 4.11.  We have followed the directions (several times)
>exactly - or at least we have tried.  The configuration page will print.
>A test page will print from JetAdmin (ver 2.4).  The network insists
>that the printer is not connected.  Jobs go to the assigned print queue,
>but nothing will print.  Any suggestions?

We have quite a few HP JetDirect 3 ports in use and have the same
problems.  I can setup the port and the printer, but if I click on it
after it's configured it says that it can't communicate with the
device.  It still works thought!  One thing I learned is that you CAN
NOT use the Novell Client 32 v2.2 to setup more than ONE port on the
3 port JetDirect.  You have to use any version before v2.2 or else it
will lock up the workstation and possibly screw up the JetDirect to
the point that you have to reset it to facroty settings.  I learned
this from HP tech support.  They are currenlty 'working' with Novell
on a solution.

Also, v2.5 of the JetAdmin software is out and allows you to create
the objects using the JetAdmin software instead of creating them
first in NWAdmin and trying to match up the names...  Good Luck!!

------------------------------

Date: Mon, 29 Dec 1997 18:57:49 -0800
From: Anthony Baratta <Anthony@BARATTA.COM>
Subject: Re: Printing: Jetdirect Broadcasts

>2 questions: I recall posts regarding turning off HP Jetdirect
>broadcasting which at one time was thought to "flood the net" with
>advertising. Was that SAP advertising or another setting which was
>turned on by default in previous releases?
>
>Is there a searchable archive of the Novell posts similar to the
>Win95-L archive site?

Here's info I found on the Jet Direct Broadcasts Storms. Its a TCP/IP
problem.

We've all experienced this arrogant search algorithm in action!! There
are a few relatively simple steps to quiet down your network while
maintaining the overall functionality of the JetAdmin product.

The JetAdmin utility for Windows 95, version 2.3x, implements a TCP/IP
Broadcast Discovery mode with two mechanisms for finding HP printers on
a network:

1.  The "Broadcast" mechanism sends out one general request packet in an
attempt to find HP printers which understand TCP/IP.  This mechanism is
a reasonable method for finding printers.  However, it is not always
100% effective, and may need to be invoked more than once in order to
find all available printers.

2.  The "Subnet Search" mechanism tries to contact sequentially every IP
address on a subnet to find HP printers.  This mechanism puts out a
large load of broadcast traffic, usually causing an unacceptable
deterioration of network performance.

Most HP JetAdmin users should disable the Subnet Search mechanism.
PLEASE

READ AND PERFORM THE FOLLOWING INSTRUCTIONS FOR DISABLING SUBNET
SEARCH!!


INSTRUCTIONS FOR DISABLING SUBNET SEARCH:

*** IMPORTANT *** These instructions should be performed IMMEDIATELY
after
the JetAdmin software is installed on the Windows 95 PC.

The instructions assume that the user has both regedit.exe and the
TCP/IP protocol loaded on the system. These instructions specify a
change to the Windows 95 Registry using the regedit utility.  Care
should be exercised in using regedit since modifying the Registry
incorrectly could cause serious operating system damage.  A backup of
the Registry should be performed before ANY modifications are made.
Users who have questions
about the Registry, regedit, or similar concerns should contact
Microsoft

for assistance.

If users are unable to perform these instructions, they should
IMMEDIATELY
remove the HP JetAdmin Utility from their system.

The steps to perform the Registry modification are:

* From the Task Bar, click on the Start button * Select Run...
* Type in regedit in the Open field
* Double-click on HKEY_LOCAL_MACHINE * Double-click on SOFTWARE
* Double-click on Hewlett-Packard
* Double-click on HP JetAdmin
* Double-click on TCPIP
* On the right side of the window, you will see the item 'No Subnet
Search';
Double-click on this item
* Enter the number 1 in the Value data field (0=3D search, default;
1=3Dno search)
* Click on OK
* Close the Registry Editor.
* Reboot the PC

The Registry file has now been modified so that no subnet searches will
occur.


EXTRA INFORMATION:

The Broadcast mechanism does not need to be disabled as it is relatively
benign. The Broadcast mechanism alone should be sufficient for finding
TCP/IP printers.  Users who do not need TCP/IP Discovery may disable
both the Subnet Search and the Broadcast mechanism.  Without TCP/IP
Discovery, JetAdmin defaults to using only the IPX/SPX protocol to find
printers.

The Broadcast mechanism may be disabled as follows:

* Run the JetAdmin Utility
* Select the Options menu
* Click on Preferences
* Click on the TCP/IP Discovery tab
* Click on the Broadcast box to clear the check mark
* Click on OK.  (The general request Broadcast is now disabled)

Please refer to the HP JetAdmin documentation or contact Hewlett Packard
regarding these and other issues with the HP JetAdmin Utility.

---------

Date: Tue, 30 Dec 1997 08:12:36 CST
From: Karl Kamin <Karl@TIS.KELLY.AF.MIL>
Subject: Re: Printing: Jetdirect Broadcasts

>2 questions: I recall posts regarding turning off HP Jetdirect
>broadcasting which at one time was thought to "flood the net" with
>advertising. Was that SAP advertising or another setting which was
>turned on by default in previous releases?
>
>Is there a searchable archive of the Novell posts similar to the
>Win95-L archive site?

That was JetAdmin 2.35.  It would ARP your entire network looking
for HP printers. If you are on a class B network, that meant 65,000
+ arps for each machine!  To turn off the arping use REGEDIT and
change the NoSubnetSearch to a 1 from 0.  This will stop the arping.

HKEY_LOCAL_MACHINE/SOFTWARE/HP
JetAdmin/TCPIP/NoSubnetSearch=0x0000001

------------------------------

Date: Fri, 9 Jan 1998 09:58:00 -0700
From: Hansang Bae <hbae@PRIMENET.COM>
Subject: Re: Removing a bridge

>> Node <address> () claims net addr 710 should be 700
>>on all servers. We're stumped for where to look. Does anyone have any
>>ideas of what the problem might be?

"Baird, John" wrote:
>In addition to reconfiguring any IPX routers which are configured to
>use 710 you should reboot all print servers previously on 710.

Well, you have the node address, that should help.  As John mentioned,
print servers (even external stand-alones like netport, jetdirect et al)
need to be reboot.  And *ALL* Macs should be turned off for about 10
mins as well.  Those peskey PRAMs will get you everytime.

------------------------------

Date: Fri, 30 Jan 1998 08:14:58 +0000
From: Randy Richardson <randy@INTER-CORPORATE.COM>
Subject: Re: Apple Printer help

>I've been getting a log full of the following errors:
>
> 1-30-98   4:01:03 am:    ATPS-4.12-456
>   Severity = 3  Locus = 17  Class = 0
>   Printer <Austin Office HPIIISi>: NBP confirm: No buffer space
>   available.
>
>Note the time.  Take my word for it, no one is here ar 4:00am<grin>.
>I looked in the manual for the -456 error code and nothing is listed.

Is your printer going into sleep mode?

------------------------------

Date: Mon, 23 Feb 1998 22:00:59 -0800
From: Randy Richardson <randy@INTER-CORPORATE.COM>
Subject: Re: HP jet direct and nw411

>I just upgraded a 50 user Novell 3.12 network to Intranetware, and my
>jet direct external print servers stopped working. When i called HP I
>was told that the units I have were outdated, and were not upgradable.
>The HP rep told me the print servers I have were not compatible with
>Novell 4.11 (or was it NDS?), and that I have to purchase new units. So
>I purchased new units, and they give me problems too!   When attempting
>to create an OU called printers, and build my printing environment using
>NWadmin (win 95) in OU=printers, I could not do it. The Pserver would
>only attach to an old bindery print que, and NWadmin says that all my
>jet directs are down. I was unable to configure the jet direct servers
>with new ques. What am I doing wrong?  I Hope i did not miss a previous
>thread on the subject, as I have been away from the list for awhile.

The JetDirect boxes need a user to login as in order to service
print queues.  The following configuration tips may also be helpful:

	- Configure the JetDirects to use only one protocol and frame type
	- Update the JetDirect firmware on all JetDirects
	- Make sure the JetDirect is configured for NDS
	- Configure your NDS Printers as "Unknown/Remote"
	- Get the latest version of "JetAdmin.Exe"

---------

Date: Tue, 24 Feb 1998 12:53:24 -0800
From: Mike Neal <miken@EUROPA.COM>
Subject: Re: HP jet direct and nw411

>>> > > I just upgraded a 50 user Novell 3.12 network to ......
>>> >
>>> >        The JetDirect boxes need a user to login as in order to service
>>> > print queues.
>>>
>>> I'm sorry, the jet directs need a user to log in as what? in order to
>service
>>> print ques?
>>
>>        The JetDirects need to login as a user.  Create a user called
>>"Printer" and restrict its login address (after you get it working)
>>to those of the JetDirect boxes.  You can use the same user for all
>>print queues.
>>
>>        With RPrinter and NPrinter, login is not required because these
>>systems are only servicing a printer.
>>
>>>Thanks for your response to my post. I do have the boxes configured
>>>for NDS, but i have all frame types selected.
>>
>>        Having all frame types selected doesn't hurt anything, but if you
>>take one away from your server later on, your JetDirect box might
>>need to be restarted if it was using the one you removed.
>>
>>        The problem with frame type autodetection is that a different frame
>>type is sometimes selected.
>
>This is how I get HP jetDiect cards to work.
>
>Create a User - I have setup about 50 hp jetdirect and not once created a
>user.
>
>For qserver mode (I always use this) I setup a print server, a printer and
>a queue for each jet direct in NWADMIN. Example Acct_PS, Acct_P and Acct_Q.
>
>Then inside of the jetadmin utilities I tell it to rename the jetdirect
>card to Acct_PS then tell it to use NDS and give it the container. This is
>all I ever do and they have always work correctly the 1st time. The only
>thing is any netware utility will not show the correct status of the
>jetdirect cards, at least in my views.

With the latest JetAdmin for W95, ver. 2.5, you can create the printer,
print que and print server from within JetAdmin, no NWAdmin required.

	http://hpcc923.external.hp.com/cposupport/indexes1/janovs.html

------------------------------

Date: Mon, 2 Mar 1998 16:51:31 +1000
From: Michael Bednarek <mb@DOH.HEALTH.NSW.GOV.AU>
Subject: Re: PSERVER and HP JetAdmin

[snip]
>The problem is that I cannot get the network to talk to it.

>I'm running the Jet Admin tool (2.33 for winNT) and I can see and
>configure the printer, but I can also see that it doesn't reckonise
>that it's connected to a novell network.
>
>Under PSERVER, I have the printer defined, the queue defined, but it
>simply won't reckonise that the printer is available or even on the
>network.   I followed the instruction EXACTLY as descibed in the HP
>Printer manual tooo!!!!! :-(

I had a similarly unsuccessful experience, using JetAdmin 2.53, until
I read in JAREADME.TXT that it requires the Novell IntranetWare Client.
After I installed that, JetAdmin worked as advertised. Of course, other
problems with the client also surfaced.

---------

Date: Mon, 2 Mar 1998 15:36:36 +930
From: Mark Smith <marks@OSS.ERIN.GOV.AU>
Subject: Re: PSERVER and HP JetAdmin(Solved)

The solution (of sorts) was to initially use the New Jet Admin tool
for NT, then I had to use the really old $JET$DOS.EXE which would
allow me to specify the server and queue required.

------------------------------

Date: Mon, 2 Mar 1998 13:11:23 -0800
From: Randy Richardson <randy@INTER-CORPORATE.COM>
Subject: Re: slow printing...

>>Is NPrinter running in a multi-tasking environment, or just through
>>straight DOS?  Which client are you using on this box?
>
>AFAIK, the LJ6l uses bi-directional print drivers, obviously not
>passed by the print queue.  Unfortunately this is the case for most
>of the home / home office HP machines.  I use LJ3 drivers to push a
>6l and it runs fine 99% of the time.  Some of the newer TTfonts must
>be printed as graphics, however, slowing things down a bit.

NDPS (Novell's Distributed Print Services) will solve your problem,
or you could just install the printer drivers without all the
"user-friendly" executables.

------------------------------

Date: Thu, 5 Mar 1998 10:04:25 +0200
From: Eli Peleg <epeleg@CC.HUJI.AC.IL>
Subject: Re: Win95 nprinter

>Now I got the NRPINTER to execute, but now it says:
>
>"NPRINTER FILE "&0" COULD NOT BE FOUND" and ends the execution.

There is a TID on this. Make sure that the first time you launch
the program, it is in a 8.3 directory, not longer.

---------

Date: Thu, 5 Mar 1998 07:47:03 -0500
From: David Moon <dmoon@PERU.K12.IN.US>
Subject: Re: Win95 nprinter

>Now I got the NRPINTER to execute, but now it says:
>
>"NPRINTER FILE "&0" COULD NOT BE FOUND" and ends the execution.

Get the windows 95 remote printer from Novell.  Setup Pserver on the
fileserver to host the queue.

---------

Date: Thu, 5 Mar 1998 19:29:12 UTC+0200
From: Amador Hernandez <amador@ETSEIB.UPC.ES>
Subject: W95 NPRINTER

Thanks to all for all answers to my question about the error

"NPRINTER FILE "&0" COULD NOT BE FOUND".........

I found what it was: if you have the NPTWIN95.EXE in a directory with
long file names IT DOES NOT WORK.....since I changed the name of the
directory to a 8 char name, it works fine.

------------------------------

Date: Thu, 19 Mar 1998 12:39:04 +1200
From: "Baird, John" <BAIRD2@WHIO.LINCOLN.AC.NZ>
Subject: Anyone seen this before? (WARNING:  Error detected in Queue

>Recently one of my NW 3.12 servers started displaying this error message
>at the console.
>
>	WARNING:  Error detected in Queue. ID=0200001D
>
>The message shows up at the console 3 times, and it only seems to happen
>at night.  The only thing the server should be doing late at night is
>backing it self up (BackupExec 7.01)
>
>None of my print queue's have the ID 0200001D.  In fact I  listed the
>registry with JRB's LISTOBJ and there is no object in the registry with ID
>0200001D.

I suspect the error message itself contains an error. Normally when
displaying an object ID, the byte order of the 32 bit value comprising the
ID must be swapped. For example this is done when deriving the subdir
names of sys:mail from the object IDs. I would guess that you will find
a queue with object ID 1D000002.

If this allows you to identify the queue, then you can check it carefully
using pconsole. Chances are you won't spot a problem, so the simplest
solution is to delete and recreate the queue. The problem may lie in the
.SYS and/or .SRV files in the queue directory. These are held open by the
server, but can be deleted immediately after a reboot, before any queue
activity takes place (they will be automatically recreated), so thats another
possibility.

---------

Date: Thu, 19 Mar 1998 11:29:22 -0600
From: Andrew Hagen <ahagen@POP.ISDFA.SEI-IT.COM>
Subject: Re: Anyone seen this before? (WARNING:  Error detected in Queue

>>Recently one of my NW 3.12 servers started displaying this error
>>message at the console.
>>
>>   WARNING:  Error detected in Queue. ID=0200001D
>>[ ... deleted material ... ]

312ptc adds an NLM that can produce this message. From document
2934545,

====begin inserted piece of file======

    READQFIX NLM
    ============

    When a Queue is full, the File Server will get into an infinite
    loop trying to service Queue Management System (QMS) requests.
    Note that PCONSOLE makes QMS requests for building a list of jobs,
    inserting and deleting print jobs, as well as inserting and
    deleting print queues. Symptoms observed when this problem occurs
    include, but are not limited, to utilization up to 96 %, users
    loosing connections and Packet Receive Buffers count going high.

    By applying READQFIX.NLM, the file server can correctly process a
    QMS request for a queue which is full. Note that if a queue is
    full prior to loading READQFIX, the following error message may
    appear on the console at any time after loading READQFIX.

    "WARNING: Error detected in Queue. ID=xxxxxxxx"

    If this happens the queue with the given ID number should be
    deleted and recreated.


====end inserted piece of file======

------------------------------

