search for: error_dns_invalid_nam

Displaying 4 results from an estimated 4 matches for "error_dns_invalid_nam".

Did you mean: error_dns_invalid_name
2012 Mar 06
1
problem for joining the domain.
...uld help. My samba version is 3.6.3-44 on Centos 6 This is what I get [root at scan_srv2 tmp]# net ads join -U Administrator Enter Administrator's password: Using short domain name -- DOMAIN Joined 'SCAN_SRV2' to realm 'DOMAIN.com' DNS Update for scan_srv2.DOMAIN.com failed: ERROR_DNS_INVALID_NAME DNS update failed! My smb.config is workgroup = DOMAIN admin users = Administrator realm = DOMAIN.COM server string = Linux Samba File Server security = ADS encrypt passwords = yes preferred master = no template shell = /bin/false template homedir = /home/%D/%U...
2012 Mar 07
0
problem for joining the domain. - Solved
...4 on Centos 6 > > This is what I get > > [root at scan_srv2 tmp]# net ads join -U Administrator Enter > Administrator's password: > Using short domain name -- DOMAIN > Joined 'SCAN_SRV2' to realm 'DOMAIN.com' > DNS Update for scan_srv2.DOMAIN.com failed: ERROR_DNS_INVALID_NAME For DNS, underscores "_" are not a valid character in the hostname; changing to a hyphen "-" should stop that error message. Android phones are notorious for causing this error with DHCP/DNS. More info: http://networkadminkb.com/KB/a156/windows-2003-dns-and-the-underscore.a...
2017 Feb 27
2
Samba4 fail linux machine join to ADS
...'t know if is side of server or th linux's client machine and,Why?] Using short domain name -- POLRMVAR Joined 'INFORMATICA2' to dns domain 'polrmvar.mtz.sld.cu' [the machine has already joined to ADS Domaind ?????] DNS Update for informática2.polrmvar.mtz.sld.cu failed: ERROR_DNS_INVALID_NAME [I was checked the sintaxis in named config file but informatica2 DNS update failed: NT_STATUS_UNSUCCESSFUL don't have acent] T.I.A. -- Jesús Reyes Piedra Admin Red Neurodearrollo,Cárdenas La caja decía:"Requiere windows 95 o superior&...
2017 Feb 24
4
Samba firts DC fail over
Hello, I am currently testing for Samba4. The creation of the domain and the secondary Dc implementation works well. But by performing tests for a fail over situation I realized that when the DC that created the domain is in fail over the linux client machine can no longer retrieve the list of users from the domain. I would like to know if a person has already faced this situation and if so how he