I frequently need to print to a remote system which in turn prints to a
remote network printer or off-site location which will only allow one of
my hosts into their hosts.lpd file. This works great as long as the
receiving host is not running DU4.0. If it is, a message comes back from
lpq "waiting for <remote-host> to come up". On a normal receiving host a
socket would be assigned temporarily to the sending host, another would be
assigned to the remote printer, and the job would be sent on. On the 4.0
host, the sending host receives a socket, but no socket is created to the
remote printer. Also, lpq is not able to get queue information from the
remote site, but does not generate an error.
I tried exchanging the 3.2 lpd for the 4.0 one without success. As it is
now, I am keeping one machine at 3.2 as a print server. If anyone (DEC?)
has any idea why lpd is failing, please let me know.
Thanks,
Don Bovee, bovee_at_amath.washington.edu
Received on Fri Oct 18 1996 - 01:19:23 NZDT