[cups.general] cupsaddsmb? - other problem
h.blischke at srz.de
Thu Jan 20 03:56:46 PST 2005
> > we have also some problems with the cupsaddsmb.
> > As long as the samba is running with the setting
> > security =domain
> > the command cupsaddsmb will fail.
> > We have to switch back to
> > security = server
> Have a look at these STRs and report back if they could be related to your problem:
> That seems to bite a lot of people. (Maybe it is fixed by now). Basically, in a Windows domain, the domain name becomes an essential and valid part of the username. Only with "DOMAIN\USERNAME" you can authenticate when you tell winbind to do authentication for Samba users against a Windows Domain Controller. For the rest of Unix this seems to be a perfectly valid Unix username too in that context. Just CUPS does not yet like it.... (or so was the version I last checked.)
> > p.s. I tried really *everything* from the SMB-HowTo (really good docu!!)
> I agree. Kudos to the Samba documentation writers!
> I regret I cant do any Samba related work any more in my new job. :-(
I don't think *this* issue is related to the mentioned STRs, as no
authentification against CUPS takes
place with cupsaddsmb at this point. It is simply an issue with the
rpcclient utility (the command
fails with security = user as well), and the only systems involed at
this point are the samba application
and the win box.
SRZ Berlin | Firmengruppe besscom
tel: +49 30 75301-360
More information about the cups