similar to: 4.2 on Raspberry Pi as AD DC - success !

Hello, thanks for replying. I installed and configured samba 4.1.7 and ntp 4.2.6 according to https://wiki.samba.org/index.php/Time_Synchronisation. I don't need further time updates. I need to change the date to DC samba4 the first days of every months by the last day of the previous month and my clients automatically update their time. I am aware of problems this can trigger but in this

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

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

Matthias Busch schrieb am 12.03.2015 22:08: > --- this is my /etc/krb5.conf > > [libdefaults] > default_realm = MY-DOMAIN.LOCAL > dns_lookup_realm = false > dns_lookup_kdc = true add these (partly done below) forwardable = true renewable = true ticket_lifetime = 24h renew_lifetime = 7d debug = false delete from

Matthias Busch schrieb am 12.03.2015 15:00: > -- hostname is adserver.my-domain.local Don't do that. .local is a poor choice. Use something different. https://wiki.samba.org/index.php/DNS#Avoid_.local_TLD > -- hosts is 127.0.0.1 localhost localhost.my-domain and 192.168.7.254 > adserver, adserver.my-domain.local looks good. The first thing would be to check the configuration.

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

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

On 12/03/15 15:43, Matthias Busch wrote: > 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

>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

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, 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

Hi, I am trying to create a tarball from a 4.0.3 git checkout using "make dist", but it throws errors (small sample below, detailed Copy&Paste on request), and apart from this, www.oasis-open.org seems stale on connects from xsltproc, as can be seen in the lsof sample, below as well. Briefly and cheekily asked, is that normal? Are we all omitting docs in packaging at the moment?

Hello, I've been having trouble with configuring NUT in my home system. First, I have NUT server installed in one raspberry with one UPS connected by USB to it, I followed Techno Tim's tutorial on the matter and it worked perfectly with the web GUI. Then, I have another raspberry pi with two UPS connected by USB that I want to connect to the first so I use just one GUI, but I

Folks I'm not sure this is the right mailing list for the Centos7 port to Raspberry Pi. On the chance that this is the right place... I just booted the Centos Linux 7 for Raspbery Pi 2, but have no idea what the built-in accounts or passwords are. I've tried user: pi password: raspberry and user: root password: password to no avail. Does anyone know? Is there a HOW-TO

On Jan 9, 2024, at 8:19?PM, Claudio Zanetta Penna via Nut-upsuser <nut-upsuser at alioth-lists.debian.net> wrote: > > My problem is that I want to connect a second Raspberry to the first one with NUT server on it, so the information obtained by the second can be sent to the server > and be presented in only one web GUI. > If you are referring to this tutorial:

I was able to make NUT and my Powercom SPIDER UPS (USB port) work under the Raspberry Pi Desktop (Debian). Everything works in VMware Workstation 15 Player. But my Raspberry Pi 3b + (with raspbian) doesn’t work with the same UPS, and with same NUT configuration. Raspberry sees the UPS, but the driver does not cling. Here is the response of Raspberry 3b + to some commands. pi at raspberrypi:~

In R 3.3.2 detectCores() in package parallel reports 2 rather than 1 on Raspberry Pi B+ running Raspbian. (This report is just 'for the record'. The model is superseded and I think no longer produced.) The problem seems to be caused by grep processor /proc/cpuinfo processor : 0 model name : ARMv6-compatible processor rev 7 (v6l) (On Raspberry Pi 2 and 3 there is no error because

Raspberry Pi 1 and Zero use the arm1176jzf-s chip which AFAIK doesn't support NEON intrinsics. This may be a bug with the configure script because it appears to be compiling with NEON enabled. Lifeng can you comment? Is there a way to override the CPU detection in this case? Samuel, as a workaround you can download and compile an older version of the library. I think 1.1.2 predated the NEON

Hi. I'm an italian user. I have a nome ups, AROS Spring RT1500. I would like connect it by usb on my server raspberry pi. Someone knows a simple tutorial to send me? I did some test without success..... Thanks Flavio