RE: LPR printing problem generating event ID: 4010

Tech-Archive recommends: Fix windows errors by optimizing your registry

From: Bill Peele [MS] (bpeele_at_online.microsoft.com)
Date: 02/04/04


Date: Wed, 04 Feb 2004 19:40:16 GMT

--------------------
From: rein.poelman@gecapital.com (Rein)
Newsgroups: microsoft.public.win2000.printing
Subject: LPR printing problem generating event ID: 4010
Date: 2 Feb 2004 03:23:46 -0800

Recently we have migrated from an Nt4 server to a Windows 2000 server
Sp4.
On the NT4 server we had print queue's with LPR printing, used by our
SAP server

Our SAP server now prints via the print queue on the windows 2000
server.
We still use the same HPJetdirect printboxes connected printers.
the only thing changed is the swap of NT4 to Windows 2000.

We made the changes to the registry as suggested in Kb168457 and Kb
150930
The problem we have is that sometimes there is a 30 minute delay in
printing. Only after 30 minutes or so a print appears in the print
queue.
While at other times the printing is very swift and takes less than a
minute.

The following error appears in the server's system log:

Source: LDPSVC
Event ID: 4010
Request from [ip_address] could not be satisfied: possibly due to
network problems.

Pinging the SAP server continiously with pingplotter does not indicate
a we have a network problem.
Setting the printer to: print directly to the printer did not have any
effect
Enabling LPR byte count had no effect.

Does anyone have any suggestions how to tackle this problem?

thanks in advance,
Rein

--
First make sure we have the changes per the following article added, since this still applies to LPR/LPD printing on 
Windows 2000.
     179156 - Updated TCP/IP Printing Options for Windows NT 4.0 SP3 and Later
     http://support.microsoft.com/default.aspx?scid=kb;[LN];179156
I have also heard that if we have the value Tcp1323Opts in the registry key HKLM\\System\CurrentControlSet\Services
\Tcpip\Parameters and it is set to anything other than 0 (zero) then behavior like this can happen.  The article below talks 
more about this value.
     224829 - Description of Windows 2000 TCP Features
     http://support.microsoft.com/default.aspx?scid=kb;[LN];224829
Bill Peele
Microsoft Enterprise Support
This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the 
terms specified at http://www.microsoft.com/info/cpyright.htm 
Note:  For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread 
from which they originated. 


Relevant Pages

  • Re: LPR printing problems with Windows Server 2003
    ... servers to track printing costs. ... Pcounter I was running (version 2.50 windows) had an issue. ... Novell printer object that prints using LPR to the aforementioned printer ... LPR printing through the Windows 2003 server, ...
    (microsoft.public.windows.server.general)
  • Re: LPR printing problems with Windows Server 2003
    ... We are running Pcounter on both the Novell and Windows ... servers to track printing costs. ... Pcounter I was running (version 2.50 windows) had an issue. ... LPR printing through the Windows 2003 server, ...
    (microsoft.public.windows.server.general)
  • Re: SDK PrintSDI sample wont work on W2000
    ... Microsoft Printing, Imaging and Fax Team ... as I do on Windows XP where it does work (with the same ... > server and the same fax printer on the server). ... to send faxes using the remote printer. ...
    (microsoft.public.win2000.fax)
  • RE: migrate NT4 server to Windows 2003 server
    ... Yes, use ADMT v2.0 can help you to migrate the user accounts, groups, ... computer accounts from Windows NT 4 Domain to Windows 2003 Active ... Install the new server as NT4 BDC. ... migrate NT4 server to Windows 2003 server ...
    (microsoft.public.windows.server.migration)
  • Re: Server 2003 and NT Workstations
    ... printing in a mixed NT 4/2000 or 2003 environment is fraught ... See in particular references to "compatible drivers". ... ".Net server"). ... One possibility is to build a Windows NT 4 server just to be a print server ...
    (microsoft.public.win2000.printing)