similar to: NT_STATUS_INTERNAL_ERROR from RPC server on samba 4.5.8 AD DC

On 30/12/15 03:36, IT Admin wrote: > Hello to the Samba Mailing List, > > This is my first post, so please, should I commit any faux pas, nudge me in > the right direction and I will adjust accordingly. > > I'm experiencing a complete failure of the PDC in a Samba 4 AD Domain I've > deployed for a client. Samba failed a few days ago and I've been unable to >

Hai, Can be incorrect rights, of corrupted db. Can you give the output of ls -al /var/lib/samba/ ls -al /var/lib/samba/private ls -al /var/lib/samba/private/dns Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens IT Admin > Verzonden: woensdag 30 december 2015 4:37 > Aan: samba at lists.samba.org > Onderwerp:

Hello to the Samba Mailing List, This is my first post, so please, should I commit any faux pas, nudge me in the right direction and I will adjust accordingly. I'm experiencing a complete failure of the PDC in a Samba 4 AD Domain I've deployed for a client. Samba failed a few days ago and I've been unable to resolve the issue on my own. Google searches are leading me in circles,

Hello. I've got a network of FreeBSD servers which traditionally hosted a classic domain. I upgraded some months ago, removing the old PDC and BDC and migrating to an AD DC controller in a jail. This is working fine with Samba 4.4.13. Now I'm trying to add a second DC, so I created a new jail on another physical server and went on with the setup, following: >

Hi, Thank your for your answers. @Rowland: Yes, Winbind is installed but it seems it is not started (or cannot start) @Andrew: Please find extract in log level 4 during a service restart and a connection test with smbclient from another machine. I hope this could help, this is not clear to me : ==> /var/log/samba/log.samba <== [2018/05/29 10:54:00.173894, 0]

So you use images!? Are you shure you used different host names for each client. We found using install images will do this confusion some times because windows announced with the image name not with the new one. EDV Daniel M?ller Leitung EDV Tropenklinik Paul-Lechler-Krankenhaus Paul-Lechler-Str. 24 72076 T?bingen Tel.: 07071/206-463, Fax: 07071/206-499 eMail: mueller at tropenklinik.de

Timo Altun skrev den 2015-05-19 08:12: > Hi Davor, > > thanks for the answer. They were actually part of a NT4 domain called > mayweg.net <http://mayweg.net> (the new realm name). But I did join > workgroup "WORKGROUP" before I tried to join the new domain. > If it's possible that they're sending the information the wrong way > because they were part

On 2015-05-20 09:21, Timo Altun wrote: > Hi Davor, > > most of the domain accounts were part of an old NT4 domain. I did a > classicupgrade. > > Your theory with the NTUSER.DAT-files seemed so promising, > unfortunately that was not it. I created new accounts on an XP machine > and a Win7 machine and tried to join with them, but still receive the > same error. One of

Hi Davor, I finally found it! After going through https://wiki.samba.org/index.php/Joining_a_Windows_Client_to_a_Domain , I checked the time settings on said clients and they differed from the AD DC too much. This also explains why some clients could join after a while...they synchronised with a NTP server after a day or so and then I was able to join. After that, joining the rest of clients was

Hello, I have installed Samba4 on Debian8. RSAT from windows 7 works fine(all) and before a few days I have tried create a new domain user via RSAT on Windows 8, but something block to finish this step with popUp 'An error occured. Contact your system administrator' on samba server from log: [2015/06/15 12:04:23.431150, 2] ../source3/smbd/server.c:419(remove_child_pid) Could not

Hi, I encountered a strange problem...some of my windows machines cannot be joined to an Samba 4.17 AD domain (8 of ~90 clients). These are 7 Win7 clients and one WinXP client. The message I receive in windows is: "Logon failure: unknown user name or bad password". All other Win7 and XP machines could be joined...the same OS image has been used to install both the machines that could be

Hi Davor, most of the domain accounts were part of an old NT4 domain. I did a classicupgrade. Your theory with the NTUSER.DAT-files seemed so promising, unfortunately that was not it. I created new accounts on an XP machine and a Win7 machine and tried to join with them, but still receive the same error. One of the machines I'm not able to join with, wasn't even part of the domain

Hi Davor, thanks for the answer. They were actually part of a NT4 domain called mayweg.net (the new realm name). But I did join workgroup "WORKGROUP" before I tried to join the new domain. If it's possible that they're sending the information the wrong way because they were part of a workgroup named after the new realm, is there any way to clear the old data (apart from a new

Greetings, Rowland Penny! Got some logs. But... they do not make much sense. It seems to fail to chdir to /tmp. But I can do it with sudo just fine under the same credentials. What's going on? [2015/03/30 01:05:38.027147, 3, effective(0, 0), real(0, 0)] ../source3/lib/access.c:338(allow_access) Allowed connection from 127.0.0.1 (127.0.0.1) [2015/03/30 01:05:38.027425, 3, effective(0, 0),

Hello all ! Since a few weeks now i have lots of problem transfering files from windows clients to my samba nas. It just hangs and acts like it losts connection to the samba nas allthough when i just browse or read there is no trouble.Also if i launch a transfer from scp on a linux or with a soft like total commander or filezilla, there are also no problem. It's very strange and annoying. Does

Hi list, I'm trying to set up a simple fileserver (Samba 4.1.6 on Ubuntu 14.04) as domain member, which delegates user authentication to AD (2k8R2) via Kerberos/NSS ? SSSD without using Winbind. I have SSSD up and running and things like getent passwd some-domain-user getent group some-domain-group chown some-domain-user:some-domain-group /tmp/foobar work just fine and show the

Hello, I am attempting to debug an issue with my Samba configuration. It has been working fine, but we recently updated Samba from 4.6.x to 4.8.3 and are now seeing some issues authenticating. Most of our servers are still working fine after the upgrade, but one server is giving us issues. A little more environment info: The server is running Centos 7.1. Windows clients can connect OK. We are

On 05.09.19 16:14, Rowland penny via samba wrote: > try adding 'null passwords = yes' to your smb.conf. I have try. but can't connect (NT_STATUS_CONNECTION_RESET). Log append. Config: [global] workgroup = workgroup dns proxy = no log file = /var/log/samba/log.%m max log size = 5000 log level = 3 passdb:5 auth:5 syslog = 0 panic action =

Hi Ivo, I think I've a very similar issue on 4.1.16 and it seem that hosts allow = 10.15. 127.0.0.1 interfaces = localhost, re0 is to blame. please try to comment them and see if that work. On Mon, Aug 3, 2015 at 4:54 AM, Ivo Karabojkov <karabojkov at kit.bg> wrote: > Hello, > > I have a strange problem with Samba AD member: > It is accessible via \\server or

Good morning Rowland and samba list ... Rowland Penny wrote on 03.07.2015 18:36:32: > From: Rowland Penny <rowlandpenny241155 at gmail.com> > To: samba at lists.samba.org, > Date: 03.07.2015 18:40 > Subject: Re: [Samba] Migration Samba3 -> Samba4: Accessing domain > member server is not working > Sent by: samba-bounces at lists.samba.org > > On 03/07/15