31 Jul
2005
31 Jul
'05
8:09 p.m.
Hi,
On Sun, Jul 31, 2005 at 03:34:51PM +0200, Patrick Useldinger wrote:
Eric Dondelinger wrote:
Thanks for the tip, I learned something :-)
In the end, the problem was entirely unrelated to any configuration
issues: it seems the printer got hit by a power surge (similarly to
the ADSL router, during one of the heavier thunderstorms these days),
and needed to be entirely separated from it's source of electricity
for a while, after which it resumed functioning normally.
Greetings, Eric
I'd have tried configuration or at least more
testing via CUPS in
http://localhost:631, but unlike Debian GNU/Linux systems, this one
doesn't take the root / rootpassword as authentication.
As root, use the command "lppasswd -a <userid>" to add user
<userid> and
set the CUPS admin password for that user. You can then use that
userid/passwd combination to access http://localhost:631/admin.