similar to: NT_STATUS_IO_TIMEOUT at open_socket_out_send due to firewall

Have you tried using IPTABLES to REJECT that port. It will send something back and then maybe the timeout will fail immediately instead of waiting the timeout period? So on the local machine(that is running winbind) try iptables -A OUTPUT -p tcp --dport 49155 -j REJECT iptables -A INPUT -p tcp --dport 49155 -j REJECT Might not need it in both, but since we are checking... Jason On Thu, Jun

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

Good Morning, Ive been trying to test Samba AD on Ubuntu 18.04 using samba version 4.8.0  The DC seems to be working fine all tests have passed.  I was able to connect Win7 RSAT, a Ubuntu workstation and a File server.  My problem is the file server will not give response to 'sudo getent passwd' with or with out username or DOMAIN\username. Everything else works as far as I can tell.

dear samba community, we have a big problem on joining a Samba 3.5.6 PDC. Hopefully anyone has an idea/suggestion. When trying to join with a Samba 4.2.10 or 4.3.9 we got the following error on client site: Failed to pull dcerpc auth: NT_STATUS_RPC_PROTOCOL_ERROR. cli_rpc_pipe_open_schannel_with_key: rpc_pipe_bind failed with error NT_STATUS_RPC_PROTOCOL_ERROR libnet_join_ok: failed to open

Some additional info: The solaris server is Solaris 10 (sparc.) According to man smb.conf, "enable asu support = yes" creates an IPC only "ADMIN$" share. Using the computer management tool from a Windows machine I could verify this was the case. However, the "ADMIN$" share on the PC Netlink server is actually a data share. I did try "enable asu support =

On 03/04/15 19:33, Andrey Repin wrote: > Greetings, Rowland Penny! > >>>>>> I'm trying to get the former PDC back into domain after performing a >>>>> classic >>>>>> migration. >>>>>> AD DC is running fine... if you can call it that. >>>>>> I've edited the smb.conf and nsswitch.conf as suggested in

Some additional info: The solaris server is Solaris 10 (sparc.) According to man smb.conf, "enable asu support = yes" creates an IPC only "ADMIN$" share. Using the computer management tool from a Windows machine I could verify this was the case. However, the "ADMIN$" share on the PC Netlink server is actually a data share. I did try "enable asu support =

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

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

On 03/04/15 21:29, Andrey Repin wrote: > Greetings, Rowland Penny! > >>>>>>>> I'm trying to get the former PDC back into domain after performing a >>>>>>> classic >>>>>>>> migration. >>>>>>>> AD DC is running fine... if you can call it that. >>>>>>>> I've edited the

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

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 >

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

Hi, I get lot of these messages in log.winbindd! (failed tcon_X with NT_STATUS_IO_TIMEOUT) Can anyone tell what this means? Thank you. jonnyD

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

Trying to copy a large file from a Windows 10 box Using smbclient - like so. smbclient -U administrator%somepass //10.1.2.3/temp prompt recurse mget * mget starts, but then fails with the following details. --- parallel_read returned NT_STATUS_IO_TIMEOUT NT_STATUS_CONNECTION_DISCONNECTED opening remote file \abc.txt NT_STATUS_CONNECTION_DISCONNECTED listing \* smb: \> getting file

hi, The error is consistently occurring across all four of my DCs. [2024/01/19 14:02:05.917120, 0] source4/dsdb/kcc/kcc_periodic.c:790(samba_kcc_done) source4/dsdb/kcc/kcc_periodic.c:790: Failed samba_kcc - NT_STATUS_IO_TIMEOUT I configured logging to level 5 and observed DC1. No errors were detected; instead, kcc_periodic.c executed smoothly, and the system reported a successful outcome.

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

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