search for: werr_connection_refus

...keep you posted. You can also use this little script as a workaround, run frequently via cron (provided by Marco van Zwetselaar). Will check if replication is broken and restart the service accordingly. ----- #!/bin/sh # # check-samba-ad-dc.sh # # Stop gap measure to restart the Samba AD DC on WERR_CONNECTION_REFUSED # https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1357471 # https://bugzilla.samba.org/show_bug.cgi?id=11164 TMPFILE="/tmp/$(basename "$0").$$" if ! samba-tool drs showrepl > "$TMPFILE" || ! grep -q 'Last attempt .* successful' "$TMP...

...0 (0) error_string : 'failed to lookup DC info for domain 'AD.INTERDEKOR.COM.UA' over rpc: The connection was refused' domain_is_ad : 0x00 (0) set_encryption_types : 0x00000000 (0) result : WERR_CONNECTION_REFUSED Failed to join domain: failed to lookup DC info for domain ' AD.INTERDEKOR.COM.UA' over rpc: The connection was refused Does somebody has any idea?

...g from the new DC: ==== INBOUND NEIGHBORS ==== CN=Schema,CN=Configuration,DC=iumnet,DC=edu,DC=na Default-First-Site-Name\IUMSVRPDC via RPC DSA object GUID: 27182378-a9c7-451e-bb95-7b2172a5f311 Last attempt @ Fri Oct 27 16:03:15 2017 WAST failed, result 1225 (WERR_CONNECTION_REFUSED) 28 consecutive failure(s). Last success @ NTTIME(0) Here is the smb.conf from both the servers: *PDC* # Global parameters [global] workgroup = IUMNET realm = IUMNET.EDU.NA netbios name = IUMDCDP01 server role = active directory dom...

...tring : 'failed to lookup DC info for > domain > 'AD.INTERDEKOR.COM.UA' over rpc: The connection was refused' > domain_is_ad : 0x00 (0) > set_encryption_types : 0x00000000 (0) > result : WERR_CONNECTION_REFUSED > Failed to join domain: failed to lookup DC info for domain ' > AD.INTERDEKOR.COM.UA' over rpc: The connection was refused > > Does somebody has any idea? > -- > To unsubscribe from this list go to the following URL and read the > instructions: https://lists.samba....

...quot;AD Site & Services". But after the join of Site1DC and Site2DC for both a replication link to the OtherSiteDC is automatically created in addition to the expected CentralDC replication link in NTDS Settings. And this unwanted replication link shows up in showrepl (as expected w/ error WERR_CONNECTION_REFUSED as there is no direct connection between the sites) Deleting the unwanted replication link in RSAT "AD Site & Services" has no effect, it will automatically re-appear later (named <automatically generated> again). On all DCs running 'samba-tool drs kcc' issues no erro...

...es : Warning: /usr/sbin/samba > already running ! ... (warning). > > So after all the script tries to start samba again, but since > there appeared to be a process remaining, it fails to > actually start, and this causes all kinds of failures: > > - Replication fails with (WERR_CONNECTION_REFUSED) > - LDAP queries to that dc fail with query error: Transport > endpoint is not connected > > Rebooting the DC solves everything, but scheduling a reboot > every morning is not an elegant solution. :-) > > Here is the part of the sernet-samba-ad script where the > res...

On Fri, 16 Dec 2016 13:46:24 +0100 Artur Moor via samba <samba at lists.samba.org> wrote: > If I remove 'nmbd bind explicit broadcast = no' in 'smb4.conf', then > nmbd wan't start and I get following in the log: > > [2016/12/16 12:37:35.075428, 0] > ../source3/lib/util_sock.c:396(open_socket_in) > bind failed on port 137 socket_addr = 10.0.140.255.

...you have a DC. ==== INBOUND NEIGHBORS ==== CN=Schema,CN=Configuration,DC=iumnet,DC=edu,DC=na Default-First-Site-Name\IUMSVRPDC via RPC DSA object GUID: 27182378-a9c7-451e-bb95-7b2172a5f311 Last attempt @ Fri Oct 27 16:03:15 2017 WAST failed, result 1225 (WERR_CONNECTION_REFUSED) 28 consecutive failure(s). Last success @ NTTIME(0) Here is the smb.conf from both the servers: *PDC* Did I mention you do not have a PDC ? :-) # Global parameters [global] workgroup = IUMNET realm = IUMNET.EDU.NA netbios name = IUMD...

...ailed! > Starting SAMBA AD services : Warning: /usr/sbin/samba already running ! ... (warning). So after all the script tries to start samba again, but since there appeared to be a process remaining, it fails to actually start, and this causes all kinds of failures: - Replication fails with (WERR_CONNECTION_REFUSED) - LDAP queries to that dc fail with query error: Transport endpoint is not connected Rebooting the DC solves everything, but scheduling a reboot every morning is not an elegant solution. :-) Here is the part of the sernet-samba-ad script where the restart occurs: > PID=$(cat ${PIDFILE})...

> Why bother with all the above, just use samba-ad-dc instead. Yes, I streamlined the script somewhat. Let's see what happens when replication fails next time. > You are going to have to supply more info, is there anything in the logs > when replication fails? > If not, try raising the log level until you do get something. Anything specific I should look for? As said it