search for: nt_status_io_timeouts

hello folks. congrats on samba 3.2 it's an awesome release. i'm trying to take advantage of the parallel cifs capabilities of this release. lustre (too complex) and gpfs (not free) at not available to me right now, so i'm using gfs v2 and iscsi as my storage building blocks. i'm running 3.2 on centos 5.2. everything is configured and i compiled samba4 to use smbtorture,

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

Dear all, we are transitioning from an openldap / MIT KDC setup to a samba4 AD. I am doing this by setting up a samba NT4 domain, populating it from LDAP and sticking in the password hashes which I automatically extract from the MIT KDC arc4-hmac keys. Then I run the classicupgrade. I do this whole thing from cron in a script once a day to be able to slowly migrate services. The MIT / openldap

Hello all, Im on the latest fresh installed centos7 with samba / winbind samba: Architektur : x86_64 Version : 4.2.10 Ausgabe : 6.el7_2 Name : samba-winbind Architektur : x86_64 Version : 4.2.10 Ausgabe : 6.el7_2 doing wbinfo -i user is working doing wbinfo -g is working doing wbinfo -u is not working and I get in winbind log: NT_STATUS_IO_TIMEOUT and Im not able to access

On Mon, 11 Mar 2019 07:16:30 +0100 Christian via samba <samba at lists.samba.org> wrote: > Dear all, > > we are transitioning from an openldap / MIT KDC setup to a samba4 AD. > I am doing this by setting up a samba NT4 domain, populating it from > LDAP and sticking in the password hashes which I automatically > extract from the MIT KDC arc4-hmac keys. Then I run the >

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

On Mon, 2019-03-11 at 07:16 +0100, Christian via samba wrote: > Dear all, > > we are transitioning from an openldap / MIT KDC setup to a samba4 AD. I > am doing this by setting up a samba NT4 domain, populating it from LDAP > and sticking in the password hashes which I automatically extract from > the MIT KDC arc4-hmac keys. Then I run the classicupgrade. I do this > whole

Hai, I'm preparing for my wintersport vacantion and i must finish some things here. So thats why im low profiling atm. Try in the command line. Remove -UDOM\Adminstrator Add : -k -S hostname(.fqdn) Is expect that to work. Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens > Rowland Penny via samba >

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

I've been grappling with a recurring set of errors for quite some time now: - UpdateRefs failed with NT_STATUS_IO_TIMEOUT - Failed samba_kcc - NT_STATUS_IO_TIMEOUT - IRPC callback failed for DsReplicaSync - NT_STATUS_IO_TIMEOUT Despite cranking up the log level to 10, the returned information remains frustratingly cryptic and hard to decipher. This error, being overly generic, continues to

Hello all, I'm having a problem with smbclient after an upgrade from 3.0.37 to 3.5.3 (I also tested 3.5.11 and 3.6.0). The client uses a command similar to: tar -cz /some/directory | smbclient '\\server_ip\share' -N -c 'put - "\directory\filename"' After that the client checks the exit status to determine if the transfer succeeded or failed. The server

On Tue, 12 Mar 2019 01:47:53 +0100 Christian via samba <samba at lists.samba.org> wrote: > Am 11.03.2019 um 09:24 schrieb Rowland Penny via samba: > > On Mon, 11 Mar 2019 07:16:30 +0100 > > Christian via samba <samba at lists.samba.org> wrote: > > > >> Dear all, > >> > >> we are transitioning from an openldap / MIT KDC setup to a samba4

Am 11.03.2019 um 09:24 schrieb Rowland Penny via samba: > On Mon, 11 Mar 2019 07:16:30 +0100 > Christian via samba <samba at lists.samba.org> wrote: > >> Dear all, >> >> we are transitioning from an openldap / MIT KDC setup to a samba4 AD. >> I am doing this by setting up a samba NT4 domain, populating it from >> LDAP and sticking in the password hashes

Hello Andrew, 1. What is the explanation for the fact that when the log level is set to 5 or 7, the NT_STATUS_IO_TIMEOUT error does not appear, but when it is at the default log level, it does? Another point I've noticed before is that when I run the command "samba-tool dbcheck --cross-ncs --reset-well-known-acls --fix --yes" (*Checked 15337 objects (0 errors)*), and in another

Either the local server is busy, or possibly (but it would not explain the samba_kcc) Samba's drepl process is stuck talking to a remote server. Is the drepl local processes very busy doing inbound replication? My instinct is either the server is very busy (and this should show up in CPU use) or a transaction is being held open excessively. Andrew Bartlett On Sat, 2024-03-09 at 19:11 -0300,

Samba occasionally fails with the following. I have seen many questions regarding this but no answers unfortunately. I am wondering what the setting is where I can increase this time out value of 10000 milliseconds in case that specific request is just slow. This is called many times a day and only just occasionally fails. I have looked through the entire manual for smb.conf and can't find a

I have an unusual problem that I can't seem to figure out. As a background I had to rebuild my Samba4 AD DC from scratch, since my USB stick went out. The Samba4 AD DC is now running on a Raspberry Pi with the root file system on an external USB hard drive. It also has an email server using postfix/dovecot/spamassassin on it too. It's very cool to have an AD DC and email server

On Thu, 2024-04-11 at 14:21 -0300, Elias Pereira wrote: > Hello?Andrew, > > 1. What is the explanation for the fact that when the log level is > set to 5 or 7, the NT_STATUS_IO_TIMEOUT error does not appear, but > when it is at the default log level, it does? I don't have an explanation for this, sorry. ?Have you looked into the 1.5 second queries, what is sending them 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) >

Bump. On 06/15/2016 11:42 AM, Mike Ely wrote: > Hi, > > We've got a few layers of firewall between our DCs and a domain guest > providing winbind services. What I've noticed is that on first run > winbind tries to use the high ports to set up part of the > communication. During that process, the winbindd process runs at 100% > CPU, and it takes about two minutes