Koozali.org: home of the SME Server

Cups Problem again

Finchwizard

Cups Problem again
« on: January 12, 2004, 04:42:45 AM »
I am running SME 6 Final.
I have the CUPS contrib installed.
There is a Printer added to Cups, to the local LPR port.
The password list are synced so that Windows Clients can see it.
The security for Samba is 'security = domain'
And the domain has been joined.

Why is it, when ppl browse the server, the server authenticated the shares of the PDC(Nt4) Yet, when they try and print, it checks /etc/passwd(I'm assuming, needs account on server to work)

Why is it so.?
I have tried everything I can think of, and it's really frustrating, has anyone got any idea what might be the problem?

Robert

Re: Cups Problem again
« Reply #1 on: January 14, 2004, 08:55:49 PM »
Anything useful in samba or cups logs after increasing the log levels?

Finchwizard

Re: Cups Problem again
« Reply #2 on: January 15, 2004, 12:19:52 AM »
I figured it out myself.

Security = server is bad, so don't use it.

I use Security = domain, but it still requires a local Unix account for some things.

So you use Winbind to get a list of users off the PDC. So it just looks like all the users appear in passwd on the computer.

I got it all sorted, lots of reading through the samba manual ;)

Robert

Re: Cups Problem again
« Reply #3 on: January 15, 2004, 11:11:02 AM »
Cool! Can you still access the CUPS web interface and send print jobs through IPP as a winbind user? If so, what form do the winbind account names take? Would you consider doing a writeup about your samba configuration and winbind authentication? It sounds very interesting.

Finchwizard

Re: Cups Problem again
« Reply #4 on: January 17, 2004, 10:26:14 PM »
Yes, I still use CUPS for everything, that was the main thing I was trying to use....

When a user appears in the CUPS queue, it just displays the domain and username, with whatever seperator you choose when configuring winbind.

eg.

DOMAIN+finchwizard

That is what it will appear as in the CUPS queue.

When I do up the documentation part so that if something go's wrong it can be reconfigured, I'll post a copy somewhere.