From owner-freebsd-questions Wed Jan 10 15:39:54 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id PAA13058 for questions-outgoing; Wed, 10 Jan 1996 15:39:54 -0800 (PST) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id PAA13052 for ; Wed, 10 Jan 1996 15:39:51 -0800 (PST) Received: from gemini.sdsp.mc.xerox.com ([13.231.132.20]) by alpha.xerox.com with SMTP id <14661(1)>; Wed, 10 Jan 1996 15:39:06 PST Received: from gnu.mc.xerox.com (gnu.sdsp.mc.xerox.com) by gemini.sdsp.mc.xerox.com (4.1/SMI-4.1) id AA16271; Wed, 10 Jan 96 18:38:59 EST Received: by gnu.mc.xerox.com (4.1/SMI-4.1) id AA10437; Wed, 10 Jan 96 18:38:58 EST Message-Id: <9601102338.AA10437@gnu.mc.xerox.com> To: Randy Berndt Cc: freebsd-questions@freebsd.org Subject: Re: 'tickling' remote lpd In-Reply-To: Your message of "Wed, 10 Jan 1996 13:35:24 PST." <2.2.16.19960110153135.1dd70b76@nething.com> Date: Wed, 10 Jan 1996 15:38:53 PST From: "Marty Leisner" Sender: owner-questions@freebsd.org Precedence: bulk In message <2.2.16.19960110153135.1dd70b76@nething.com>, you write: >I have a remote printer that has stopped working. I have rebooted >the remote machine, and lp'ing a job locally on that machine prints. >(I have successfully printed remotely before, it just stopped working.) > >When I do a 'lpq -Premote', it tells me it is waiting for xx.xx.xx.xx >to come up. How do I convince the local lpd to try again? I have killed >and restarted lpd on the local machine, but it is still waiting. > >I can ping the remote, telnet to the remote and the remote can telnet >to me. > >NOTE: I am subscribed to the digest version of this list, and I need this >answer quickly. Please email me DIRECTLY. > >Thanks. > >Randy Berndt >---------------------------------- >AOS/VS, FreeBSD, DOS: >I'm caught in a maze of twisty little command interpreters, all different. > lpd is very strange...(it retries quickly a few times, then it retries some time (hours?) later... (my take is it wasn't written for networking initially, someone had the brilliant (-; idea to "lets extend this for ethernet! Maybe look at plp... Are you sure lpd is running on the remote is running lpd? Do you kill all the instances on all machines? Also, use tcpdump or snoop to watch the network activity...and see what the packets look like... marty