cannot print over network, using cups

all of a sudden i cannot print to my printer that i set up through cups earlier this week.

after the print screen comes up, i press print but there is no follow up message or error. when i pull up the cups management there is still no job that was canceled or has an error. it is as if cups is not receiving the job.

additionally, when i go to print a test page through cups management it says this printer is not accepting new jobs.

please advise,
bam

Tried starting the printer ? it’s one of the options in printers section of cups

Andy

ruled out hardwareproblems?

Andy: I do see the button that says “Accept Jobs”. Tried clicking it. Got this error:

401 Unauthorized
Enter your username and password or the root username and password to access this page. If you are using Kerberos authentication, make sure you have a valid Kerberos ticket.

cant quite figure out how to authenticate.

I seem to have multiple issues related to authentication on this machine. Cant get email to function proper as well…

b

printer prints for other computers on same network.
one is a mac the other is a windows box.
this linux machine is the only one that will not print, now.
b

On Wed October 8 2008 11:06 am, bmccall17 wrote:

>
> deltaflyer44;1880988 Wrote:
>> Tried starting the printer ? it’s one of the options in printers section
>> of cups
>>
>> Andy
>
> Andy: I do see the button that says “Accept Jobs”. Tried clicking it.
> Got this error:
>> 401 Unauthorized
>> Enter your username and password or the root username and password to
>> access this page. If you are using Kerberos authentication, make sure
>> you have a valid Kerberos ticket.
>
> cant quite figure out how to authenticate.
>
> I seem to have multiple issues related to authentication on this
> machine. Cant get email to function proper as well…
>
> b
>
>
bmccall17;
There should be an authentication box that appears, for user name enter: root;
for password enter: <root’s password>.

P. V.
Cogito cogito ergo cogito sum.

The box appeared at one point. But now it no longer appears. Is there a cookie I can clear or something that would cause the software to re-prompt me?

On Fri October 10 2008 01:46 am, bmccall17 wrote:

>
> PV;1881104 Wrote:
>> On Wed October 8 2008 11:06 am, bmccall17 wrote:
>>
>> >
>> > deltaflyer44;1880988 Wrote:
<snip PV>
>> bmccall17;
>> There should be an authentication box that appears, for user name
>> enter: root;
>> for password enter: <root’s password>.
>> –
>> P. V.
>> Cogito cogito ergo cogito sum.
>
> The box appeared at one point. But now it no longer appears. Is there
> a cookie I can clear or something that would cause the software to
> re-prompt me?
>
>
bmccall17;

More likely something like kdewallet or some similar application. In any event
you will not need to authenticate until you try to write a change to the Cups
server. If all else fails, try creating a new user and use that account to see
if it works with that account. If it works with the new user, you know the
problem is with your user’s config; if it does not work then Cups must be
mucking up. If it’s Cups try restarting Cups. (In a terminal su to root and
enter “rccups restart” [no quotes]. Actually I might try this first.)

P. V.
Cogito cogito ergo cogito sum.

here is what I got:

bash: rccups: command not found

huh?

On Fri October 10 2008 07:36 pm, bmccall17 wrote:

> here is what I got:
> bash: rccups: command not found
>
> huh?
>
> PV;1881801 Wrote:
<snip>

>> If it’s Cups try restarting Cups. (In a terminal su to
>> root and
>> enter “rccups restart” [no quotes]. Actually I might try this first.)
>> –
<snip>
>

bmccall17:

Did you su to root first? If so and it still does not work, then again su to
root and try:

“/etc/init.d/cups restart” [no quotes]

P. V.
Cogito cogito ergo cogito sum.

i tried http://localhost:631/ in firefox instead of konquerer. it prompted me for the username and password.

i was successfully able to set it to accept jobs again!!.a

Additionally, I found that if I cleared my cookies in konquerer then i was prompted again through cups and was able to fix my issues.

Amazing, how something as simple as a cookie setting can reek such havoc.

be well
Thank you.