[SOLVED] SAMBA & CUPS -:- Can't Print To Windows Printer

KristyX · Last edited by KristyX on Tue May 18, 2004 7:04 am; edited 2 times in total

Hi!

I have a small LAN (with the Workgroup name: MAIN-ONE) that has a Win98 computer called "Melody" which shares the printer "Lexmark" (it's a Lexmark E210).

I've got Samba working so I can see her, browse her files and ping her as well.

But as for cups, I've set up the Printer (the conf is below) but when I print, nothing happens. I've attached the error log as well.. I can't see anything wrong but maybe a more experienced user can?

Any help would be appreciated!

Thanks,
Kristy

---

/etc/cups/printer.conf

OldCat · n00b Joined: 10 Sep 2003 Posts: 30 Location: New Zealand

I have basically the same set up and it works great. The difference I have in the config file is in the DeviceURI. I do not have the Domain/Workgroup Name listed, since samba already knows about it. So, just use the machine name and share name.

KristyX · Posted: Tue May 18, 2004 4:48 am Post subject:

Thanks for replying!

I made the change to printer.conf but it still isn't printing

Just to double-check, I don't have to add anything about the printer
the Samba's Config file (smb.conf) right? (I know, it sounds unrelated
but I was just wondering..)

Also, are there any special groups that user has to be part of to be
able to print?

Thanks,
Kristy
_________________
Knowledge is a process of piling up facts; wisdom lies in their simplification. [Martin Fischer]

KristyX · Posted: Tue May 18, 2004 5:15 am Post subject:

One more thing.. I'm not sure what's different but now, the jobs under CUPS's completed jobs shows that the new jobs are being aborted.

The files I tried printing earlier today however show that they were "completed" (it didn't happen btw.. the lexmark didn't even "warm up" heh)

KristyX · Posted: Tue May 18, 2004 6:40 am Post subject:

YAY!!!! I found the problem!!!

I was going through the CUPS documentation and under the Troubleshooting section there was a "telling" example of what was wrong with the sample guy's printer.. so the exercise was to look at the logs and see if you can spot it.

Since it was relatively easy, I saw the error. And that's when I thought that I should try going through my own error log line by line (I had done it earlier.. but had no idea what I was looking for)

And that's when, by God's Grace, I found the culprit: