similar to: Issue with Linux & Windows clients domain join - Error: NT_STATUS_CANT_ACCESS_DOMAIN_INFO

Displaying 20 results from an estimated 30000 matches similar to: "Issue with Linux & Windows clients domain join - Error: NT_STATUS_CANT_ACCESS_DOMAIN_INFO"

2011 Jul 04
1
Domain join problem
Hi I am having a problem joining a domain, please assist here is my smb.conf file: [global] workgroup = CORP realm = CORP.GO2UTI.COM preferred master = no server string = Samba Server security = ADS username map = /etc/samba/smbusers log file = /var/samba/log/log.%m max log size = 50 dns proxy = No password server =
2004 Sep 03
0
Can't join Domain on PDC: NT_STATUS_CANT_ACCESS_DOMAIN_INFO (PAM: 4)
Hi all, I've got the following problem when trying to join a domain on a samba pdc itself: net rpc join eccag -U root asks for password an then tells me that it cannot connect to the PDC. Winbind-log gives the following: [2004/08/31 02:29:15, 0] nsswitch/winbindd_util.c:get_trust_pw(1024) get_trust_pw: could not fetch trust account password for my domain ECCAG [2004/08/31 02:29:15, 2]
2020 Feb 08
1
Samba 4.11.6 cannot JOIN - 'Could not find machine account'
Thanks for the help with this, Rowland. > Where these 2008 DCs upgraded from an earlier version ? (2000, 2003) Yes, the two Windows servers were migrated over the years to Server 2008 (one is 2008 R2). I've now moved the _msdcs folder and made it a zone in the forest, restarted NETLOGON, and set the functionality of the forest to Server 2008, then rebooted both windows servers. This
2020 Feb 08
0
Samba 4.11.6 cannot JOIN - 'Could not find machine account'
A small update... I was able to remove the "Cannot reach a KDC" errors by disabling Apparmor. However, the original WERR_DNS_ERROR_RCODE_NAME_ERROR error remains and is now the first error in the log. > Thanks for the help with this, Rowland. > > > Where these 2008 DCs upgraded from an earlier version ? (2000, 2003) > > Yes, the two Windows servers were migrated
2006 Aug 16
0
connect_to_domain_password_server: unable to open the domain client session to machine SJMEMDC40. Error was : NT_STATUS_CANT_ACCESS_DOMAIN_INFO
Good afternoon. I cannot seem to get my test samba (domain member) server to use a windows 2003 PDC, SJMEMDC40. Are there any outstanding issues with a win2003 PDC and a samba domain member server? Her are my errors: [2006/08/16 16:40:46, 0] rpc_client/cli_pipe.c:get_schannel_session_key(2443) get_schannel_session_key: could not fetch trust account password for domain 'CBT'
2009 Nov 19
0
Linux & Windows clients domain join - Error: NT_STATUS_CANT_ACCESS_DOMAIN_INFO
Sorry, I'll try this again. It appears the email got stripped out and left the attachment. ------------------------ I'm having an issue where any machine refuses to join the domain. It's a a Debian server(lenny) with an LDAP backend. I assume the issue is something obvious, but this is an "inherited" network and based on the state of the rest of it, the issue could be
2006 Feb 08
1
New trick for old dogs
We have been using Samba for many years. The company has just switched from an NT domain to an Active Directory domain. The new server is running Windows Server 2003. We are having trouble configuring our Solaris 8 server so it can join the domain as a server. Just getting Samba to compile and link was interesting enough. This included downloading and compiling a new version of the BerkeleyDB,
2002 Jun 07
0
winbindd + wbinfo -> NT_STATUS_CANT_ACCESS_DOMAIN_INFO
I still can't get winbindd working properly even though I am making some progress here. I retrieved the latest CVS version last night and now I can finally use non-anonymous connections - that works very well. I *did* update both of the pam modules in /lib and /lib/security winbindd runs under the account of a regular domain user "wbinfo -u" shows me all users and "getent
2013 Jul 30
1
samba4 - classicupgrade - problem - passdb.error uncaught exception - Cannot load backend methods for 'ldapsam:ldap://localhost' backend NT_STATUS_CANT_ACCESS_DOMAIN_INFO
Even after cleaning etc and private directories im still getting the same error: Provisioning convert_string_talloc: Conversion not supported.*pdb_init_ldapsam: WARNING: Could not get domain info, nor add one to the domain. We cannot work reliably without it.* pdb backend ldapsam:ldap://localhost did not correctly init (error was NT_STATUS_CANT_ACCESS_DOMAIN_INFO) ERROR(<class
2011 Nov 24
0
NT_STATUS_CANT_ACCESS_DOMAIN_INFO
Hi Folks, I'm having an issue with Samba on one of my Linux servers. I've configured a share but I'm not able to access it. From the Samba log file, I can see the error line I pasted below. I will really appreciate your help to figure out the culprit. Thanks, Patrick *[2011/11/24 12:56:48, 0] auth/auth_domain.c:connect_to_domain_password_server(119)
2019 May 02
0
Possibly WERR_DS_DRA_ACCESS_DENIED or NT_STATUS_CANT_ACCESS_DOMAIN_INFO
On Thu, 2 May 2019 14:44:18 -0400 James Fowler <fowlerj at adst.org> wrote: > I have read that so many times. I started out with the simple, > prompted 'samba-tool domain join' and built up from there. > > Version is: > Samba 4.7.6 from Ubuntu (18.04.2) > > Interesting what happens when I take out --site directive (see below). > > root at DC2:~#
2019 May 02
0
Possibly WERR_DS_DRA_ACCESS_DENIED or NT_STATUS_CANT_ACCESS_DOMAIN_INFO
On Thu, 2 May 2019 11:56:30 -0400 James Fowler via samba <samba at lists.samba.org> wrote: > So we have two different Samba servers we are trying to connect to > what was originally a Windows 2003 AD and was raised to 2008R2 (both > Forest and Domain). > (We really only need to connect one of them - the one hosting Samba > 4.7.6). > > Any ideas or suggestions are
2019 May 06
0
Possibly WERR_DS_DRA_ACCESS_DENIED or NT_STATUS_CANT_ACCESS_DOMAIN_INFO
On Mon, 6 May 2019 09:32:45 -0400 James Fowler <fowlerj at adst.org> wrote: > Inline reply. > > > > > There is also that word 'Zentyal', was/is this computer a > > > > Zentyal DC ? > > > Yes. > > > > Which, is it a DC, or was it a DC > > > It has never been a DC. I even wiped the machine (again) at one > point
2019 May 06
0
Possibly WERR_DS_DRA_ACCESS_DENIED or NT_STATUS_CANT_ACCESS_DOMAIN_INFO
On Mon, 6 May 2019 10:39:05 -0400 James Fowler <fowlerj at adst.org> wrote: > Inline. > > On Mon, May 6, 2019 at 9:58 AM Rowland Penny via samba < > samba at lists.samba.org> wrote: > > > On Mon, 6 May 2019 09:32:45 -0400 > > James Fowler <fowlerj at adst.org> wrote: > > > > > Inline reply. > > > > > > > >
2019 May 03
0
Possibly WERR_DS_DRA_ACCESS_DENIED or NT_STATUS_CANT_ACCESS_DOMAIN_INFO
On Thu, 2 May 2019 16:51:02 -0400 James Fowler <fowlerj at adst.org> wrote: See inline comments > root at DC2:~# cat /etc/resolv.conf > # Dynamic resolv.conf(5) file for glibc resolver(3) generated by > resolvconf(8) > # and managed by Zentyal. > # > # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE > OVERWRITTEN # > nameserver 192.168.1.254 > #search
2008 Sep 24
1
Share name and file rights
A question about share names: When we open a samba share, I want the symbol on my desktop to have the name "johndoe@sambaserver1", not just "johndoe". This is because we have a number of different "sambaservers" that johndoe can log on to, and it will be a mess on his desktop if he uses several connections at the same time. i cannot find this feature in the
2019 May 06
2
Possibly WERR_DS_DRA_ACCESS_DENIED or NT_STATUS_CANT_ACCESS_DOMAIN_INFO
All, but once, I've used it as second DC in conjunction with a Windows AD server, joining it to an existing domain. Granted, this is the first time I've used it with a 2008R2 AD domain and forest level. Before I spent anyone else's time on this, I wiped it completely (down to new disk labels) and still run into this error. It is good to know that it should be working. If anyone
2019 May 06
0
Possibly WERR_DS_DRA_ACCESS_DENIED or NT_STATUS_CANT_ACCESS_DOMAIN_INFO
On Mon, 6 May 2019 07:06:42 -0400 James Fowler <fowlerj at adst.org> wrote: > Inline reply. > > On Fri, May 3, 2019 at 3:08 AM Rowland Penny via samba < > samba at lists.samba.org> wrote: > > > On Thu, 2 May 2019 16:51:02 -0400 > > James Fowler <fowlerj at adst.org> wrote: > > > > See inline comments > > > > > root at
2013 Feb 04
1
samba4 - classicupgrade - problem - passdb.error uncaught exception - Cannot load backend methods for 'ldapsam:ldap://localhost' backend NT_STATUS_CANT_ACCESS_DOMAIN_INFO
Hello, I'm migrating to samba4 (samba 4.0.2 in Debian 6.0.6) After copying .tdb files and smb.conf and migrating ldap server to the new server and configured it. When I run: /usr/loca/samba/bin/samba-tool domain classicpugrade --dbdir=samba --user-xattrs=yes --realm=sadom.espel.com samba/smb.conf I get: Reading smb.conf WARNING: The "idmap backend" option is deprecated WARNING:
2019 May 06
2
Possibly WERR_DS_DRA_ACCESS_DENIED or NT_STATUS_CANT_ACCESS_DOMAIN_INFO
Inline. On Mon, May 6, 2019 at 9:58 AM Rowland Penny via samba < samba at lists.samba.org> wrote: > On Mon, 6 May 2019 09:32:45 -0400 > James Fowler <fowlerj at adst.org> wrote: > > > Inline reply. > > > > > > > There is also that word 'Zentyal', was/is this computer a > > > > > Zentyal DC ? > > > > Yes. >