For RFC compliance, the TCP source ports used are 721 - 731. TCP/IP
protocol has a timeout of 4 minutes when it will not reuse a port until 4
minutes after it was released. You can change this timeout or force LPR out
of RFC compliance
TCP/IP protocol
http://support.microsoft.com/default.aspx?scid=kb;en-us;314053
TCP/IP and NBT Configuration Parameters for Windows XP
change TcpTimedWaitDelay
Key: Tcpip\Parameters
Value Type: REG_DWORD - Time in seconds
Valid Range: 30-300 (decimal)
Default: 0xF0 (240 decimal)
Description: This parameter determines the length of time that a connection
stays in the TIME_WAIT state when being closed. While a connection is in the
TIME_WAIT state, the socket pair cannot be re- used. This is also known as
the "2MSL" state, as by RFC the value should be twice the maximum segment
lifetime on the network. See RFC793 for further details.
LPR out of compliance
http://support.microsoft.com/default.aspx?scid=kb;en-us;179156
Updated TCP/IP Printing Options for Windows NT 4.0 SP3 and Later
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto
This posting is provided "AS IS" with no warranties, and confers no rights.
danny_dion said:
I need to print "Label" to a Zebra LP 2844.
I want use LPR port to my server 2000 to reach LPD to my windows XP pro.
The printing is Ok if I print Label One by one.
If many print jobs come to the Server spooler, the printing hang for 2-3 minutes
and then continue without errors after this time.
I tried with different printer and always the problem.
Someone know if parameters existe to bypass the 2-3 minutes waiting time?
