similar to: Cannot print from Win7 AD client

I run a Samba4 AD and joined a Synology NAS running Samba 3.6.9. I can access the shares using smbclient or mount -t cifs from all Linux machines (usually running Samba 3.6.6 clients). I can mount the shares from WinXP home and Win7 home. However, with a Win7 Ultimate machine joined to the AD most of the time it doesn't work. I can logon to the machine with my AD credentials, but I am

I created a demo share on my AD DC. After obtaining a copy of Win7 Ultimate I could now verify that the share has all rights granted to anyone (don't know how Windoze call "Jeder" in English). I can read and write the Share using AD\Administrator. AD\StandardUser can mount the share and read, what the Administrator put there. But he cannot create or modify files.

I set-up a basic AD DC using samba 4.1.9 successfully. I joined my NAS to the domain, i.e. I saw no errors and see the users and groups of my AD listed in the GUI of the NAS. When I try to connect to a share of the NAS the following happens: mgr at ws1:~$ smbclient -U 'AD\mgr' //nas/Test Enter AD\mgr's password: Domain=[AD] OS=[Unix] Server=[Samba 3.6.9] tree connect failed:

Hi, Since recently printer deployment is broken on Windows 7 (and above?) due to KB3170455. This is probably the same problem https://lists.samba.org/archive/samba/2016-August/202078.html on Win 10. After a lot of reading and investigating it appears that we now (after KB3170455) need: - A Point & Print Restriction GPO enabled with FQDN of all Print Servers and "Do not show warning

Hi Louis, no all driver work (brother, kyocera, hp) I installed the driver but I get the same message with trust. It seems not work without remove the security patches. When I remove security patches it seems not important which driver are installed. In theory it should work with the driver but it seems not. Greetz, Sven -----Ursprüngliche Nachricht----- Von: samba [mailto:samba-bounces at

Hi, I'm going to migrate my old CUPS server to a new setup. It shall provide the printing backend for Samba4 and should integrate as seamless as possible. Both Windows and Linux users should not require additional passwords, but should be authenticated by their Kerberos tickets. Is there anything particular to consider? E.g. has the CUPS server to be joined to the AD and should it run a

A couple of days ago my PDC died due to a hardware failure. Since I had a secondary DC I hoped it would take over silently. Well, it did, but not exactly silently. I finally claimed the PDC role for it, which apparently worked. But I had to edit the DNS information to remove the PDC using the management console. After that the system seemed to work. At least I could log in from our Win7

Greg, > Unfortunately, these attributes do not exist as standard, so you would > either have to add a user with ADUC or manually add them yourselves with > ldbedit. As standard on windows, they both start at '10000', though you > can set them to whatever you require, just make sure that they do not > interfere with any local Unix users. If you like to manage Unix users

Am 19.01.2015 um 12:30 schrieb Ashish Yadav: > Hi, > > On Mon, Jan 19, 2015 at 3:45 PM, Lars Hanke <debian at lhanke.de > <mailto:debian at lhanke.de>> wrote: > > I run a Samba4 AD and joined a Synology NAS running Samba 3.6.9. I > can access the shares using smbclient or mount -t cifs from all > Linux machines (usually running Samba 3.6.6 clients).

Hi Louis, Hi Achim, on windows 10 i removed the 3176493 which is on windows 7 / 8 3177725. It has no effect on restriction. Its always restricted. Sven -----Ursprüngliche Nachricht----- Von: samba [mailto:samba-bounces at lists.samba.org] Im Auftrag von Achim Gottinger via samba Gesendet: Montag, 15. August 2016 18:39 An: samba at lists.samba.org Betreff: Re: [Samba] Windows 10 point and print

Hi Marc, >> The cause is that the password change didn' reach both AD DCs, but only >> one. The other one still had the old value as could be seen by >> samba-tool ldapcmp. Restarting the DCs and waiting for a couple of >> seconds brings them back to sync and Windows logons work as they used to. >> Any idea, what I should do next time to obtain valuable output

It is actually rather easy to set the attributes via powershell, and that is probably the best way to add them in a Server 2012 R2 environment. I wrote a powershell script to do this automatically for users and groups in an entire domain that should be pretty generic to be reused. It also mirrors the logic used in automatic winbind UID/GID generation to be able to coexist in an environment where

This topic has been on the list two years ago, already, but apparently to no conclusion. I'm trying to join a Debian Wheezy machine (Samba 3.6.6) to my freshly made backports AD (Samba 4.1.7). This is what I see: root at samba4:/# net ads join -U Administrator at AD.MICROSULT.DE Enter Administrator at AD.MICROSULT.DE's password: Using short domain name -- AD Joined 'SAMBA4' to

Ok, it's here: http://pastebin.com/JEnr5wUq The id_offset is that value because i initially didn't use rfc2307 attributes, but instead On 29 January 2015 at 23:27, Tim <lists at kiuni.de> wrote: > @Hans-Kristian: > I'd like to see it. How did you automate this? > > @Andrew: > In another thread I suggested to set the rfc2307 info automatically when a > domain

Well, seems like I hit every mudhole that could be on the way ... root at samba4:/# getent passwd | grep mgr mgr:*:10000:10000:Lars LH. Hanke:/home/AD/mgr:/bin/bash root at samba4:/# ldapsearch -LLL -D "CN=Administrator,CN=Users,DC=ad,DC=microsult,DC=de" -x -W '(uid=mgr)' uid uidNumber gidNumber sAMAccountName name gecos Enter LDAP Password: dn: CN=Lars LH.

Thanks Rowland, for the thoughts. > If you are running Samba4 as an AD DC, you should never start the nmbd > deamon, you should also never start smbd manually. Yes, I could optimize to use /etc/init.d/samba-ad-dc immediately,but in fact this is what /etc/init.d/samba does. The messages with "AD DC daemon" are generated by that script, and it is the failing one. > What

Hi folks. I've got a system where my WinXP (they still work well) workstations have a virtual printer installed on them. This virtual printer uses Apple Colour Laserwriter Postscript drivers to generate PS files which are then printed to a linux server where Samba passes the file to one of my scripts which then parses the file, extracts data, coverts the PS to PDF and then inserts the

hello list, i have a running vm with win7. When i fire up an 'virsh shutdown win7' nothing happens. When i fire up a second the same command, then the win7 machine is shutting down. Why do i need to fire up this command twice? Any ideas? best regards marko --

After upgrading Win7 and W2K8 R2 clients to service pack 1 it is no longer possible to log in to domain(before the upgrade the clients can log in into domain). Clean installation of Win7/W2K8 R2 with integrated sp1 has the same effect. Our domain PDC is running on samba 3.3.7. I'm curious if anyone else has seen this already. Thank you Mikhail Zuskov

I'm curious how others manage their windows 7 machines on a samba 3.x.x domain .. especial the part of policies and scripts. i got the win7 running in the samba domain, but i'm stuck in the policies part.. and i don't want to use nitrobit for this. how do other users do this.. ?! thx, Collen