similar to: Fwd: Two DNS issues with samba

Displaying 20 results from an estimated 7000 matches similar to: "Fwd: Two DNS issues with samba"

2024 Jun 08
1
Fwd: Two DNS issues with samba
On Sat, 8 Jun 2024 17:05:25 +0200 Ronny Preiss via samba <samba at lists.samba.org> wrote: > Hi, > > I have two problems with my 2 Samba AD-DC. I don't know if the two > problems are related. > Both domain controllers show the same error pattern for problem 1.The > second problem only occurs with the second domain controller. > The domain itself seems to work and
2024 Jun 09
1
Fwd: Two DNS issues with samba
> No need to build Samba yourself, you can find packages here: > > http://www.corpit.ru/mjt/packages/samba/ How can I install these files? Here are the requested files from both servers. ## DC01 ## /etc/hostname 01-dc01 ----- /etc/hosts 127.0.0.1 localhost #127.0.1.1 01-dc01 # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0
2024 Jun 23
3
Fwd: Two DNS issues with samba
Hi, - I have changed my /etc/resolv.conf for all my three DCs. ### DC 01-03 nameserver 10.10.10.11 nameserver 10.10.10.12 nameserver 10.10.10.13 search intern.preiss.network - In the next step I changed my /etc/hosts for each DC ### DC1 127.0.0.1 localhost 10.10.10.11 01-dc01.intern.preiss.network 01-dc01 ### DC2 127.0.0.1 localhost 10.10.10.12 01-dc02.intern.preiss.network 01-dc02
2024 Jun 14
1
Fwd: Two DNS issues with samba
On Fri, 14 Jun 2024 08:04:57 +0200 Ronny Preiss via samba <samba at lists.samba.org> wrote: > Am Mo., 10. Juni 2024 um 10:14 Uhr schrieb Rowland Penny via samba < > samba at lists.samba.org>: > > > On Sun, 9 Jun 2024 13:18:10 +0200 > > Ronny Preiss via samba <samba at lists.samba.org> wrote: > > > > > > No need to build Samba yourself, you
2019 Aug 16
2
Failing to join existing AD as DC
First of all, thanks to you all for bearing with me. To answer the questions: - Subnets: yes, different subnets, routing is fine, can connect to Windows DC via telnet (DNS), OpenSSL on 389 and 636 - Naming: I could not find any object in the existing AD with the same name of the Samba DC that I want to add - Join existing: I try to join an existing Windows AD, not Samba AD I wiped the
2024 Jun 14
1
Fwd: Two DNS issues with samba
Am Mo., 10. Juni 2024 um 10:14 Uhr schrieb Rowland Penny via samba < samba at lists.samba.org>: > On Sun, 9 Jun 2024 13:18:10 +0200 > Ronny Preiss via samba <samba at lists.samba.org> wrote: > > > > No need to build Samba yourself, you can find packages here: > > > > > > http://www.corpit.ru/mjt/packages/samba/ > > How can I install these
2019 Mar 08
2
ipconfig /registerdns & PTR Records
Hello $LIST, i setup a new clean domain to examine the feature of updating/creating PTR records. When i call ipconfig /registerdns on the client i get this entry in the windows eventlog (sorry german) Fehler beim Registrieren der Hostressourceneinträge (A oder AAAA) für den Netzwerkadapter mit den folgenden Einstellungen: Adaptername: {2A467E48-624B-4CCF-9B7D-9BA5629D8117}
2024 Jun 10
1
Fwd: Two DNS issues with samba
On Sun, 9 Jun 2024 13:18:10 +0200 Ronny Preiss via samba <samba at lists.samba.org> wrote: > > No need to build Samba yourself, you can find packages here: > > > > http://www.corpit.ru/mjt/packages/samba/ > How can I install these files? Try reading the 'README' file from the link I posted. > > Here are the requested files from both servers. > >
2013 May 29
1
Error Message while joining a Domain as a DC
I joined an existing domain according to: https://wiki.samba.org/index.php/Samba4/HOWTO/Join_a_domain_as_a_DC My var/log.samba shows the following error message ... and unfortunately ... I have no idea what that means. [2013/05/29 20:48:00, 0] ../lib/util/util_runcmd.c:334(samba_runcmd_io_handler) /usr/local/samba/sbin/samba_dnsupdate: tkey query failed: GSSAPI error: Major = Unspecified
2016 Sep 21
2
replPropertyMetaData & KCC issues after updating to Samba 4.5.0
On 9/18/2016 6:23 PM, Garming Sam wrote: > Hi, > > For the unsorted attributeID values errors, can you first try: > > samba-tool dbcheck --cross-ncs --fix --yes 'fix_replmetadata_unsorted_attid' > > There's too much going on, and it does look like it might be bailing > out. Running it with 'fix_replmetadata_unsorted_attid' should fix those > first
2019 Jan 02
2
AD bind DNS broken after 4.7.3 -> 4.9.2 upgrade
On Wed, 02 Jan 2019 20:09:44 +0100 Král Gergely via samba <samba at lists.samba.org> wrote: > 2018-12-31 20:50 időpontban L.P.H. van Belle via samba ezt írta: > > Can you try to upgrade to any 4.8 version then to 4.9.4? > > might work, atleast my guess this will have a better chance get > > passed this bug. > > > > I can confirm that an upgrade to 4.7.3 to
2024 Jun 13
1
winbind error after startup on Samba member server
Hi folks, The last log record from journalctl -xeu winbind directly after winbind startup is: Jun 13 12:41:36 datasrv winbindd[582]: gpupdate_cmd_done: gpupdate failed with exit status 1 For completeness, the log entries for winbind startup is displayed below. Things seem to work though, but I have never seen it before (I don't like error messages). When I noticed the message I
2024 Jun 13
1
winbind error after startup on Samba member server
On Thu, 13 Jun 2024 16:26:17 +0200 Peter Milesson via samba <samba at lists.samba.org> wrote: > Hi folks, > > The last log record from journalctl -xeu winbind directly after > winbind startup is: > > Jun 13 12:41:36 datasrv winbindd[582]: gpupdate_cmd_done: gpupdate > failed with exit status 1 > > For completeness, the log entries for winbind startup is
2018 Mar 23
2
samba 4.7->4.8 in place upgrade
Hi, i have the same problem. Inplace upgrade and i get the following error. Mar 23 13:46:50 orion2 systemd[1]: Started Session 30346 of user root. Mar 23 13:46:50 orion2 systemd-logind[1316]: Removed session 30346. Mar 23 13:46:50 orion2 sernet-samba-ad[7358]: Shutting down SAMBA AD services : ..done Mar 23 13:46:50 orion2 systemd[1]: Stopped LSB: initscript for the SAMBA AD services. Mar 23
2024 Jun 13
1
winbind error after startup on Samba member server
On 13.06.2024 17:21, Rowland Penny via samba wrote: > On Thu, 13 Jun 2024 16:26:17 +0200 > Peter Milesson via samba <samba at lists.samba.org> wrote: > >> Hi folks, >> >> The last log record from journalctl -xeu winbind directly after >> winbind startup is: >> >> Jun 13 12:41:36 datasrv winbindd[582]: gpupdate_cmd_done: gpupdate >>
2019 Jan 02
2
AD bind DNS broken after 4.7.3 -> 4.9.2 upgrade
> On 2 Jan 2019, at 22:43, Rowland Penny via samba <samba at lists.samba.org> wrote: > > On Wed, 2 Jan 2019 19:35:04 +0000 > Rowland Penny via samba <samba at lists.samba.org> wrote: > >> On Wed, 02 Jan 2019 20:09:44 +0100 >> Král Gergely via samba <samba at lists.samba.org> wrote: >> >>> 2018-12-31 20:50 időpontban L.P.H. van Belle
2012 Sep 20
1
Samba4, DHCP, & BIND DLZ
Hello, I have recently compiled, installed and configured samba4 to run on a FreeBSD server. samba -V reports the version to be Version 4.1.0pre1-GIT-57990cb. The server has working BIND 9.9 and ISC-DHCP services running on it. I have provisioned samba 4 to use the BIND_DLZ DNS backend. On the whole things seem to be working. local names are being resolved. phpLDAPAdmin shows the new
2018 Jul 02
2
samba 4.8.3 "apply group policy = yes" error
Hello, Centos 7.5 samba 4.8.3 installation, compiled from source working as AD DC. It was an update from 4.7 (not an in place update, but added new DC's to existing domain and demoted 4.7.x DC's). After adding to my smb.conf: /apply group policies = yes/ I see errors on samba star: ../lib/util/util_runcmd.c:327(samba_runcmd_io_handler)   /usr/local/samba/sbin/samba_gpoupdate: SID
2016 Mar 22
2
Samba4 - Cannot contact any KDC for requested realm
Good afternoon, I have installed a fileserver with samba4 environment. This is configured to works as AD-DC even if I only use it as a fileserver (at the moment). All seems to works fine but, every 10 minutes, the log print these messages: Mar 22 11:53:17 fileserver samba[1946]: [2016/03/22 11:53:17.557554, 0] ../lib/util/util_runcmd.c:324(samba_runcmd_io_handler) Mar 22 11:53:17 fileserver
2016 Aug 22
1
RPC server is unavailable when using ADUC
Hello. We're running Samba 4.3.9 AD on two Ubuntu 16.04 LTS machines. I'm managing AD users and DNS from Windows 10 joined to the domain, by using ADUC. Last week I noticed the following error when starting ADUC as Administrator of the AD domain: ---- Naming information cannot be located because: The RPC server is unavailable. Contact your system administrator to verify that your domain