public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: reader@newsguy.com
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user]  Re: [OT] print to printer on winxp via cups samba smb
Date: Wed, 13 Sep 2006 20:10:31 -0500	[thread overview]
Message-ID: <87k647s16g.fsf@newsguy.com> (raw)
In-Reply-To: 7573e9640609131318h48ad6563jbbad3b9475baeb72@mail.gmail.com

"Richard Fish" <bigfish@asmallpond.org> writes:

> On 9/13/06, reader@newsguy.com <reader@newsguy.com> wrote:
>> State Stopped
>
> I'm guessing that this is your problem.  What does "lpc status"
> report?  Does "cupsenable chub-print" help?

lpc status first reported:
chub-print:
        printer is on device 'smb' speed -1
        queuing is enabled
        printing is disabled
        no entries
        daemon present

As you see, `disabled' but why would that be?  My config doesn't
mention enable/disable and in the past I simply ran the cupsd service
or not to turn off/on.  Something new?

So I thought it might just start working after:
  cupsenable chub-print
But I guess it is not going to.

After running `cupsenable chub-print' and attempting to print a job
the log output in error_log contains thousands of lines of output from
just one attempt.  Among them grepping for the Error lines I see stuff
indicating a connection was not allowed.  That output in a moment.

First let me show that a connection is definately in working order:

 smbclient -L //chub -Ureader |grep print

 WARNING: The "printer admin" option is deprecated
 Password: 
 Domain=[CHUB] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
 Domain=[CHUB] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
        print$          Disk      Printer Drivers
        chub-print      Printer   HP Officejet 7400 series

 smbclient //chub/chub-print -U reader

 WARNING: The "printer admin" option is deprecated
 Password: 
 Domain=[CHUB] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
 smb: \>

The share is there and can be accessed with smbclient

After attempting to print, a few minutes pass and a new look with
lpc status:  Shows printing is now disabled again. 

Partial Error_log output follows:
grep ^E /var/log/cups/error_log

(Note: Many in-between lines are skipped and those printed are wrapped
for mail)

  E [13/Sep/2006:19:44:53 -0500] [Job 24] Tree connect failed
  (NT_STATUS_BAD_NETWORK_NAME)
  
  E [13/Sep/2006:19:44:53 -0500] [Job 24] No ticket cache found for
  userid=1000
  
  E [13/Sep/2006:19:44:53 -0500] [Job 24] Can not get the ticket cache
  for reader
  
  E [13/Sep/2006:19:44:53 -0500] [Job 24] Session setup failed:
  NT_STATUS_LOGON_FAILURE
  
  E [13/Sep/2006:19:44:53 -0500] [Job 24] Tree connect failed
  (NT_STATUS_BAD_NETWORK_NAME)
  
  E [13/Sep/2006:19:44:53 -0500] [Job 24] Unable to connect to CIFS
  host, will retry in 60 seconds...
  
  E [13/Sep/2006:19:45:53 -0500] [Job 24] Tree connect failed
  (NT_STATUS_BAD_NETWORK_NAME)
  
  E [13/Sep/2006:19:45:53 -0500] [Job 24] No ticket cache found for
  userid=1000
  
  E [13/Sep/2006:19:45:53 -0500] [Job 24] Can not get the ticket cache
  for reader
  
  E [13/Sep/2006:19:45:53 -0500] [Job 24] Session setup failed:
  NT_STATUS_LOGON_FAILURE
  
  E [13/Sep/2006:19:45:53 -0500] [Job 24] Tree connect failed
  (NT_STATUS_BAD_NETWORK_NAME)
  
  E [13/Sep/2006:19:45:53 -0500] [Job 24] Unable to connect to CIFS
  host, will retry in 60 seconds...
  
  E [13/Sep/2006:19:46:53 -0500] [Job 24] Tree connect failed
  (NT_STATUS_BAD_NETWORK_NAME)
  
  E [13/Sep/2006:19:46:53 -0500] [Job 24] No ticket cache found for
  userid=1000
  
  E [13/Sep/2006:19:46:53 -0500] [Job 24] Can not get the ticket cache
  for reader
  
  E [13/Sep/2006:19:46:53 -0500] [Job 24] Session setup failed:
  NT_STATUS_LOGON_FAILURE
  
  E [13/Sep/2006:19:46:53 -0500] [Job 24] Tree connect failed
  (NT_STATUS_BAD_NETWORK_NAME)
  
  E [13/Sep/2006:19:46:53 -0500] [Job 24] Unable to connect to CIFS
  host, will retry in 60 seconds...
  
  E [13/Sep/2006:19:47:53 -0500] [Job 24] Unable to connect to CIFS host
  after (tried 3 times)
  
  E [13/Sep/2006:19:47:53 -0500] PID 15252
  (/usr/libexec/cups/backend/smb) stopped with status 1!
  
  E [13/Sep/2006:19:47:54 -0500] PID 15251
  (/usr/libexec/cups/filter/foomatic-rip) stopped with status 9!

-- 
gentoo-user@gentoo.org mailing list



  reply	other threads:[~2006-09-14  1:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-13 16:59 [gentoo-user] [OT] print to printer on winxp via cups samba smb reader
2006-09-13 20:04 ` Mick
2006-09-14  0:37   ` [gentoo-user] " reader
2006-09-13 20:18 ` [gentoo-user] " Richard Fish
2006-09-14  1:10   ` reader [this message]
2006-09-14  1:55     ` [gentoo-user] " Richard Fish
     [not found]       ` <87y7snqifr.fsf@newsguy.com>
2006-09-14  4:27         ` Richard Fish
     [not found]           ` <87ac52k3o1.fsf@newsguy.com>
2006-09-14 13:56             ` reader
2006-09-15  7:40             ` Richard Fish
2006-09-15 13:52               ` reader
2006-09-15 16:55                 ` Richard Fish
2006-09-15 17:56                   ` reader
2006-09-15 23:57                     ` Richard Fish
2006-09-17  2:09                       ` reader
2006-09-17  4:27                         ` Richard Fish
2006-09-17 11:44                           ` reader
2006-09-17 15:21                             ` Richard Fish
2006-09-18 17:12                               ` reader

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87k647s16g.fsf@newsguy.com \
    --to=reader@newsguy.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox