similar to: Accidental samba_dnsupdate success after NT_STATUS_CONNECTION_REFUSED

Greetings, The process to join a new samba 4.6 DC to an existing samba 4.1 DC repeatedly caused: samba_dnsupdate --verbose --all-names to fail on the new DC with: Failed to connect host x.x.x.x on port 49152 - NT_STATUS_CONNECTION_REFUSED Noted: both samba versions are obsolete and will be updated post haste. Regardless, samba_dnsupdate was accidentally invoked on the new DC while the

Found the solution shortly after I sent this e-mail.  Needed to add "tls enabled = no" to the working server to get the other server to restore functionality. On 3/8/2018 3:58 PM, Brent Davidson via samba wrote: > I am desperately in need of help. I have a Centos 7.2 server running Samba > 4.6.13 as an active directory domain controller. I am trying to join a new > Centos

Andrew Bartlett wrote: > Don Kuenz wrote: >> >> Greetings, >> >> This post pertains to a Disaster Recovery (DR) scenario on a Samba 4.8 >> server. The DR server was provisioned as a standalone host, on a >> network isolated from the Production Server (PS). >> The DR's /var/db/samba4 directory, which contains the private >> directory,

I am desperately in need of help. I have a Centos 7.2 server running Samba 4.6.13 as an active directory domain controller. I am trying to join a new Centos 7.4 server running Samba 4.6.13 to the domain. The domain command will not connect to the other server. I have firewalld and selinux disabled on both servers, I can ping both ways. From the new server I was able to do a kinit -U

On Fri, 2019-11-15 at 20:16 +0000, Don Kuenz via samba wrote: > > Greetings, > > This post pertains to a Disaster Recovery (DR) scenario on a Samba > 4.8 > server. The DR server was provisioned as a standalone host, on a > network isolated from the Production Server (PS). > The DR's /var/db/samba4 directory, which contains the private > directory, was then

Andrea Venturoli wrote: > Don Kuenz wrote: > >> Samba 4.8. It turns out that both the FreeBSD bin and source packages >> are broke. Fully functional, error free binaries were eventually created >> by manually installing about a dozen requisite packages, one at a time >> along the way, whenever make halted on an error. >> To add to a difficult day, something

On Sun, 04 Dec 2016 08:01:09 -0600 Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > I have two DC's running Samba 4.5.0 and the "dtdc03" log.samba is > showing the following: > > root at dtdc03:~# tail -f /usr/local/samba/var/log.samba > [2016/12/01 10:14:39.167794, 0] > ../source4/librpc/rpc/dcerpc_sock.c:245(continue_ip_open_socket)

On Sun, 04 Dec 2016 09:43:25 -0600 Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > On 2016-12-04 09:11, Rowland Penny via samba wrote: > > > On Sun, 04 Dec 2016 08:01:09 -0600 > > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > > > >> I have two DC's running Samba 4.5.0 and the "dtdc03"

(Ah, just finish my message and Rowland also mosted. Well, see this as extra info ) This "should" not be needed. Run this : https://raw.githubusercontent.com/thctlo/samba4/master/samba-check-SePrivileges.sh bash samba-check-SePrivileges.sh And you see all default settings. And you should see: (everyhere) but i picked SeDiskOperatorPrivilege as example SeDiskOperatorPrivilege:

aha ... ;-) netstat --numeric-hosts --numeric-ports --programs -u -t -l i didnt see samba running.. ;-) >I removed the "service bind9 stop &&" from line 449 (as bind9 was >already stopped, why stop it again) and ran the script on my >VM. All the "NT_STATUS_CONNECTION_REFUSED" warnings were gone. but.. the NT_STATUS_CONNECTION_REFUSED is a samba

I have two DC's running Samba 4.5.0 and the "dtdc03" log.samba is showing the following: root at dtdc03:~# tail -f /usr/local/samba/var/log.samba [2016/12/01 10:14:39.167794, 0] ../source4/librpc/rpc/dcerpc_sock.c:245(continue_ip_open_socket) Failed to connect host 192.168.16.50 (aa03011a-94c2-4c52-bc60-6fd2f75d35e5._msdcs.dtshrm.dt) on port 135 - NT_STATUS_CONNECTION_REFUSED.

On 2016-12-04 10:25, Rowland Penny via samba wrote: > On Sun, 04 Dec 2016 09:43:25 -0600 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > > On 2016-12-04 09:11, Rowland Penny via samba wrote: > > On Sun, 04 Dec 2016 08:01:09 -0600 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > > I have two DC's running

Hello, I've been trying to install Samba4 for a while now, following the instructions over at: http://linuxdrops.com/install-samba-4-on-centos-rhel-fedora-debian-ubuntu/ However, when I get to the stage where I should be able to join the domain with a Windows machine (7, not XP) I run into networking issues. For one, my network is behind a NAT so I can't just use a public DNS for

On 27/02/15 17:28, Bob of Donelson Trophy wrote: > > > I thought I was over this the other day when I got it to work properly > on my VM. > > Now, on an actual PC I am getting: > > ==========Test kerberos =============================== > > Lets test some things > > Testing : kerberos > > Password for Administrator at DTSHRM.DT: > > Warning: Your

And please also do check hostname -s hostname -d hostname -f if you see somewhere 127.0.0.1 or incorrect hostname. Check /etc/hosts Greetz, Louis > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens mathias dufresne > Verzonden: woensdag 27 januari 2016 7:40 > Aan: Henry McLaughlin > CC: samba > Onderwerp: Re: [Samba]

On 26/02/15 08:15, L.P.H. van Belle wrote: > aha ... > > ;-) > > netstat --numeric-hosts --numeric-ports --programs -u -t -l > i didnt see samba running.. ;-) > > >> I removed the "service bind9 stop &&" from line 449 (as bind9 was >> already stopped, why stop it again) and ran the script on my >> VM. All the

I'm running samba 4.1.2 on Linux Mint 15. Getting the following: ? ./samba-tool drs kcc samba-realm Failed to connect host 192.168.231.132 on port 135 - NT_STATUS_CONNECTION_REFUSED Failed to connect host 192.168.231.132 (samba-realm) on port 135 - NT_STATUS_CONNECTION_REFUSED. I don't see samba or smbd listening on port 135. 53 and 137 are. e.g.: ? netstat -anp | grep samba | grep

On 27/02/15 18:00, Bob of Donelson Trophy wrote: > > > Thanks Rowland. > > Being the novice that I am, I thought the line would 'pickup' my DOMAIN > and replace the ${SAMBA_NT_DOMAIN}. So, I just tried the line correctly > and it asked for my Administrator password and subsequently granted > access. At least I know I can go and correct manually, if I need too.

On 2016-12-04 09:11, Rowland Penny via samba wrote: > On Sun, 04 Dec 2016 08:01:09 -0600 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > >> I have two DC's running Samba 4.5.0 and the "dtdc03" log.samba is >> showing the following: >> >> root at dtdc03:~# tail -f /usr/local/samba/var/log.samba >> [2016/12/01

Hai, Base on : >I have applied the changes as suggested. >After restarting the server, smbclient-command worked! But after I restarted the Samba Client with > ?/etc/init.d/samba restart? I was once again confronted with the same problem! >Again, only another server restart did the trick. Can you retry the restart samba with systemd and see if thats working better. Type :