search for: getdcname

I'm wondering what the difference is between the two wbinfo functions, "getdcname" and "DSgetdcname". The help is not very helpful here: --dsgetdcname /|domain|/ Find a DC for a domain. --getdcname /|domain|/ Get the DC name for the specified domain. I have a Samba4 PDC that is returning different results for these depending upon whether it's run...

Should I expect to see when I run wbinfo --getdcname=domain it return a domain controller for an ad server? It does return a server name for domain_network, the non-ad server. David Shapiro Unix Team Lead 919-765-2011 >>> David Shapiro 2/3/2006 10:50:51 AM >>> I am trying to get a aix samba server to join an ads domain. I thi...

Hello Kris, On 03/02/2020 07:15, Kris Lou via samba wrote: > Unless it's_not_ a global catalog. Check your SRV records again, there > should be corresponding "_gc" records (similar to "_ldap") for each DC. Checked and both DCs pass all tests:- host -t SRV _ldap._tcp.mydomain.com. host -t SRV _gc._tcp.mydomain.com. host -t SRV _kerberos._udp.mydomain.com. host -t

...2020 18:49, Kris Lou via samba wrote: > > From windows: > echo %logonserver% \\DC3 > nltest /dsgetdc:<domain> DC:\\DC3 Address: \\192.168.0.218 Dom Guid: bla bla bla ... The command completed successfully. > From a *nix domain member (i.e. client, not DC): > wbinfo --getdcname=<domain> > winbind --ping-dc wbinfo --getdcname=MYDOMAIN DC3 wbinfo --ping-dc checking the NETLOGON for domain[mydomain] dc connection to "dc3.mydomain.com" succeeded > That's probably expected. I don't think nslookup can query multiple DNS > servers at once....

...cho %logonserver% > > \\DC3 > > > > nltest /dsgetdc:<domain> > > DC:\\DC3 > Address: \\192.168.0.218 > Dom Guid: bla bla bla > ... > The command completed successfully. > > > > From a *nix domain member (i.e. client, not DC): > > wbinfo --getdcname=<domain> > > winbind --ping-dc > > wbinfo --getdcname=MYDOMAIN > DC3 > > wbinfo --ping-dc > checking the NETLOGON for domain[mydomain] dc connection to " > dc3.mydomain.com" succeeded > > > > That's probably expected. I don't think nsl...

...nd 2 BDC addresses through WINS. Fri May 12 09:56:55 EDT [auth.dc.trace.DCConnection.statusMsg:info]: AUTH: TraceDC- Found 2 PDC addresses through WINS. found PDC TRILLIAN at aaa.bbb.ccc.241 Not able to communicate with PDC 192.168.254.254 trying 192.168.254.254...Fri May 12 09:57:07 EDT [auth.dc.GetDCName.failed:error]: AUTH: Error 0x0 while trying to get Domain Controller name for 192.168.254.254: Timed out waiting for reply. ... I'd expect it to find only aaa.bbb.ccc.241 - Any idea what am I missing here? The PDC is also the WINS server, in case that matters. Thanks, -- Roy McMorran Sy...

...true krb4_convert = false proxiable = false #minimum_uid = 1 #external = sshd #use_shmem = sshd } # wbinfo --own-domain MYDOMAIN # wbinfo -t checking the trust secret via RPC calls succeeded wbinfo -g shows the Groups of MYDOMAIN wbinfo -u shows the Users of MYDOMAIN # wbinfo --getdcname=MYDOMAIN Could not get dc name for domainname Now Firewall is active: # iptables --list Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target pr...

...init -V Administrator at WGNAME.AD.MYCORP.COM<mailto:Administrator at WGNAME.AD.MYCORP.COM> returns: Authenticated to Kerberos v5 And klist commands show tickets with today's date. We are running CentOS 7, samba-4.10.16-20.el7_9.x86_64 wbinfo -t/-u/-g runs successfully as does wbinfo --getdcname MYCORP No problems so far other than "net ads join" fails, have to use "realm join" instead which messes up smb.conf smb.conf [global] kerberos method = system keytab log level = 3 max log size = 5000 log file = /var/log/samba/log.%h.%m template homedir = /home/%U@%D template...

