I also posted this on the AIX forum in hopes of getting help.
I am trying to setup remote printing from a Linux machine (Red Hat 5.3) to an AIX machine (AIX 5.3). Remote printing for "normal" print jobs is working out OK, but I'm having trouble with some AIX printers that have a user defined backend.
I turned on logging for lpd on the AIX machine. When lpd submits the job using enq, it includes the option "-fl". From the lpd debug log:
I'm thinking it's a problem on the Linux side, because when I print from another AIX machine, there is no "-fl" included:
The "-fl" flag is getting passed to our backend process, which already has a -f option being supplied so it's failing. I can't find why/where the "-o-fl" is being submitted to enq, either on the Linux or AIX side. I can't seem to get detailed logging on the Linux side.
I am setting up a unix remote print server for approximately 500 printers. We send about 1,000 print jobs per day over the WAN. I am looking for hardware specs. I know I can overkill, but would rather get a sensible machine. Any suggestions? (2 Replies)
I am using Sco Openserver 5.0.6 and I have an Okidata 16n printer on a GETNET print server.
I am able to print to the printer. However I am having display issues.
Normally when I setup a local printer I am able to tell it what model to use. Ex.(HPLaserJet).
When I setup the remote... (2 Replies)
I'm trying to print from my Solaris server to a Windows Print Server
The Print Server will then pass the print job to a PC connected via dial-up and print it locally.
EG:
Solaris
-----
| |
| |
------
/88888/
-------
\
/
... (1 Reply)
I am looking for a dial-up remote printing solution as under :
1. We have a Centralized location where Sun Solaris (A) is installed. From here printing command will be despatched.
2. This printing command will be routed to WAN cloud to Main Branches (B1,B2,B3)and from there, printer at... (0 Replies)
Hi all,
I am an amature in AIX.I am facing a problem with remote printing in AIX5L...
One laser printer is there connected to a print server (HP),which is configured as remote printer from AIX Server.
Due to some problem the print server is replaced and the same is configured with the old... (3 Replies)
Dear Sir
Please how can I print a job localy with my printer while a server from where I am working belong to another network?
Actulally to print a job I am oblige to :
1rst to print it inside a file
2nd coping the file to my network (rcp)
3rt sending the file to my local printer (lp... (2 Replies)
Hello,
I am trying to setup remote printing from a Linux machine (Red Hat 5.3) to an AIX machine (AIX 5.3). Remote printing for "normal" print jobs is working out OK, but I'm having trouble with some AIX printers that have a user defined backend.
I turned on logging for lpd on the AIX... (0 Replies)
Sir, i have a sco 5.5 installed server and 6 clients connected through pci specialix card and printing working fine in these all terminals. 7 and 8 ports are free now, i need to setup another terminal for login on through 7 or 8 port for remote login. i connect a external modem using 25 pin male... (2 Replies)
Hello all.
I am setting up a queue under AIX 4.2.1 to print to a remote Linux CUPS queue. At present I can print to the queue remotely from Windows but not AIX. What I am seeing is lpstat reads the state of the remote queue but at job submission time I am getting backend exit fatal errors. The... (4 Replies)
We are using Red Hat. We have a issue like this: We want to print from Linux, to a printer attached to a Windows machine. What we want to print is a PDF. It prints, but the printing starts from the middle of the page. In the report, there is no space at the top but still printing starts from the... (5 Replies)
Discussion started by: rohan69
5 Replies
LEARN ABOUT OPENDARWIN
cups-lpd
cups-lpd(8) Apple Inc. cups-lpd(8)NAME
cups-lpd - receive print jobs and report printer status to lpd clients
SYNOPSIS
cups-lpd [ -h hostname[:port] ] [ -n ] [ -o option=value ]
DESCRIPTION
cups-lpd is the CUPS Line Printer Daemon ("LPD") mini-server that supports legacy client systems that use the LPD protocol. cups-lpd does
not act as a standalone network daemon but instead operates using the Internet "super-server" inetd(8) or xinetd(8). If you are using
inetd, add the following line to the inetd.conf file to enable the cups-lpd mini-server:
printer stream tcp nowait lp /usr/lib/cups/daemon/cups-lpd cups-lpd
-o document-format=application/octet-stream
Note: If you are using Solaris 10 or higher, you must run the inetdconv(1m) program to register the changes to the inetd.conf file.
If you are using the newer xinetd(8) daemon, create a file named /etc/xinetd.d/cups containing the following lines:
service printer
{
socket_type = stream
protocol = tcp
wait = no
user = lp
group = sys
passenv =
server = /usr/lib/cups/daemon/cups-lpd
server_args = -o document-format=application/octet-stream
}
OPTIONS -h hostname[:port]
Sets the CUPS server (and port) to use.
-n
Disables reverse address lookups; normally cups-lpd will try to discover the hostname of the client via a reverse DNS lookup.
-o name=value
Inserts options for all print queues. Most often this is used to disable the "l" filter so that remote print jobs are filtered as
needed for printing; the examples in the previous section set the "document-format" option to "application/octet-stream" which forces
autodetection of the print file format.
PERFORMANCE
cups-lpd performs well with small numbers of clients and printers. However, since a new process is created for each connection and since
each process must query the printing system before each job submission, it does not scale to larger configurations. We highly recommend
that large configurations use the native IPP support provided by CUPS instead.
SECURITY
cups-lpd currently does not perform any access control based on the settings in cupsd.conf(5) or in the hosts.allow(5) or hosts.deny(5)
files used by TCP wrappers. Therefore, running cups-lpd on your server will allow any computer on your network (and perhaps the entire
Internet) to print to your server.
While xinetd has built-in access control support, you should use the TCP wrappers package with inetd to limit access to only those comput-
ers that should be able to print through your server.
cups-lpd is not enabled by the standard CUPS distribution. Please consult with your operating system vendor to determine whether it is
enabled on your system.
COMPATIBILITY
cups-lpd does not enforce the restricted source port number specified in RFC 1179, as using restricted ports does not prevent users from
submitting print jobs. While this behavior is different than standard Berkeley LPD implementations, it should not affect normal client
operations.
The output of the status requests follows RFC 2569, Mapping between LPD and IPP Protocols. Since many LPD implementations stray from this
definition, remote status reporting to LPD clients may be unreliable.
SEE ALSO cups(1), cupsd(8), inetconv(1m), inetd(8), xinetd(8),
http://localhost:631/help
COPYRIGHT
Copyright 2007-2011 by Apple Inc.
4 August 2008 CUPS cups-lpd(8)