Make sure that the Domain Controller is not offline or that its name is not mistyped. Try to ping the FQDN (Fully Qualified Domain Name) of the DC. For example, this problem can occur if a domain controller in the domain has not registered an "A" record for itself in DNS.
Of course, network connectivity and DNS problems could cause this problem, so check for this type of problems too.
Here are some examples when this error may occur:
- M228328 - This behavior can occur if there is no network protocol installed on the computer.
- M239897 - In this case, the computer was unable to contact a Domain Name Server (DNS) server.
- M252137 - The computer was unable to contact a global catalog server.
- M258832 - In this case, NetBIOS over TCP/IP was disabled on the client computer.
- M259374 - This problem can occur if the server that is running the Domain Name System (DNS) service has not registered an "A" record for itself in DNS.
- M279212 - The error appears if you provide an incorrect domain name when you are prompted for your credentials.
- M298656 - Domain Name System (DNS) server problems caused the error in this case.
- M299563 - This error can appear if the Netlogon service is not started.
- M312467 - This article describes a situation in which IPSec policies were configured to allow only secure communication between the Exchange 2000 server and the Global Catalog server.
- M810402 - Norton Internet Security 2002 prevented clients from joining a domain in this case.
M839880 shows information on how to troubleshoot RPC Endpoint Mapper errors.
See the links below for further information on this error.
Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net.
Obtain enhanced visibility into Cisco ASA firewall logs using the free Firegen for Cisco ASA Splunk App. Take advantage of dashboards built to optimize the threat analysis process.