Nic Robertson
asked on
Member server attempting to join a Windows Domain issue
Issue joining a domain
I am having the following problem adding a fileserver to a domain.
Background: Server is a member server, able to see the DC via nslookup, and ping it. Firewall is also disabled on member server, and I have correct permissions to add server to domain (unfortunately, I do not have the rights to log into the DC itself).
Here is the Netsetup logs:
12/24/2019 18:29:37:218 NetpDoDomainJoin
12/24/2019 18:29:37:218 NetpDoDomainJoin: using current computer names
12/24/2019 18:29:37:218 NetpDoDomainJoin: NetpGetComputerNameEx(NetB ios) returned 0x0
12/24/2019 18:29:37:218 NetpDoDomainJoin: NetpGetComputerNameEx(DnsH ostName) returned 0x0
12/24/2019 18:29:37:218 NetpMachineValidToJoin: 'Servername'
12/24/2019 18:29:37:218 NetpMachineValidToJoin: status: 0x0
12/24/2019 18:29:37:218 NetpJoinDomain
12/24/2019 18:29:37:218 HostName: Servername
12/24/2019 18:29:37:218 NetbiosName: Servername
12/24/2019 18:29:37:218 Domain: xxx.yyy.zzz.com
12/24/2019 18:29:37:218 MachineAccountOU: (NULL)
12/24/2019 18:29:37:218 Account: @@BR7fmEJmblZSrrdbzB8sjUn2 36WJ
12/24/2019 18:29:37:218 Options: 0x27
12/24/2019 18:29:37:218 NetpValidateName: checking to see if 'xxx.yyy.zzz.com' is valid as type 3 name
12/24/2019 18:29:37:218 NetpValidateName: 'xxx.yyy.zzz.com' is not a valid NetBIOS domain name: 0x7b
12/24/2019 18:29:37:812 NetpCheckDomainNameIsValid [ Exists ] for 'xxx.yyy.zzz.com' returned 0x0
12/24/2019 18:29:37:812 NetpValidateName: name 'xxx.yyy.zzz.com' is valid for type 3
12/24/2019 18:29:37:812 NetpDsGetDcName: trying to find DC in domain 'xxx.yyy.zzz.com', flags: 0x40001010
12/24/2019 18:29:37:874 NetpDsGetDcName: status of verifying DNS A record name resolution for 'DC-Server.xxx.yyy.zzz.com ': 0x0
12/24/2019 18:29:37:874 NetpDsGetDcName: found DC '\\DC-Server.xxx.yyy.zzz.c om' in the specified domain
12/24/2019 18:29:37:874 NetpJoinDomainOnDs: NetpDsGetDcName returned: 0x0
12/24/2019 18:29:37:874 NetpDisableIDNEncoding: using FQDN xxx.yyy.zzz.com from dcinfo
12/24/2019 18:29:37:874 NetpDisableIDNEncoding: DnsDisableIdnEncoding(UNTI LREBOOT) on 'xxx.yyy.zzz.com' succeeded
12/24/2019 18:29:37:874 NetpJoinDomainOnDs: NetpDisableIDNEncoding returned: 0x0
12/24/2019 18:29:39:093 NetUseAdd to \\DC-Server.xxx.yyy.zzz.co m\IPC$ returned 1311
12/24/2019 18:29:39:093 NetpJoinDomainOnDs: status of connecting to dc '\\DC-Server.xxx.yyy.zzz.c om': 0x51f
12/24/2019 18:29:39:093 NetpJoinDomainOnDs: Function exits with status of: 0x51f
12/24/2019 18:29:39:093 NetpResetIDNEncoding: DnsDisableIdnEncoding(RESE TALL) on 'xxx.yyy.zzz.com' returned 0x0
12/24/2019 18:29:39:093 NetpJoinDomainOnDs: NetpResetIDNEncoding on 'xxx.yyy.zzz.com': 0x0
12/24/2019 18:29:39:093 NetpDoDomainJoin: status: 0x51f
Ethernet adapter Ethernet0:
Connection-specific DNS Suffix . : xxx.yyy.zzz.com
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : 00-0G-29-23-6D-15
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.8.64.12(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Lease Obtained. . . . . . . . . . : Thursday, December 26, 2019 10:15:37 AM
Lease Expires . . . . . . . . . . : Sunday, December 29, 2019 10:28:16 AM
Default Gateway . . . . . . . . . : 10.8.64.1
DHCP Server . . . . . . . . . . . : 10.8.241.125
DNS Servers . . . . . . . . . . . : 10.8.241.123
10.8.241.124
10.8.241.122
11.15.68.43
Primary WINS Server . . . . . . . : 10.8.241.122
Secondary WINS Server . . . . . . : 10.8.51.123
NetBIOS over Tcpip. . . . . . . . : Enabled
C:\Users\admin>nslookup
Default Server: DC-Server.xxx.yyy.zzz.com
Address: 10.8.241.123
Furthermore - I looked up the error in the logs and I see this displayed below:
No domain controller found. ERROR_NO_LOGON_SERVERS. 1311
it doesn't make sense to me since in my "ipconfig /all" , the server can talk to the DC with the DHCP address given.
Any ideas? Thanks in advance!
I am having the following problem adding a fileserver to a domain.
Background: Server is a member server, able to see the DC via nslookup, and ping it. Firewall is also disabled on member server, and I have correct permissions to add server to domain (unfortunately, I do not have the rights to log into the DC itself).
Here is the Netsetup logs:
12/24/2019 18:29:37:218 NetpDoDomainJoin
12/24/2019 18:29:37:218 NetpDoDomainJoin: using current computer names
12/24/2019 18:29:37:218 NetpDoDomainJoin: NetpGetComputerNameEx(NetB
12/24/2019 18:29:37:218 NetpDoDomainJoin: NetpGetComputerNameEx(DnsH
12/24/2019 18:29:37:218 NetpMachineValidToJoin: 'Servername'
12/24/2019 18:29:37:218 NetpMachineValidToJoin: status: 0x0
12/24/2019 18:29:37:218 NetpJoinDomain
12/24/2019 18:29:37:218 HostName: Servername
12/24/2019 18:29:37:218 NetbiosName: Servername
12/24/2019 18:29:37:218 Domain: xxx.yyy.zzz.com
12/24/2019 18:29:37:218 MachineAccountOU: (NULL)
12/24/2019 18:29:37:218 Account: @@BR7fmEJmblZSrrdbzB8sjUn2
12/24/2019 18:29:37:218 Options: 0x27
12/24/2019 18:29:37:218 NetpValidateName: checking to see if 'xxx.yyy.zzz.com' is valid as type 3 name
12/24/2019 18:29:37:218 NetpValidateName: 'xxx.yyy.zzz.com' is not a valid NetBIOS domain name: 0x7b
12/24/2019 18:29:37:812 NetpCheckDomainNameIsValid
12/24/2019 18:29:37:812 NetpValidateName: name 'xxx.yyy.zzz.com' is valid for type 3
12/24/2019 18:29:37:812 NetpDsGetDcName: trying to find DC in domain 'xxx.yyy.zzz.com', flags: 0x40001010
12/24/2019 18:29:37:874 NetpDsGetDcName: status of verifying DNS A record name resolution for 'DC-Server.xxx.yyy.zzz.com
12/24/2019 18:29:37:874 NetpDsGetDcName: found DC '\\DC-Server.xxx.yyy.zzz.c
12/24/2019 18:29:37:874 NetpJoinDomainOnDs: NetpDsGetDcName returned: 0x0
12/24/2019 18:29:37:874 NetpDisableIDNEncoding: using FQDN xxx.yyy.zzz.com from dcinfo
12/24/2019 18:29:37:874 NetpDisableIDNEncoding: DnsDisableIdnEncoding(UNTI
12/24/2019 18:29:37:874 NetpJoinDomainOnDs: NetpDisableIDNEncoding returned: 0x0
12/24/2019 18:29:39:093 NetUseAdd to \\DC-Server.xxx.yyy.zzz.co
12/24/2019 18:29:39:093 NetpJoinDomainOnDs: status of connecting to dc '\\DC-Server.xxx.yyy.zzz.c
12/24/2019 18:29:39:093 NetpJoinDomainOnDs: Function exits with status of: 0x51f
12/24/2019 18:29:39:093 NetpResetIDNEncoding: DnsDisableIdnEncoding(RESE
12/24/2019 18:29:39:093 NetpJoinDomainOnDs: NetpResetIDNEncoding on 'xxx.yyy.zzz.com': 0x0
12/24/2019 18:29:39:093 NetpDoDomainJoin: status: 0x51f
Ethernet adapter Ethernet0:
Connection-specific DNS Suffix . : xxx.yyy.zzz.com
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection
Physical Address. . . . . . . . . : 00-0G-29-23-6D-15
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 10.8.64.12(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.252.0
Lease Obtained. . . . . . . . . . : Thursday, December 26, 2019 10:15:37 AM
Lease Expires . . . . . . . . . . : Sunday, December 29, 2019 10:28:16 AM
Default Gateway . . . . . . . . . : 10.8.64.1
DHCP Server . . . . . . . . . . . : 10.8.241.125
DNS Servers . . . . . . . . . . . : 10.8.241.123
10.8.241.124
10.8.241.122
11.15.68.43
Primary WINS Server . . . . . . . : 10.8.241.122
Secondary WINS Server . . . . . . : 10.8.51.123
NetBIOS over Tcpip. . . . . . . . : Enabled
C:\Users\admin>nslookup
Default Server: DC-Server.xxx.yyy.zzz.com
Address: 10.8.241.123
Furthermore - I looked up the error in the logs and I see this displayed below:
No domain controller found. ERROR_NO_LOGON_SERVERS. 1311
it doesn't make sense to me since in my "ipconfig /all" , the server can talk to the DC with the DHCP address given.
Any ideas? Thanks in advance!
Hi,
The idea of a file server with DHCP instead of static IP is a little strange but let's pass it.
What is the output of nltest /sc_reset:DOMAIN?
What is the version of Windows file server and DC?
Dimitris
The idea of a file server with DHCP instead of static IP is a little strange but let's pass it.
What is the output of nltest /sc_reset:DOMAIN?
What is the version of Windows file server and DC?
Dimitris
ASKER
Hi Darrell,
Ip for the server is assigned statically through the DHCP reservation.
Nslookup, shows the same as above question:
C:\Users\admin>nslookup
Default Server: DC-Server.xxx.yyy.zzz.com
Address: 10.8.241.123
Name: XXX.YYY.ZZZ.COM
It pulls over 20+ results, including the server listed above: 10.8.241.123
Ip for the server is assigned statically through the DHCP reservation.
Nslookup, shows the same as above question:
C:\Users\admin>nslookup
Default Server: DC-Server.xxx.yyy.zzz.com
Address: 10.8.241.123
Name: XXX.YYY.ZZZ.COM
It pulls over 20+ results, including the server listed above: 10.8.241.123
ASKER
Hi Dimitris-
Windows File (Server 2016), and I believe the DC is also 2016 with AD functions.
NLTtest results:
C:\Users\admin>nltest /sc_reset:xxx.yyy.zzz.com
I_NetLogonControl failed: Status = 1722 0x6ba RPC_S_SERVER_UNAVAILABLE
Windows File (Server 2016), and I believe the DC is also 2016 with AD functions.
NLTtest results:
C:\Users\admin>nltest /sc_reset:xxx.yyy.zzz.com
I_NetLogonControl failed: Status = 1722 0x6ba RPC_S_SERVER_UNAVAILABLE
Nic,
Can you check the time of both DC and file server?
The false ssems to be something with the RPC service or DNS. Most probably to fix it you must have access to DC.
Dimitris
Can you check the time of both DC and file server?
The false ssems to be something with the RPC service or DNS. Most probably to fix it you must have access to DC.
Dimitris
ASKER
Dimitris,
I can't access the DC due to permissions, but time appears the same within one minute. Fileshare for sure is good to go on time.
Now I am unsure if this helps, I am doing a server upgrade to an existing server.
Server was 2008r2 originally but is now upgraded to 2016, and is rejoining the same domain with the same IP and computer name.
I can't access the DC due to permissions, but time appears the same within one minute. Fileshare for sure is good to go on time.
Now I am unsure if this helps, I am doing a server upgrade to an existing server.
Server was 2008r2 originally but is now upgraded to 2016, and is rejoining the same domain with the same IP and computer name.
Nic,
If it is not working after the upgrade, I would make a reboot in DC. If in this case si not working, you have to login to DC in order to debug it.
No other way to solve it.
If it is not working after the upgrade, I would make a reboot in DC. If in this case si not working, you have to login to DC in order to debug it.
No other way to solve it.
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Can you resolve the domain from the server using NSLookup? Does it resolve to the correct (Domain Controller) IP address? If so, is it the local DC?