On Fri, 4 Apr 2003 07:18:50 -0500
Michael Bevilacqua <[EMAIL PROTECTED]> wrote:
> On Fri, Apr 04, 2003 at 06:09:49AM -0500, Tom Allison wrote:
> > Tried both, no luck.
>
> Sorry if I missed some of this thread, but did you increase the logging
> level to look at the problem? I find that helped m
On Fri, Apr 04, 2003 at 06:09:49AM -0500, Tom Allison wrote:
> Tried both, no luck.
Sorry if I missed some of this thread, but did you increase the logging
level to look at the problem? I find that helped me at first.
Also, I wrote up a small howto that has some gotchas in it, maybe you
can give
[EMAIL PROTECTED] wrote:
On Thu, 03 Apr 2003 21:46:06 -0500
Tom Allison <[EMAIL PROTECTED]> wrote:
sudo lpadmin -p Kyocera -E -v socket://192.168.0.100 -m
Kyocera-FS-1900-Postscript.ppd
lpadmin: add-printer failed: server-error-service-unavailable
lpadmin: add-printer failed: server-error-servi
On Thu, 03 Apr 2003 21:46:06 -0500
Tom Allison <[EMAIL PROTECTED]> wrote:
> sudo lpadmin -p Kyocera -E -v socket://192.168.0.100 -m
> Kyocera-FS-1900-Postscript.ppd
> lpadmin: add-printer failed: server-error-service-unavailable
> lpadmin: add-printer failed: server-error-service-unavailable
>
[EMAIL PROTECTED] wrote:
On Thu, 03 Apr 2003 06:06:05 -0500
Tom Allison <[EMAIL PROTECTED]> wrote:
| I started to try this approach and died here:
|
| Setting up cupsys (1.1.15-4) ...
| Starting CUPSys: cupsd.
I have what is supposed to be a network printer with support for
JetDirect, Cups and
On Thu, Apr 03, 2003 at 05:43:40PM -0500, [EMAIL PROTECTED] wrote:
| It bears noting in all this that when in CUPS you use "lp" commands
| they come from the cupsys-bsd package, which provides same-named
| replacements for traditional printing commands.
Close. The "lp", "lpstat", "cancel", etc. c
It bears noting in all this that when in CUPS you use "lp" commands they come from the
cupsys-bsd package, which provides same-named replacements for traditional printing
commands.
They are not the same "lp" commands you read about in Linux books and other places.
Kevin
--
To UNSUBSCRIBE, em
On Thu, Apr 03, 2003 at 09:17:23AM -0500, [EMAIL PROTECTED] wrote:
| > On Thu, 03 Apr 2003 06:06:05 -0500
| > Tom Allison <[EMAIL PROTECTED]> wrote:
| >
| >> > | I started to try this approach and died here:
| >> > |
| >> > | Setting up cupsys (1.1.15-4) ...
| >> > | Starting CUPSys: cupsd.
| >
| >
> On Thu, 03 Apr 2003 06:06:05 -0500
> Tom Allison <[EMAIL PROTECTED]> wrote:
>
>> > | I started to try this approach and died here:
>> > |
>> > | Setting up cupsys (1.1.15-4) ...
>> > | Starting CUPSys: cupsd.
>
>> I have what is supposed to be a network printer with support for
>> JetDirect, Cups
On Thu, 03 Apr 2003 06:06:05 -0500
Tom Allison <[EMAIL PROTECTED]> wrote:
> > | I started to try this approach and died here:
> > |
> > | Setting up cupsys (1.1.15-4) ...
> > | Starting CUPSys: cupsd.
> I have what is supposed to be a network printer with support for
> JetDirect, Cups and LPD.
Derrick 'dman' Hudson wrote:
On Wed, Apr 02, 2003 at 06:14:12AM -0500, Tom Allison wrote:
| Derrick 'dman' Hudson wrote:
| >I would first install the 'cupsys' package. Then add a local queue
| >for the printer (use either the lpadmin command or the web interface
| >which you'll find at http://loca
On Wed, Apr 02, 2003 at 06:14:12AM -0500, Tom Allison wrote:
| Derrick 'dman' Hudson wrote:
| >I would first install the 'cupsys' package. Then add a local queue
| >for the printer (use either the lpadmin command or the web interface
| >which you'll find at http://localhost:631/). Specify the co
Derrick 'dman' Hudson wrote:
On Sun, Mar 30, 2003 at 07:02:49AM -0500, Tom Allison wrote:
| I have a printer which runs on a network connection.
|
| I scanned for ports and found ports associated with lpd (515), cups (631),
| and jetdirect (9100?) and was trying to configure a cups client.
Sound
On Sun, Mar 30, 2003 at 07:02:49AM -0500, Tom Allison wrote:
| I have a printer which runs on a network connection.
|
| I scanned for ports and found ports associated with lpd (515), cups (631),
| and jetdirect (9100?) and was trying to configure a cups client.
Sounds like an HP JetDirect card c
On Sun, Mar 30, 2003 at 07:02:49AM -0500, Tom Allison wrote:
> And nothing, so I removed it and tried:
There are a few known gotcha's with CUPS. I wrote up an install summary
that you can take a look at to check against your install work if you
like. It's located at:
http://www.bevilacqua.us/HowT
On Sun, 30 Mar 2003 07:02:49 -0500
Tom Allison <[EMAIL PROTECTED]> wrote:
> So I tried configuring it a direct configuration:
>
> foomatic-configure -s cups -n remoteraw -c socket://192.168.0.100:631/
> foomatic-configure -s cups -D -n remoteraw
>
> And nothing, so I removed it and tried:
>
>
I have a printer which runs on a network connection.
I scanned for ports and found ports associated with lpd (515), cups (631),
and jetdirect (9100?) and was trying to configure a cups client.
I installed the following packages:
a2ps
cupsys-bsd
cupsys-client
foomatic-bin
foomatic-db
I tried to s
Hi,
your set up looks fine (we have the same set up as you here at our office,
JetDirect's work fine with the Debian/Linux lpr package). What you need
to do to get rid of that banner page is to telnet to the JetDirect
box and disable the banner page:
canaima:~# telnet hplj4p
Trying 130.151.17.167
Hello All:
I have been settin up one of our Debian machines to serve as a
departmental printer server for Macs and Windows95 machines. The problem
I am having is with an HP LaserJet 4m+ with JetDirect card. The printer
has its own IP number and it is directly connected to the network. I have
se
19 matches
Mail list logo
