Article ID: 867519
Article Last Modified on 10/30/2006
APPLIES TO
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Professional Edition
Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows Registry
SYMPTOMS
When you send a large print job from a computer that is running IBM AIX and SAP software to a Microsoft Windows 2000-based server that is running the Line Printer Daemon (LPD) service, the print job is not printed. Additionally, the following event is logged in the Application log:
Event Type: Warning
Event Source: LPDSVC
Event Category: None
Event ID: 4010
Date: 02.04.2004
Time: 09:48:35
User: N/A
Computer: ComputerName
Description:
Request from IPAddress could not be satisfied: possibly due to network problems
However, when you send a small print job from the same AIX-based computer to the same Windows 2000-based server, the print job may be printed correctly.
CAUSE
This problem occurs because the Windows 2000-based computer uses a time-out period. The time-out period stops the LPD server from waiting for print jobs that are corrupted or that have stopped before being completed.
By default, the time-out period is 60 seconds. When the problem that is described in the "Symptoms" section occurs, the AIX-based computer sends a Receive Job command and then creates the print job file. The print job file is then sent to the Windows 2000-based computer. If it takes longer than 60 seconds to create the print job file and send the print job file to the print server, the print job times out. The Windows 2000-based computer then responds with a negative acknowledgement, and the print job is canceled.
RESOLUTION
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.
To resolve this problem, install Windows 2000 Service Pack 3 or the hotfix that is mentioned in the following Microsoft Knowledge Base article on the Windows 2000-based computer:
280344 Large print jobs time out after 60 seconds in Windows Server 2003 and in Windows 2000 Server
After you have installed Windows 2000 Service Pack 3 or the hotfix mentioned in Knowledge Base article, create the following registry entry to configure the LPD service time-out value:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LPDSVC\Parameters
To do this, follow these steps:
- Click Start, click Run, type regedit, and then click OK.
- Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LPDSVC\Parameters - On the Edit menu, click Add, and then click DWORD Value.
- Name the new value RecvTimeout.
- Right-click RecvTimeout, and then click Modify.
- In the Edit DWORD Value dialog box, click to select the Decimal check box, and then enter a value between 60 and 1200 seconds in the Value data box.
For example, if you want the wait time-out to be longer than 60 seconds, you can enter 120 or 240 in the Value data box. - Quit Registry Editor.
Depending on the size of the print job and the quality of the network connection, you may want to configure SAP on the AIX-based computer to use a longer time-out period. To set a longer time-out period, modify the following default time-out values on the AIX-based computer:
- rspo/tcpip/timeout/connect = 120
- rspo/tcpip/timeout/read = 120
- rspo/tcpip/timeout/write = 120
- rspo/tcpip/retrytime = 60
- rspo/tcpip/retries = 5
- rspo/host_spool/check_retries = 5
The third-party products that this article discusses are manufactured by companies that are independent of Microsoft. Microsoft makes no warranty, implied or otherwise, regarding the performance or reliability of these products.
Keywords: kb3rdparty kbtshoot kbprb KB867519
