similar to: DNS update - NT_STATUS_IO_TIMEOUT every 10 minutes

Hai, ? Just a tip for the people reading the list. ? if you see Failed DNS update - NT_STATUS_IO_TIMEOUT? or messages : ?RPC unavailable if you connect from windows client to the samba AD DC server ? Read this. ? I have a "test' AD DC on a XEN server running and this DC does nothing. 1 pc ( win7) is joined, some dns recored are set, nothing special.. ? today i checked the logs, and

Hai, ? From out of nothing, im getting the messages below in my log. [2014/06/30 09:39:19.216634,? 0] ../source4/dsdb/dns/dns_update.c:294(dnsupdate_nameupdate_done) ? ../source4/dsdb/dns/dns_update.c:294: Failed DNS update - NT_STATUS_IO_TIMEOUT ? No dhcp servers involved in this, just 3 with static ip's. nothing changed, besides some GPO edititing. ? Just upgraded from (sernet) 4.1.8

Hai, ? Im seeing something very strange.? ( Debian wheezy, sernet-samba 4.1.14 ) ? after update-ing my debian servers and restarting them, im see-ing the following on my ADDC2. ? [2015/01/19 11:09:10.422641,? 0] ../source4/dsdb/dns/dns_update.c:294(dnsupdate_nameupdate_done) ? ../source4/dsdb/dns/dns_update.c:294: Failed DNS update - NT_STATUS_IO_TIMEOUT ? I?checked the SOA's of the DNS and

On 19/01/15 10:30, L.P.H. van Belle wrote: > Hai, > > Im seeing something very strange. ( Debian wheezy, sernet-samba 4.1.14 ) > > after update-ing my debian servers and restarting them, im see-ing the following on my ADDC2. > > [2015/01/19 11:09:10.422641, 0] ../source4/dsdb/dns/dns_update.c:294(dnsupdate_nameupdate_done) >

Hello List, in the following environment SUSE Linux Enterprise 11SP3 with bind 9.9.4P2 and the Sernet samba packages in version 4.1.7. samba works as AD PDC. Every few days our bind dns server denies updates. It looks like a problem with kerberos and the bind_dlz driver: Jul 2 08:04:21 s4ad named[22579]: samba_dlz: starting transaction on zone baettenhausen.local Jul 2 08:04:21 s4ad

good day Ali Bendriss, I followed exactly this tutorial to update the samba. Thank you, everyone I'll be honest as I have full knowledge about the Samba 4 will redo the structure thus have more work more on the other hand I'm sure I will not make a mistake that can generate me more trouble. Regards, Gabriel Franca > Em 14/08/2015, à(s) 09:39, Ali Bendriss <ali.bendriss at

Good morning friends, I have the following structure: Centos 6.6 1) AD samba using .tgz package 2) using the proxy Sernet packages which use command: samba-tool domain join XXX.corp DC -U Administrator --realm = XXX.corp and set the squid via NTLM. Issues: 1) after the update I get the following messages in / var / log / messages: Aug 13 04:08:56 kernel samba: Out of memory: Kill process

I can confirm this behavior, forwards work ok until the limit is reached. Setup is a single DC with less that 6 machines joined to the domain and maybe another 6 machines pointing at this DNS. Does anyone want the gdb info that was stated from a prior thread back in issue 10? interim fix: I just added ulimit -n 8192 to the start script and a cron to restart samba twice a day for now. samba

Good morning Rowland. Today there are 2 servers with Samba 4.1.19 1) Samba 4.1.19 compiled used for the control domain (AD) 2) using Samba 4.1.19 Sernet package I used the command "samba-tool domain join" to use the Squid authenticating via NTLM. Before I was as follows: 1) Samba 4.0.4 compiled AD 2) using Samba 4.1.19 Sernet package I used the command "samba-tool domain

On 13/08/15 12:46, Gabriel Franca wrote: > Good morning friends, > > I have the following structure: > > Centos 6.6 > > 1) AD samba using .tgz package > > 2) using the proxy Sernet packages which use command: samba-tool domain join XXX.corp DC -U Administrator --realm = XXX.corp and set the squid via NTLM. > > Issues: > > 1) after the update I get the

On 08/13/2015 01:46 PM, Gabriel Franca wrote: > Good morning friends, > > I have the following structure: > > Centos 6.6 > > 1) AD samba using .tgz package > > 2) using the proxy Sernet packages which use command: samba-tool domain join XXX.corp DC -U Administrator --realm = XXX.corp and set the squid via NTLM. > > Issues: > > 1) after the update I get the

The two systems I'm referring to are on different domains, different locations. No connection whatsoever except me being the one administering both. According to oEMInformation the server was provisioned by 4.3.3. I just checked the Samba log file and it seems that version 4.7.4 was running before the update. I'm now looking at the logs right before the upgrade and indeed, there have

I could really use some support with this. I understand it's always possible to just restore from a backup but the more interesting question is if something can be done with the data at hand. Basically, I'm trying to understand how it's possible that a dbcheck shows no errors, an ldbsearch is successful, and yet it's not possible to start the AD properly. What else is there that

How do we check the data from Samba4 that the data from Samba3 successfully migrated? I dunno if it successfully migrated coz got these (last part): [root at gaara LiveData]# /usr/local/samba/bin/samba-tool domain classicupgrade --dbdir=/srv/LiveData/var_lib_samba/samba --use-xattrs=yes --realm=kazekage.sura.sandbox.local --dns-backend=SAMBA_INTERNAL /srv/smb.conf Once the above files are

Our domain controllers have run samba 4.4.3 since it was released. We didn't upgrade because it was so stable :) I recently decided that release was too old and upgraded to 4.8.2 (then current). Our domain controllers were crashing on 4.8.2 so I upgraded to 4.8.3 as soon as it was released but this has not resolved the issue. When the issue occurs the DC becomes unresponsive and needs to be

On 13/08/15 13:12, Gabriel Franca wrote: > Good morning Rowland. > > Today there are 2 servers with Samba 4.1.19 > > 1) Samba 4.1.19 compiled used for the control domain (AD) > 2) using Samba 4.1.19 Sernet package I used the command "samba-tool domain join" to use the Squid authenticating via NTLM. > > Before I was as follows: > > 1) Samba 4.0.4 compiled AD

Hello Rowland Talking to users at that time discovered the following: They remove the machine network cable, put the User and Password them the domain, after the windows open the desktop they connect the network cable back in the machine and get to work. If you do this procedure is giving User and wrong password! On the issue of time the 2 DC's station using ntp. I stopped the samba

----- Original Message ----- | Hi Felipe, | Am 25.01.2017 um 14:16 schrieb Felipe_G0NZÁLEZ_SANTIAG0 via samba: | > I provisioned a server with Samba4.3 from repo ubuntu16.04. | > I tested some things, but I can NOT connect to my Samba DC from the Windows | > DNS client. | > ADUC, AD Sites and services, and AD Domain & Trusts, connects Ok. | > But DNS [" Acces is Denied

On 13/08/15 13:58, Gabriel Franca wrote: > Hello Rowland > > Talking to users at that time discovered the following: > > They remove the machine network cable, put the User and Password them the domain, after the windows open the desktop they connect the network cable back in the machine and get to work. > > If you do this procedure is giving User and wrong password! I am not

New to linux and new to Samba so any direction in troubleshooting would be helpful. Here is what I have so far. Within a half an hour of a reboot of the server my cpu reaches high numbers and becomes slow to respond on all actions. With my limited understanding I have used vmstat to observe the system. I noticed is that the numbers of forks grows from 1-2k to 43k within 30 minutes after reboot. I