Hi All,

I'm trying to test kerberos/lprng interaction, but before I can do
that I need to have a simple client/server setup.

Basically what I have is:

host1 running lpd with printer 'lp' set up (all is fine here)
host2 not running lpd, printing to remote queue on host1 via printcap
entry:

lp:
    :lp=lp@host1:client

This doesn't work at all however:

[host2]toby: lpq -Plp
Printer 'lp@localhost' - cannot open connection - Connection refused
Make sure the remote host supports the LPD protocol
[host2]toby:

Doing lpq -Plp@host1 is OK.

... although what I'm trying to do does work OK under an old version
of LPRng (3.6.12).

However, if I include the :direct keyword on the client-side printcap
entry, I can print to the remote queue OK, although I get no feedback:

[host2]toby: lpq -Plp
Printer: lp - direct connection to device 'lp'
[host2]toby:

So, this (and the parts in the HOWTO relating to :direct) suggests to
me that I'm not doing this the correct way - is this the case?

If so, what is the correct way to use print clients to a remotely
hosted printer?

I can't help thinking that I must be missing something blindingly
obvious, but really have no idea what it could be.  Any help
gratefully received.

Thanks
Toby Blake
University of Edinburgh

-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address

If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
with:                           | example:
subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]

If you have major problems,  send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------

Reply via email to