On 17/12/2019 14:20, L.P.H. van Belle via samba wrote:>>> smb.conf: >>> [global] >>> security = ADS >>> realm = SAMDOM.EXAMPLE.COM (redacted) >>> workgroup = SAMDOM (redacted) >>> >>> idmap config * : backend = tdb >>> idmap config * : range = 3000-7999 >> Whilst you have read 'Setting_up_Samba_as_a_Domain_Member', >> you seem to >> have missed the part about setting up the 'idmap config' >> lines for the >> 'SAMDOM' domain, or are you using sssd ? >> >> Rowland > Yes, i seen that also, but this is not a problem of configs but code in samba. > I have the same problem here. :-(Well yes, you may have, but at least Samba will know who your users are ;-) This needs fixing before the printers can be. Rowland
Hi Rowland,> Well yes, you may have, but at least Samba will know who your users are ;-) > > This needs fixing before the printers can be.Fixed it, I have now the following and reset all file permissions: idmap config * : backend = tdb idmap config * : range = 3000-7999 idmap config SAMDOM : backend = rid idmap config SAMDOM : range = 10000-999999 Unfortunately I have the lines missing on my fileserver as well, that is a task for another year ;) What exactly is the issue with only "idmap config *"? If I understand correctly I only have a server-local tdb but no functional problems? The printer problem shows the same behaviour as before. Cheers, Christian -- ifu Hamburg - Member of iPoint Group "Productivity meets Sustainability" ifu Institut f?r Umweltinformatik Hamburg GmbH Max-Brauer-Allee 50 - 22765 Hamburg - Germany fon: +49 40 480009-0 - fax: +49 40 480009-22 - email: info at ifu.com Managing Director: Jan Hedemann - Commercial Register: Hamburg, HRB 52629 www.ifu.com - www.umberto.de - www.e-sankey.com In der Zeit vom 23.12.2019 bis einschlie?lich 03.01.2020 bleibt das ifu Hamburg geschlossen. Ein Notdienst ist eingerichtet. Alle Mitarbeiter des ifu w?nschen Ihnen eine frohe Weihnachtszeit! In the period from 23rd of December 2019 until the 3rd of January 2020 ifu Hamburg will remain closed. An emergency service has been set up. All ifu employees wish you a merry christmas time!
On 18/12/2019 13:21, Christian Haase via samba wrote:> Hi Rowland, > >> Well yes, you may have, but at least Samba will know who your users are ;-) >> >> This needs fixing before the printers can be. > Fixed it, I have now the following and reset all file permissions: > > idmap config * : backend = tdb > idmap config * : range = 3000-7999 > idmap config SAMDOM : backend = rid > idmap config SAMDOM : range = 10000-999999 > > Unfortunately I have the lines missing on my fileserver as well, that is > a task for another year ;) > What exactly is the issue with only "idmap config *"? If I understand > correctly I only have a server-local tdb but no functional problems?Your smb.conf shows that your computer is running as a Unix domain member (security = ADS) and the default domain (*) is meant for the Well Known SIDS and anything outside the main domain. The local tdb files are really just caches. You should use one of the winbind backends: 'ad' if you want the same IDs everywhere 'rid' if you only have one domain and do not want to add anything to AD 'autorid' if you have multiple trusted domains> > The printer problem shows the same behaviour as before.Have you tried Louis's suggestion of a different driver ? Rowland
> -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Rowland penny via samba > Verzonden: woensdag 18 december 2019 14:46 > Aan: samba at lists.samba.org > Onderwerp: Re: [Samba] Hosted printer drivers can not be used >....> > > > > The printer problem shows the same behaviour as before. > > Have you tried Louis's suggestion of a different driver ?I explicit took the driver he needed, and that did not work for him, Where it did work fine for me. So, still something in his setup isnt correct. At least, thats what i expect. I want to see more of the setup, if it works here, it should also work for him. There might only be one difference, i notice i used "dutch" drivers, where he might use german. And if thats the case, then a higher log level is a must. And then i suspect a UTF8 convertion problem. But logs mighth show that. This is a bit based on what i've seen lately, in general. Greetz, Louis