similar to: Error NT_STATUS_CONNECTION_REFUSED samba@lists.samba.org)

On Wed, 20 Feb 2019 17:21:18 -0500 samba.x.eliezer613 at spamgourmet.com wrote: > Hi, followed your github page. Near the end get... It's not my github page, it's Louis's >  cat /etc/netplan/01-netcfg.yaml > cat: /etc/netplan/01-netcfg.yaml: No such file or directory Cannot help you there, I always remove netplan, but perhaps Louis can comment. > > I am running

Hi, After installing samba on ubuntu 18.04 following the guide at https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directory_Domain_Controller  can't do anything with it. # smbclient -L localhost -N Connection to localhost failed (Error NT_STATUS_CONNECTION_REFUSED) looks like its not even running... ps ax | egrep "samba|smbd|nmbd|winbindd"  1965 pts/0    S+     0:00

On Tue, 19 Feb 2019 18:40:03 -0500 samba.x.eliezer613 at spamgourmet.com wrote: > Hi Rowland, actually just trying to learn AD. Have a 'regular' samba > server running here for years. In as much as a smb.conf it seems to > have one : > > [global] >         dns forwarder = 192.168.25.253 >         netbios name = DC1 >         realm = DC1.INTERNAL >        

On 18/10/2019 18:48, John Redmond wrote: > DNS is another area where I have read and experimented a lot.? Result: > confusion.? Again, I'm using fresh installs of Ubuntu 18.04 LTS > "server" for both the AD-DC and the fileserver machines.? Here's what > the various config files on the fileserver look like now.? Test > results are not exactly what they

On Tue, 8 Jan 2019 09:38:54 +0530 venkat ramu <ramut123 at gmail.com> wrote: > Hi Rowland, > > Please find the attached requested details. also Could you please > share right document for the SAMBA configuration with AD > authentication for file server. Thank you the help. > > Thanks, > Venkat OK, you have a choice here, you can either do what I do, which is make

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Am 20.02.19 um 20:51 schrieb samba.x.eliezer613--- via samba: > After installing samba on ubuntu 18.04 following the guide at > https://wiki.samba.org/index.php/Setting_up_Samba_as_an_Active_Directo ry_Domain_Controller > can't do anything with it. > > # smbclient -L localhost -N Connection to localhost failed (Error >

On Wed, 20 Feb 2019 09:19:27 -0500 samba.x.eliezer613 at spamgourmet.com wrote: > Hi Rowland, no samba is not running on the VM. I will yum remove > samba* and build from tarball and see what happens. > Better still, use another distro, the red-hat distros will never allow provisioning of a Samba AD DC. Building Samba to update soon gets tiring. Rowland

Hi Rowland, Thats not the point here, if this is a AD-DC or not.. ;-) I'll explain. This is about, how DNS requests are done on the system and accepted by the "dns service" You can install unlimited DNS servers on the AD-DC and chain them, but wize.. No offcourse not. :-) Turning off systemd-resolved is probably a good idea, yes, it is. But it does not harm if its on as long

So, I'm curious about the contrast between modifying netplan vs simply disabling systemd.resolved Is there some advantage to the gyrations to make netplan work, vs simply disabling resolved and manually defining the IP and DNS server? [I'm not complaining, I'm thankful for all the options - just wanting to have the best handle possible on the reasoning behind one method vs the other.]

Hai, I detected a minor error and i added a quick fix. And i'm testing my 4.8.1 debian package on ubuntu 18.04, see below.. Syslog shows. May 9 14:50:26 ubuntu1804 systemd[9448]: /lib/systemd/system-generators/netplan failed with exit status 1. The fix is: editor /etc/netplan/01-netcfg.yaml The last adresses: needs a server adres. cat /etc/netplan/01-netcfg.yaml # This file describes

Hai James, Thanks, thats exactly what we needed. I'll comment below. > -----Oorspronkelijk bericht----- > Van: James Atwell [mailto:james.atwell365 at gmail.com] > Verzonden: donderdag 13 augustus 2020 14:46 > Aan: samba at lists.samba.org > CC: L.P.H. van Belle > Onderwerp: Re: [Samba] Samba DNS fails when queried with > nslookup commands > > Hi Louis and

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

Le 03/05/2019 à 16:20, L.P.H. van Belle a écrit : > Hai, > > wbinfo -Y S-1-5-21-2816186202-4468957523-2022743653-513 > Does this resolve? > You should see "domain users" I see 13010 (that's normal according to the doc) but wbinfo --sid-to-fullname S-1-5-21-2816186202-4468957523-2022743653-513 give me "domain users" > > And your missing your

On Ubuntu 20.04 I have provisioned a AD DC using samba-4.12 from Louis' Repo and his instructions: https://github.com/thctlo/samba4/blob/master/full-howto-Ubuntu18.04-samba-AD_DC.txt In the output of: samba-tool domain provision --use-rfc2307 --realm=XXX.XXX --domain=XXX --dns-backend=BIND9_DLZ --adminpass=XXXxxx I see this: WARNING /usr/lib/python3/dist-packages/samba/provision/sambadns.py

Hai, Only the forwarder is running in this systemd setup. This : 127.0.0.53:53 does NOT conflict with normaly resolv.conf setting Because samba or any dns server does not run on 127.0.0.53 Dont make the mistake to see this for : 127.0.0.1 Please show : /etc/hosts /etc/resolv.conf Depending on which one your using: /etc/network/interfaces and/or /etc/netplan/01-netcfg.yaml

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

Hai, wbinfo -Y S-1-5-21-2816186202-4468957523-2022743653-513 Does this resolve? You should see "domain users" And your missing your primary dnsdomain. (search) Go here. https://github.com/thctlo/samba4/blob/master/full-howto-Ubuntu18.04-samba-AD_DC.txt Your missing, ( see line 370 ) search: [ internal.example.com ] Add it.. Also i missed 2 other points. smb.conf add:

On 27/02/15 19:25, Bob of Donelson Trophy wrote: > > > Thanks Rowland but that idea did not work. > > I will simply grant access to those that failed manually. > > (Really wish I had kept the VM that the scripthad worked on so I could > go back and see what happened but, too late, I have already deleted to > save precious hard drive space.) > > If I have any

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"