...s with today's date. We are running CentOS 7, samba-4.10.16-20.el7_9.x86_64 That is a very old version of Smba. Agreed! Downloading and making a newer version is on my to-do list. Need to thoroughly test all dependencies. > > wbinfo -t/-u/-g runs successfully as does wbinfo --getdcname MYCORP That does surprise me. Me too, but I don't argue with success. (BTW those wbinfo commands start to fail along with Samba a few days after joining AD on our CentOS 6 servers. Not going to trouble you with that here, other than to ask what version of Samba 4 would you recommend w...

...alone server. The Debian 4 box showed the same problem as the NAS while the Debian 5 box worked as expected. (In both cases the PDC was the newly upgraded box running Samba 3.2.5.) Everything I've tried seems to indicate that things are properly configured--with the exception of "wbinfo --getdcname HQ" which returns "Could not get dc name for HQ" and "wbinfo -a ..." which also fails. Those two things are probably related--but as you can see below all other wbinfo commands work correctly. Is this a known issue that I missed? Any thoughts on where to look further? Tha...

...--domain=CORE > --target-hostname=open-ldap2.core.mydomain.hu > NT_STATUS_WRONG_PASSWORD: Wrong Password (0xc000006a) > > so, looks like it works. > > # net ads status > > gives a very long output. > > And wbinfo gives only open-ldap as DC: > > # wbinfo --dsgetdcname=CORE > open-ldap.core.mydomain.hu > \\10.10.20.202 > 1 > 37241698-63dd-40d5-805b-d83f4a35223a > core.mydomain.hu > core.mydomain.hu > 0xe00013fd > Default-First-Site-Name > Default-First-Site-Name > > # wbinfo --getdcname=CORE > OPEN-LDAP > > # wbinfo -a...

...ession key for Bliss? I even tried changing the trustpassword to see if that would reset the the schannel key. It failed due to an inability to get the schannel session key. Also, maybe it's unimportant, but with winbind running, I tried to fetch the DC name for my domain with "wbinfo --getdcname 'Bliss'", but it returned "Could not get dc name for Bliss". Should this work with samba 3.4.3 ? The Windows client goes from getting 'Domain name can't be found" to "Access Denied" depending on combinations of the Sign/Seal level of security and NTLM/...

...a) # ntlm_auth --username=abc_airween --password=WRONGPASS # --domain=CORE --target-hostname=open-ldap2.core.mydomain.hu NT_STATUS_WRONG_PASSWORD: Wrong Password (0xc000006a) so, looks like it works. # net ads status gives a very long output. And wbinfo gives only open-ldap as DC: # wbinfo --dsgetdcname=CORE open-ldap.core.mydomain.hu \\10.10.20.202 1 37241698-63dd-40d5-805b-d83f4a35223a core.mydomain.hu core.mydomain.hu 0xe00013fd Default-First-Site-Name Default-First-Site-Name # wbinfo --getdcname=CORE OPEN-LDAP # wbinfo -a abc_airween%GOODPASS plaintext password authentication failed Could no...

...ng to winbindd succeeded # wbinfo --all-domains BUILTIN BLISS # wbinfo --own-domain BLISS # wbinfo --trusted-domains BUILTIN BLISS # wbinfo --online-status BLISS BUILTIN : online BLISS : online # wbinfo -P checking the NETLOGON dc connection succeeded # wbinfo --getdcname BLISS Could not get dc name for BLISS ^^^^^ ^ --This is the first indication of a problem....also when I try wbinfo --dsgetdcname.... it just goes off and thinks about it. (don't know if it ever would come back...waited about 30 seconds, but gave up) I can map a uid to a sid: #...

I am trying to get two Samba PDC/Domains setup with a trust between them. They are separate domains because they are separate companies (one is a subsidiary of the other) located in different cites. I am using Centos 5.1 x86_64 and Samba 3.0.28a packages built by me from Fedora 8 source RPMs. Based on what I have read, in order to do the trust thing I need to use Winbind/idmap to handle the non

It appears that you cannot include groups from trusted domains in the 'valid users =' directive on a share. Here is the scenario as I experienced it (names have been changed to protect the innocent): Configuration: - Samba 3.0.21b as a member server in a real NT4 domain (security = domain) called 'NTDOMAIN' - NTDOMAIN has a two-way trust with Windows 2003 Active Directory

...ended for human and machine audiences, respectively. The 'samba-tool visualize uptodateness' visualizes replication lag as a heat-map matrix based on the DRS uptodateness vectors. This will show you if (but not why) changes are failing to replicate to some DCs. Automatic site coverage and GetDCName improvements -------------------------------------------------- Samba's AD DC now automatically claims otherwise empty sites based on which DC is the nearest in the replication topology. This, combined with efforts to correctly identify the client side in the GetDCName Netlogon call will impr...

...ended for human and machine audiences, respectively. The 'samba-tool visualize uptodateness' visualizes replication lag as a heat-map matrix based on the DRS uptodateness vectors. This will show you if (but not why) changes are failing to replicate to some DCs. Automatic site coverage and GetDCName improvements -------------------------------------------------- Samba's AD DC now automatically claims otherwise empty sites based on which DC is the nearest in the replication topology. This, combined with efforts to correctly identify the client side in the GetDCName Netlogon call will impr...

...ended for human and machine audiences, respectively. The 'samba-tool visualize uptodateness' visualizes replication lag as a heat-map matrix based on the DRS uptodateness vectors. This will show you if (but not why) changes are failing to replicate to some DCs. Automatic site coverage and GetDCName improvements -------------------------------------------------- Samba's AD DC now automatically claims otherwise empty sites based on which DC is the nearest in the replication topology. This, combined with efforts to correctly identify the client side in the GetDCName Netlogon call will impr...

...ended for human and machine audiences, respectively. The 'samba-tool visualize uptodateness' visualizes replication lag as a heat-map matrix based on the DRS uptodateness vectors. This will show you if (but not why) changes are failing to replicate to some DCs. Automatic site coverage and GetDCName improvements -------------------------------------------------- Samba's AD DC now automatically claims otherwise empty sites based on which DC is the nearest in the replication topology. This, combined with efforts to correctly identify the client side in the GetDCName Netlogon call will impr...