From: root@alijku65 (Gerald Hanusch) Subject: Re: printing to/from remote machines Date: Fri, 16 Apr 1993 14:23:25 CDT
Bill E. Eickmeier (bee@watarts.uwaterloo.ca) wrote:
<deleted>
: [38]% ls -l /etc/hosts.lpd
: -rw-r--r-- 1 root root 116 Apr 12 11:02 /etc/hosts.lpd
: -----
: [39]% cat /etc/hosts.lpd
: otherbox.uwaterloo.ca
: -----
: [40]% grep 35/tcp /etc/services
: lp 35/tcp # any private printer server [JBP]
: printer 35/tcp # any private printer server [JBP]
BSD LPR Service uses 515/tcp instead od 35/tcp, which is used by SysV lp Service.
: Here's how things look when I try to print from a remote machine to my
: linux printer (this originally worked fine, but has since stopped):
: Spool queue: lp_linuxbox
: Local (waiting to be sent to remote site):
: otherbox: waiting for linuxbox to come up since Wed Apr 14 15:18:55 1993
: (errno=60 'Connection timed out')
: 1st bee 10 temp 3030 bytes
: Remote(linuxbox):
: ...right here I hit ctrl-c since it seems to hang...
This error seems to be a Kernel-TCP Bug, a guy an myself had exactly the
same effects, when we upgraded from 99pl4 to 99pl7 or 99pl8.
I have traced the Ethernet traffic with the PD "Gobbler" Packet
Analyzer and found, that the Linux box sends a few tcp packets to
the remote printer server and the gets a major timeout problem.
If the printer server acknowledges to slow to the linux tcp packets,
linux tcp seems not to handle the new SYN packets correctly.
When I use the old 99pl4, and trace it, the sequence is correct,
and if SYN is needed due to slow printer servers, its recovered ok.
On 99pl8 TCP the trace looks like this : 5 - 6 packets sent, Linux TCP
doesn't wait for the ACK and opens a new source port without closing
the old one. Perhaps Linus can help ?
: Any and all ideas are welcome...
me too , :-),
Temp. solution: use 99pl4 kernel if you want LPR package to print
on (slow) remote printers.
Kind regards, Gerald
(Posted from a Linux Box with 99pl4 using TIN)