Rowland Penny
2024-Jan-03 20:16 UTC
[Samba] {Device Timeout} The I/O operation specified in %hs was not completed before the timeout period expired
On Wed, 3 Jan 2024 17:09:26 -0300 Elias Pereira <empbilly at gmail.com> wrote:> Sorry, but I didn't realize that in the command I didn't specify to > check for udp. > > root at dc2:~# nmap --min-parallelism 100 -p > 53,88,135,139,389,445,464,636,3268,3269,49152-65535 200.132.218.160 > *(dc3)* Starting Nmap 7.93 ( https://nmap.org ) at 2024-01-03 17:02 > -03 Nmap scan report for DC3 (200.132.218.160) > Host is up (0.00015s latency). > Not shown: 16381 closed tcp ports (reset) > PORT STATE SERVICE > 53/tcp open domain > 88/tcp open kerberos-sec > 135/tcp open msrpc > 139/tcp open netbios-ssn > 389/tcp open ldap > 445/tcp open microsoft-ds > 464/tcp open kpasswd5 > 636/tcp open ldapssl > 3268/tcp open globalcatLDAP > 3269/tcp open globalcatLDAPssl > 49152/tcp open unknown > 49153/tcp open unknown > 49154/tcp open unknown > MAC Address: BE:79:98:04:F5:84 (Unknown) > Nmap done: 1 IP address (1 host up) scanned in 0.59 seconds > > root at dc2:~# nmap --min-parallelism 100 -p 53,88,123,137,138,389,464 > -sU 200.132.218.160 *(dc3)* > Starting Nmap 7.93 ( https://nmap.org ) at 2024-01-03 17:03 -03 > Nmap scan report for DC3 (200.132.218.160) > Host is up (0.0011s latency). > > PORT STATE SERVICE > 53/udp open domain > 88/udp open|filtered kerberos-sec > 123/udp open ntp > 137/udp open netbios-ns > 138/udp open|filtered netbios-dgm > 389/udp open ldap > 464/udp open|filtered kpasswd5 > MAC Address: BE:79:98:04:F5:84 (Unknown) > Nmap done: 1 IP address (1 host up) scanned in 1.38 seconds > > Is a firewall running and if so, are all the > > required ports open ? > > Okay. All the necessary ports are open. > > Is dns configured correctly ? > > root at dc2:~# cat /etc/resolv.conf > search campus.sertao.ifrs.edu.br > nameserver 200.132.218.163 (*own IP*) > > root at dc3:~# cat /etc/resolv.conf > search campus.sertao.ifrs.edu.br > nameserver 200.132.218.160 (*own IP*) > > Based on this, what could be causing the "timeout" in the replica > command? >Everything looks okay, so I am not sure what is going on here, kerberos ??? What is in /etc/krb5.conf ? Rowland
Elias Pereira
2024-Jan-03 20:24 UTC
[Samba] {Device Timeout} The I/O operation specified in %hs was not completed before the timeout period expired
> > Everything looks okay, so I am not sure what is going on here, kerberos???I don't know either! :( What is in /etc/krb5.conf ? root at dc2:~# cat /etc/krb5.conf [libdefaults] dns_lookup_realm = false dns_lookup_kdc = true default_realm = CAMPUS.SERTAO.IFRS.EDU.BR root at dc2:~# ls -laht /etc/krb5.conf -rw-r--r-- 1 root bind 115 Dec 12 15:31 /etc/krb5.conf root at dc3:~# cat /etc/krb5.conf [libdefaults] dns_lookup_realm = false dns_lookup_kdc = true default_realm = CAMPUS.SERTAO.IFRS.EDU.BR root at dc3:~# ls -laht /etc/krb5.conf -rw-r--r-- 1 root bind 115 Jul 7 11:33 /etc/krb5.conf Is there any way I can increase the timeout in the command? On Wed, Jan 3, 2024 at 5:17?PM Rowland Penny via samba < samba at lists.samba.org> wrote:> On Wed, 3 Jan 2024 17:09:26 -0300 > Elias Pereira <empbilly at gmail.com> wrote: > > > Sorry, but I didn't realize that in the command I didn't specify to > > check for udp. > > > > root at dc2:~# nmap --min-parallelism 100 -p > > 53,88,135,139,389,445,464,636,3268,3269,49152-65535 200.132.218.160 > > *(dc3)* Starting Nmap 7.93 ( https://nmap.org ) at 2024-01-03 17:02 > > -03 Nmap scan report for DC3 (200.132.218.160) > > Host is up (0.00015s latency). > > Not shown: 16381 closed tcp ports (reset) > > PORT STATE SERVICE > > 53/tcp open domain > > 88/tcp open kerberos-sec > > 135/tcp open msrpc > > 139/tcp open netbios-ssn > > 389/tcp open ldap > > 445/tcp open microsoft-ds > > 464/tcp open kpasswd5 > > 636/tcp open ldapssl > > 3268/tcp open globalcatLDAP > > 3269/tcp open globalcatLDAPssl > > 49152/tcp open unknown > > 49153/tcp open unknown > > 49154/tcp open unknown > > MAC Address: BE:79:98:04:F5:84 (Unknown) > > Nmap done: 1 IP address (1 host up) scanned in 0.59 seconds > > > > root at dc2:~# nmap --min-parallelism 100 -p 53,88,123,137,138,389,464 > > -sU 200.132.218.160 *(dc3)* > > Starting Nmap 7.93 ( https://nmap.org ) at 2024-01-03 17:03 -03 > > Nmap scan report for DC3 (200.132.218.160) > > Host is up (0.0011s latency). > > > > PORT STATE SERVICE > > 53/udp open domain > > 88/udp open|filtered kerberos-sec > > 123/udp open ntp > > 137/udp open netbios-ns > > 138/udp open|filtered netbios-dgm > > 389/udp open ldap > > 464/udp open|filtered kpasswd5 > > MAC Address: BE:79:98:04:F5:84 (Unknown) > > Nmap done: 1 IP address (1 host up) scanned in 1.38 seconds > > > > Is a firewall running and if so, are all the > > > required ports open ? > > > > Okay. All the necessary ports are open. > > > > Is dns configured correctly ? > > > > root at dc2:~# cat /etc/resolv.conf > > search campus.sertao.ifrs.edu.br > > nameserver 200.132.218.163 (*own IP*) > > > > root at dc3:~# cat /etc/resolv.conf > > search campus.sertao.ifrs.edu.br > > nameserver 200.132.218.160 (*own IP*) > > > > Based on this, what could be causing the "timeout" in the replica > > command? > > > > Everything looks okay, so I am not sure what is going on here, kerberos > ??? > What is in /etc/krb5.conf ? > > Rowland > > > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba.org/mailman/options/samba >-- Elias Pereira