[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [K12OSN] Very frustrating!



Hello,

Just before you sent me that email I did exactly that. Put the file
into the chroot, and ran it from the client shell and the printer
seemed to accept the firmware.  In windows it always does what can
best be described as a 'hiccup' when it gets the firmware and it did
exactly that!  So this is a good thing.

I also agree with you that it's not detecting it from the client.  I
think because it was on the server in the past it's detecting it
there.  I will try to add it again.

Joseph

On Fri, Jan 30, 2009 at 10:12 PM, Rob Owens <rowens ptd net> wrote:
> On Fri, Jan 30, 2009 at 09:48:58PM -0500, Joseph Bishay wrote:
>> Bad form to reply to my own email but one more thing!
>>
>> I noticed something unusual but I think is good.  I deleted all the
>> printers that I had created on the server.  Once I confirmed that they
>> are all gone, I restarted CUPS.  When I went in and asked it to list
>> all the printers, cups automatically regenerated the entry for the usb
>> printer, with the Device URI: socket://192.168.2.250:9100  -- that is
>> the correct one.  Could it be detecting it from the client's USB
>> connection?  I know if I plug the printer into the server it does the
>> same thing.
>>
> I don't think it's detecting it on the thin client.  Is/was that printer configured on another Linux box?  It may be detecting it from there, even though the printer is no longer attached to that box.
>
> -Rob
>
> _______________________________________________
> K12OSN mailing list
> K12OSN redhat com
> https://www.redhat.com/mailman/listinfo/k12osn
> For more info see <http://www.k12os.org>
>


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]