search for: catwiesel

...is now marked as deprecated, so f20's setting is > better now. > > --- > TAKAHASHI Motonobu <monyo at monyo.com> / @damemonyo > facebook.com/takahashi.motonobu > > > > > ---------- Mensaje reenviado ---------- > From: Matthias Busch <catwiesel at gmx.net> > To: samba at lists.samba.org > Cc: > Date: Sat, 14 Mar 2015 04:54:31 +0100 > Subject: [Samba] 4.2 on Raspberry Pi as AD DC - success ! > after the last few days playing around with 4.1.17 I decided to start new > and try 4.2 > > --- Hardware, OS: > Pi B+,...

Hi! Did you managed to correctly deploy GPOs? I'm facing some issues with some types of gpo not being applied. Thanks Filipe Moreira Enviado de um dispositivo m?vel No dia 14/03/2015, ?s 10:50, Matthias Busch <catwiesel at gmx.net> escreveu: > Hey List, > > first, let me give a huge thanks to everyone who replied and helped. > I learned a lot and I could not have done it in any reasonable time frame without your suggestions and answers! > > I started new from scratch to make sure no old con...

so far, I've only tried to deploy msi via gpo. what gpo type is troubling you? i could try and report back... when I had initial gpo trouble it was because dns wasnt working quite right (when adding a new pc to the domain, it was not added to dns and hence could not gpoupdate) does gpoupdate /force give any errors?

Hey List, first, let me give a huge thanks to everyone who replied and helped. I learned a lot and I could not have done it in any reasonable time frame without your suggestions and answers! I started new from scratch to make sure no old configuration / data was screwing with further attempts. It pretty much worked without problem. A few things that were done different ... - samba 4.2, not

Hi, after successfully building* and getting the AD DC working with samba 4.2** on the raspberry pi b I got the pi 2 and... ran into walls... *see https://lists.samba.org/archive/samba/2015-March/190073.html ** see https://lists.samba.org/archive/samba/2015-March/190057.html Since the setup in the ** link worked so well, I followed the same procedures during the 4.2 setup with the pi 2

after the last few days playing around with 4.1.17 I decided to start new and try 4.2 --- Hardware, OS: Pi B+, Raspbian 2015-02-16 --- Getting packages: - install packages: build-essential libacl1-dev libattr1-dev libblkid-dev libgnutls-dev libreadline-dev python-dev libpam0g-dev python-dnspython gdb pkg-config libpopt-dev libldap2-dev dnsutils libbsd-dev attr krb5-user docbook-xsl

further testing, log reading and googling has revealed further possible problem sources... with ipv6? my syslog shows the following errors: --- Mar 12 18:08:10 ADServer samba[2161]: [2015/03/12 18:08:10.134418, 0] ../source4/smbd/server.c:488(binary_smbd_main) Mar 12 18:08:10 ADServer samba[2161]: samba: using 'standard' process model Mar 12 18:08:10 ADServer samba[2238]: [2015/03/12

RESULT! ~# kinit administrator at MY-DOMAIN.LOCAL Password for administrator at MY-DOMAIN.LOCAL: Warning: Your password will expire in 41 days on Thu Apr 23 16:57:35 2015 !!!! --- I should have listened to you guys much sooner. I suspect that the .local did indeed have something to do with it since mDNS was running and may have screwed with dns resolution for *.local. tlds? additionally, I

Hello List, I have a raspberry pi with raspbian. I am trying to get samba 4.1.17 to work as AD DC and have problems which seem to be dns related... What I did to get here: - I removed the preinstalled samba - installed prerequisites (build-essential libacl1-dev libattr1-dev libblkid-dev libgnutls-dev libreadline-dev python-dev libpam0g-dev python-dnspython gdb pkg-config libpopt-dev

okay, I started to look into winbind and the /etc/nsswitch.conf (and smb.conf)... and it wreaked havoc... I was using the guide at https://wiki.samba.org/index.php/Setup_a_Samba_AD_Member_Server - right guide? the guide is talking about "samba member server that is part of an active directory" Is that correct? I mean, THE ad domain controller is member of the ad, but it sounds like

Hey Peter, many thanks for your reply. --- regarding .local domains I know this is regarded by some as bad form, is actively being discouraged by the samba wiki and can cause problems with bonjour/zerobla configuration. I can say for certain that no apple devices will ever come anywhere near that network and the other drawbacks of .local like getting signed certs... should never be an issue

>Hi, please don't use .local, you say that no apple devices will come >near, but what about an iphone ? and what about avahi ? >When you ran configure, you might as well just run it like this: ./configure >All the rest are defaults and you do not really need debug. >You only need to alter /etc/nsswitch.conf (yes that's the one) if you >want/need your users to log into