The name will remain ".".The specified server cannot perform the operation. The following articles contain port requirement information: 832017 Service overview and network port requirements for Windows 179442 How to configure a firewall for domains and trusts Error 10Ĭhanging the Primary Domain DNS name of this computer to "" failed. For more information, see Event ID 16650: The account-identifier allocator failed to initialize in Windows Server. Make sure that the DC that hosts the relative ID (RID) operations master is online and functional. The directory service has exhausted the pool of relative identifiers. Disable the TCP Chimney offload feature and IP offloading. Verify connectivity between the client that is being joined and the target DC over the required ports and protocols. Make sure that you have the most up-to-date drivers installed for the client computer's network adapter. When you type the domain name, make sure that you type the DNS name and not the NetBIOS name. The format of the specified network name is invalid. You may want to restart the DC if the issue persists. If the issue persists, verify the status of the DC that the client is connecting to (active connections, network connectivity, and so on). Resolutionīefore joining the computer to the domain, make sure that you have cleared all mapped connections to any drives. No more connections can be made to this remote computer at this time because there are already as many connections as the computer can accept. To verify this, you can run one of the following commands: nltest /dsgetdc: /forceĪdditionally, you can update the network adapter driver. Make sure that the correct DNS server has been configured on this client as the preferred DNS, and that the client has connectivity to that server. Verify that the computer can reach a DNS server that hosts the DNS zone of the target domain or can resolve DNS names in that domain. Restart the computer that you are trying to join to the domain to make sure that there are no latent connections to any of the domain servers. Disconnect all previous connections to the server or shared resource and try again. Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. ResolutionĪdditionally, restart the computer before you try to join the computer to the domain. When you type the domain name, make sure that you type the DNS name and not the NetBIOS name.Īn operation was attempted on a nonexistent network connection. Please verify this client is configured to reach a DNS server that can resolve DNS names in the target Domain. To verify this, you can run one of the following commands: nltest /dsgetdc: /forceĪn attempt to resolve the DNS name of a domain controller in the domain being joined has failed. Make sure that the correct DNS server is configured on this client as the preferred DNS, and that the client has connectivity to that server. For example, if the DNS name of the target domain is, make sure that you enter instead of the NetBIOS domain name of "contoso."Īdditionally, verify that the computer can reach a DNS server that hosts the DNS zone of the target domain or can resolve DNS names in that domain. When you type the domain name, make sure that you type the Domain Name System (DNS) name and not the Network Basic Input/Output System (NetBIOS) name. Please verify this client is configured to reach a DNS server that can resolve DNS names in the target domain. Networking error messages and resolutions Error 1Īn attempt to resolve the DNS name of a DC in the domain being joined has failed. Windows clients log the details of domain join operations in the %windir%\debug\Netsetup.log file. This article also provides troubleshooting suggestions for these errors.Īpplies to: Windows Server 2016, Windows Server 2012 R2 Original KB number: 4341920 Where to find the Netsetup.log file This article describes several common error messages that can occur when you join client computers that are running Windows to a domain.
0 Comments
Leave a Reply. |