similar to: KB3163912 breaks Point and Print Restrictions GPO settings for non-packaged-aware printer drivers

Hello Christian, Am 24.08.2017 um 11:36 schrieb Christian Naumer via samba: > Has anyone found a workaround for Samba print servers? > > https://social.technet.microsoft.com/Forums/en-US/030ee94a-047d-460a-bc39-52351a199364/kb31639 > 12-breaks-point-and-print-restrictions-gpo-settings > > If I set the GPOs as stated on the WIKI

On 24/08/17 12:57, Marc Muehlfeld via samba wrote: > Hello Christian, > > Am 24.08.2017 um 11:36 schrieb Christian Naumer via samba: >> Has anyone found a workaround for Samba print servers? >> >> https://social.technet.microsoft.com/Forums/en-US/030ee94a-047d-460a-bc39-52351a199364/kb31639 >> 12-breaks-point-and-print-restrictions-gpo-settings >> >>

which printer brand/model and which driver? > Op 14 aug. 2016 om 13:25 heeft Vogel, Sven via samba <samba at lists.samba.org> het volgende geschreven: > > Hi, > > it seems there is a problem/bug in windows 10 that point and print restriction dont work and gpo are ignored. I don't know. When I use windows 7 there o problems. technet article they speak about packaged

Hai,   I noticed the following “Optional” update for win7. https://support.microsoft.com/en-us/kb/3192403 October 2016 Preview of Monthly Quality Rollup for Windows 7 SP1 and Windows Server 2008 R2 SP1 Referres to :  https://support.microsoft.com/en-us/help/22801/windows-7-and-windows-server-2008-r2-update-history   We which is talked about a lot.. Addressed issue that prevents

Hello, when deploying drivers via Point-and-Print recent Windows (tested with Windows 10 1607) asks the user to confirm the driver installation. An appropriate Policy [1] is set up so that no user interaction should be required for the driver installation. There are similar reports [2,3] that identify updates KB3163912, KB3172985 and KB3170455 causing these issues. However, Windows 10 1607

Ok you probely have hit : KB3163912 and KB3172985 problems. ( win 10 ) For win 7 you can have trouble due (KB3170455) Some good info here. http://blog.vectranetworks.com/blog/microsoft-windows-printer-wateringhole-attack Here are some tips to fix this also. - Remove the KB ( start with KB3172985) , but thats not my advice. - Setup the point and print restrictions as followed. Computer

Hello Christian, Can you post me the message you got from the samba-check-db-repl.sh, Then i'll add something for it. And can you tell with version nummer of the script your using. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Christian Naumer via samba > Verzonden: woensdag 10 mei 2017 9:30 > Aan:

Am 16.04.20 um 14:18 schrieb Rowland penny via samba: > On 16/04/2020 12:45, Christian Naumer via samba wrote: >> Hello alAl, >> after update of our test server to 4.12.1 from 4.11 it crashes. If the >> vfs module is removed from the config everthing works as before. > > The only change was to upgrade to 4.12.1 ? > > If there were no other changes, then Samba

Hello Cristian, Well, nothing to say about your steps, these looks good. And lmdb could be disable in the sernet packages, cant say, i dont know. And only one DC has these problems or all? If only one DC crashed. Which DC crashes. Last added? Oldest? Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Christian

In addition to Rowland comment. if you still able to test it. Remove 1 setting at a time, restart and test it. Start with these, in this order. logging = syslog only prefork children = 8 I think if the logging line is removed your problem is solved. man smb.conf /logging should explain more. Because I cant/find the setting : logging = syslog only Greetz, Louis

Am 20.05.19 um 11:59 schrieb Rowland penny via samba: >>          logging =syslog only > > Why do you have a parameter with another parameter as its value ? > > both 'logging' and 'syslog only' are both parameters, did you mean > 'logging = syslog' ? Yes I meant this "logging = syslog" > >>          server role = active

Hello you all, this is a bit OT but I think I'll find some people here that can help. We have 4 DCs all on the same site. This is working fine. 3 Are VMs one is a physical server. They are the only DNS servers in that network. On a member server running our icinga2 installation I have this in the resolv.conf: options rotate timeout:2 retries:1 search example.com nameserver x.x.x.x (ip dc1)

Hello Christian, Ive had a quick look at you output, that looks pretty normal. I'll have a good look Friday, tomorrow day off. So my suggestion is post the output to the list but -d10 is not needed. The regular output should be sufficiant. Im wondering why there is no dc3 in kcc also but why i see over 15 RPC sessions. Maybe normal maybe not, this i dont know. Greetz, Louis >

So strange.. I copied your commando's only change the arpa and servername / domainnames All worked. So far nobody told how there ad-dc and DNS is setup.. Which i why i added : > > Debian 10, my own packages. > > Samba 4.11.6 + BIND9_DLZ is used . Now are you using samba DNS or BIND_DLZ dns ? That might help here. Greetz, Louis > -----Oorspronkelijk

Hello all, we have upgraded our 4 DCs from samba 4.4.12 to 4.6.3. The setup is working fine and no errors were displayed during the upgrade. After a day I noticed that the DC (dc1) holding the fsmo roles is missing one kcc connection (to dc3) in the output of samba-tool drs showrpl. Otherwise there are no errors displayed. On windows in the ADSites tool I see that the connection is missing and I

Dear all, somehow, new PTR records are not visible. This is on 4.11.6 DC with BIND9 ... Here is what happens: root at dc1:~# cat /etc/samba/smb.conf # Global parameters [global] bind interfaces only = Yes interfaces = 127.0.0.1 XXX.YYY.103.1 netbios name = DC1 realm = SAMDOM.REST_OF_FQDN server role = active directory domain controller server

Am 20.05.19 um 15:34 schrieb Rowland penny via samba: > On 20/05/2019 14:02, Christian Naumer via samba wrote: >> Am 20.05.19 um 14:31 schrieb Rowland penny via samba: >>> Samba 4.10.0 was the first version that works with python3 and whilst >>> this may not have a bearing on your problem, is python3 installed. >> No python3 is installed. I would also saume that

Am 18.03.20 um 22:26 schrieb Andrew Bartlett: >> Also "samba-tool domain tombstones expunge --tombstone-lifetime=0" >> does >> not delete the records with "dNSTombstoned: TRUE". Is this a >> different >> tombstone? > > That would be a different tombstone, yes. Can someone help me out with the ldap/ldb syntax to delte those by cron? >

Am 06.05.19 um 16:06 schrieb Rowland Penny via samba: > Yes, user 'vincent' has uidNumber 10010, gidNumber 13010 and > primaryGroupID 513. > > 513 corresponds to the group "Domain Users", which have gidNumber > 13010 > > Vincent Might this be the problem? He has primaryGroupID set to 513 (hello calssicupgrade?) but "Domain Users" hast a gid of

Hello all, I have a weird problem. We have several Windows 10 machines on our Network. All but one run older releases than 1709. We are using roaming profiles on those machines. The share is setup up as to allow different profiles depending on the machine used (see below). The %a is used as a legacy from times where WinXP and Win7 were used in parallel. The path then looks like this: