I get the following error when trying to connect to any AD management windows in windows server 2012. "Naming information cannot be located because: The specified domain either does not exist or could not be contacted." It is a brand new server installation and DNS has already been configured automatically by the AD installation script. Windows IP Configuration Host Name . . . . . . . . . . . . : APOLLO Primary Dns Suffix . . . . . . . : MALONE.local Node Type . . . . . . . . . . . . : Broadcast IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : MALONE.local Ethernet adapter APOLLO: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) I350 Gigabit Network Connection Physical Address. . . . . . . . . : 00-25-90-7A-14-9F DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::88fe:c048:d729:9a4b%12(Preferred) IPv4 Address. . . . . . . . . . . : 10.0.0.10(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 10.0.0.1 DHCPv6 IAID . . . . . . . . . . . : 251667856 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-18-8C-0A-CF-00-25-90-7A-14-9F DNS Servers . . . . . . . . . . . : ::1 127.0.0.1 NetBIOS over Tcpip. . . . . . . . : Enabled Directory Server Diagnosis Performing initial setup: Trying to find home server... Home Server = APOLLO * Identified AD Forest. Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name\APOLLO Starting test: Connectivity ......................... APOLLO passed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\APOLLO Starting test: Advertising Fatal Error:DsGetDcName (APOLLO) call failed, error 1355 The Locator could not find the server. ......................... APOLLO failed test Advertising Starting test: FrsEvent ......................... APOLLO passed test FrsEvent Starting test: DFSREvent There are warning or error events within the last 24 hours after the SYSVOL has been shared. Failing SYSVOL replication problems may cause Group Policy problems. ......................... APOLLO failed test DFSREvent Starting test: SysVolCheck ......................... APOLLO passed test SysVolCheck Starting test: KccEvent ......................... APOLLO passed test KccEvent Starting test: KnowsOfRoleHolders ......................... APOLLO passed test KnowsOfRoleHolders Starting test: MachineAccount ......................... APOLLO passed test MachineAccount Starting test: NCSecDesc ......................... APOLLO passed test NCSecDesc Starting test: NetLogons Unable to connect to the NETLOGON share! (\\APOLLO\netlogon) [APOLLO] An net use or LsaPolicy operation failed with error 67, The network name cannot be found.. ......................... APOLLO failed test NetLogons Starting test: ObjectsReplicated ......................... APOLLO passed test ObjectsReplicated Starting test: Replications ......................... APOLLO passed test Replications Starting test: RidManager ......................... APOLLO passed test RidManager Starting test: Services ......................... APOLLO passed test Services Starting test: SystemLog An error event occurred. EventID: 0xC00038D6 Time Generated: 01/20/2013 10:24:35 Event String: The DFS Namespace service could not initialize cross forest trust information on this domain controller, but it will periodically retry the operation. The return code is in the record data. ......................... APOLLO failed test SystemLog Starting test: VerifyReferences ......................... APOLLO passed test VerifyReferences Running partition tests on : Schema Starting test: CheckSDRefDom ......................... Schema passed test CheckSDRefDom Starting test: CrossRefValidation ......................... Schema passed test CrossRefValidation Running partition tests on : Configuration Starting test: CheckSDRefDom ......................... Configuration passed test CheckSDRefDom Starting test: CrossRefValidation ......................... Configuration passed test CrossRefValidation Running partition tests on : MALONE Starting test: CheckSDRefDom ......................... MALONE passed test CheckSDRefDom Starting test: CrossRefValidation ......................... MALONE passed test CrossRefValidation Running enterprise tests on : MALONE.local Starting test: LocatorCheck Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355 A Global Catalog Server could not be located - All GC's are down. Warning: DcGetDcName(TIME_SERVER) call failed, error 1355 A Time Server could not be located. The server holding the PDC role is down. Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error 1355 A Good Time Server could not be located. Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355 A KDC could not be located - All the KDCs are down. ......................... MALONE.local failed test LocatorCheck Starting test: Intersite ......................... MALONE.local passed test Intersite

If you're using IPv4 then you'll want 10.0.0.10 as primary and 127.0.0.1 as secondary in server's network connection properties. Also make sure client has only local DNS address (10.0.0.10) and no public dns addresses listed. Regards, Dave Patrick .... Microsoft Certified Professional Microsoft MVP [Windows] Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Hi Matthew, are you trying to connect with the management tools when you are logged on to your domain controller or from a remote computer? If you are running the remote management tools from another computer - please try to ping the domain, and domain controller if you are specifying any particular domain controller. Do you experience any domain logon failures? Please use Mark as Answer if my post solved your problem and use Vote As Helpful if a post was useful. http://www.havardkristiansen.com

Hi Matthew, are you trying to connect with the management tools when you are logged on to your domain controller or from a remote computer? If you are running the remote management tools from another computer - please try to ping the domain, and domain controller if you are specifying any particular domain controller. Do you experience any domain logon failures? Please use Mark as Answer if my post solved your problem and use Vote As Helpful if a post was useful. http://www.havardkristiansen.com Trying to connect to management tools when logged onto server using RDC (also tried locally on server) Server is not integrated into network yet as has no clients in the domain; so cannot comment about domain logon failures

If you're using IPv4 then you'll want 10.0.0.10 as primary and 127.0.0.1 as secondary in server's network connection properties. Also make sure client has only local DNS address (10.0.0.10) and no public dns addresses listed. Regards, Dave Patrick .... Microsoft Certified Professional Microsoft MVP [Windows] Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Tried this with no dice. Also ensured that NETLOGON (to script directory) is shared, still no solution...

My hair is starting to fall out, will be bald within the hour. Anyone else ever had this problem?

Few things to check. http://support.microsoft.com/kb/816042 symptom 3 http://support.microsoft.com/kb/958804 http://support.microsoft.com/kb/947022/en-us Regards, Dave Patrick .... Microsoft Certified Professional Microsoft MVP [Windows] Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Few things to check. http://support.microsoft.com/kb/816042 symptom 3 http://support.microsoft.com/kb/958804 http://support.microsoft.com/kb/947022/en-us Regards, Dave Patrick .... Microsoft Certified Professional Microsoft MVP [Windows] Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.