On Fri, 27 Feb 2004, Anthony Ewell wrote:Hi Ryan,
Dudes! The error was from LPRng Tool! From Chapter 11 of the above:
Well, if you read your original post, LPRngTool wasn't mentioned until several items in, leading me to beleive that you had edited by hand to set up the queues -- otherwise, not being familiar with LPRngTool, I probably would not have chimed in. ;)
The following is an example of a simple printcap entry that can be used to send a job to a remote printer using the RFC1179 protocol: # *LPRng* syntax
# :lp value is 'where to print the job' lp: :[EMAIL PROTECTED]
# OR Vintage BSD Print Spooler Syntax # (*LPRng* supports this as well) # :rp = remote printer, :rm = remote machine or host lp: :rp=raw:rm=10.0.0.1
I also want the TCP/IP (jet direct, etc.) section of LPRng Tool
to allow
me to add the queues name (rp) to it.
Umm... nuh-uh. See, this is where it seems like there's some confusion. When printing via TCP/IP on the JetDirect interface, there are NO queues and you print on port 9100. If you want to print to an "rp" on a remote printer, you are speaking of RFC1179 LPR printing -- distinctly different. One cannot (again, to my knowledge) combine the two. Perhaps in LPRngTool you have somehow selected LPR and TCP/IP simultaneously and this is why it's doing this...?
Sorry this has taken so long to get back. I have to support the windows world as well
and they are all virused up to their noses!
Looking at my LRPng Tool, I see the following choices: device, queue, tcp/ip, smb yada.
I am connecting to a three parallel port Jet Direct box, with the following queues: raw1,
raw2, raw3.
The Jet Direct box says it supports "tcp/ip". Now since I know nothing about RFC1179,
I am tempted to select "tcp/ip". And my queue disappears. You are saying this is because
I chose the option.
Here is the problem. LPRng Tool SHOULD NOT require me to 1) do any hand work
after it is run and 2) research any RFC's to figure out what the selections stand for. The
solution is to make the choices a little more explanatory. Here I would submit my humble
suggestions:
old: device new: device (direct connect) old: tcp/ip new: lpr/lpd (jet direct)
Just anything that keeps me from having to be a "wizard" to use the tool.
Oh, any LPRng Tool still needs to correct the [EMAIL PROTECTED]:9100 problem.
--Tony
----------------------------------------------------------------------------- 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. -----------------------------------------------------------------------------
