Problem
I have installed AFPS 4.0.2 and configured an HP plotter running HPGL2 on my OpenServer server via HPNP and have shared the printer out so it is accessible from a Windows NT4 WorkStation client.
On the Server side:
------------------
When I add the plotter to my Windows NT4 WorkStation client and use
the latest driver from HP I find that when I send a test print or a
plot from my Windows application the Print Manager shows 1 byte
transferred and remains locked, the "net print" command shows the
print in the queue with 1 byte and "scoadmin print" shows the print
in the queue with 1 byte. The Print Manager on the Windows client
then locks as the print appears to be in a loop.The "lmx.srv" process associated with the attached client consumes all
the CPU time and brings the server to 0% in the "sar" report. If you
run the command "lmstat -c <pid of lmx.srv>" this should show the name
of the client workstation your print has been generated from.In order to free the lmx.srv routine without re-starting AFPS or killing the process run:
# net session \\<client_name> /deleteand this will drop the session. In addition, you will need to run:# scoadmin printerand "Resume" the print job, currently queuing 1 byte. The print
should then appear and the client's Print Manager should then un-lock.Using the native drivers shipped with Windows NT4 WorkStation this problem is not evident, however, these native drivers will not support the latest plotters available from HP.
For example, the native HP DesignJet 650C (C2859B) works but the latest HP DesignJet 650C (C2859B) by HP doesn't work.
This problem is not evident on the same server running AFPS 3.5.2n.
This problem is not evident using Windows 2000 client.
Error messages seen in the Event Viewer include:
Error 1723 - RPC server too busy to complete this operation An Illegal SMB error was received event 6280
On the Windows Client side: -------------------------- If I right click on the "Properties" of the printer on Windows NT4 or Windows 2000 I cannot see any port settings for the printer. This means that should you need to change any "port" settings such as turning off Bi-directional printing, then this is not possible.
It is possible for printing ports to be seen by using a Registry Change called "DisableUpLevelPrinting" which is available from:
Local Machine->System->CurrentControlSet->Services->AdvancedServer->ParametersIf you make this change and stop & start AFPS then on the clients you will need to stop and start the Windows Print Spooler, via:
MyComputer->Right Click Manage->Services & Apps->Services->Print SpoolerThis will enable you to see the ports but you will not be able to print nor will you be able to remove the port even if you disable the registry key again.
Below is a list of clients and what ports are created and are configurable by printers created on AFPS 3.5.2n and 4.0.2:
Win95 WinNT Win2K
------------------------------------------------------------------------------
Port Port Port Port Port Port
Created? Configurable? Created? Configurable? Created? Configurable?AFPS3.52 Yes n/a Yes Yes Yes No
NT4Server Yes n/a Yes Yes Yes No
AFPS4.02 Yes n/a No No No NoWhen attaching a printer to true NT4 Server then a port is created on a Windows 2000 client but creating a port manually using:
Start->Settings->Printer->File->Server Properties->Add Port->Local
Port->\\<server>\<printer_share>on Windows 2000 or Windows NT4 WorkStation and attaching a printer to that port still does not rectify the issue.
AFPS 4.0.2 implements the full capabilities of Window NT's SPOOLSS
which is the protocol that a NT client uses to communicate with an NT
print server. AFPS 3.5.2 did not implement SPOOLSS and was thus doing
printing in a downlevel way comparable to that provided by older LAN
Manager servers or Window 9X clients. Cause
On the Server Side:
------------------
NT 4.0 sends a 1 byte print job in advance of the real print job.This 1 byte print job never actually gets to the printer but is, instead, immediately deleted by the NT workstation before the job is placed on the spooler queue.
It is the reason you keep seeing an email message to root reporting a print job was canceled by the administrator.
The HP driver is sending a 64K block of print data to the server and that is causing the server to return an error.
The problem appears to be due to the value 65536 (the number of data
bytes), stored as an integer, getting passed to the WriteSpoolFile()
function as a 2-byte short, and that results in a big fat zero. This
causes an error when that function attempts to write zero bytes to the
spool file. The error prompts the driver to resend the data, and this
happens repeatedly, thus causing the lmx.srv process to thrash. Solution
On the Server Side:
------------------
The problem of "lmx.srv" consuming all the CPU time and only having
1 byte in the print queues has been reported and fixed by SCO
Engineering for the Server side with a replacement "lmx.srv" daemon.On the Windows Client Side:
--------------------------
The problem of DisableUpLevelPrinting not working on the clients has
been reported and fixed by SCO Engineering with the same replacment
"lmx.srv" daemon above.A possible workaround would be to print to the plotter using LPR either directly or via the OpenServer server.
Obtaining the fix:
-----------------
This fix will be available in APP619B available at:https://ftp.scoexpert.com/openserver5/ See also
lmstat(AS)http://www.dewassoc.com/support/networking/bidiprint.htmhttp://bizforums.itrc.hp.com/cm/QuestionAnswer/1,,0xd6c53a7b3682d611abdb0090277a
778c,00.html