
close
close
Security threats keep coming! Learn how to protect your organization.
Before you start on your quest to join Windows Server 2012 to a domain, make sure that you can resolve the Active Directory (AD) domain name using DNS. Pinging the Fully Qualified Domain Name (FQDN) ensures that at least one domain controller (DC) is available to process your domain join request.
If you don’t get a reply from the ping command, check that DNS is set up correctly on the machine that you are trying to join to the domain. There should be at least one DNS entry in the network card’s IP configuration settings. You can check the network adapter’s IP address configuration by typing ipconfig /all in the command prompt, where you should see at least one DNS server address listed. If a DNS server is present in the configuration but you still can’t successfully resolve the domain’s FQDN, you will need to do some more DNS and/or network troubleshooting.
advertisment
Once the computer has rebooted, log on as a domain administrator by clicking the Switch User arrow on the logon screen and then select Other user. You can then log on to the server as a domain user. If you want to log on with a domain user that happens to have the same name as a local user, type the domain username with the domain’s FQDN suffix, such as [email protected]
More in Windows Server 2012
Most popular on petri