I am attempting to connect to a freshly installed windows server 2012 essentials environment from a windows 10 desktop. All systems are running the latest Microsoft updates. The server is a single domain controller, and I am attempting
to connect using the domain admin account.
When I attempt to connect to the windows server, I an unable to connect error message. I've attached the following extract from the log file.
[2136] 160106.123859.7162: ClientSetup: Standard Ouptput:
[2136] 160106.123859.7162: ClientSetup: Standard Ouptput: Windows IP Configuration
[2136] 160106.123859.7162: ClientSetup: Standard Ouptput:
[2136] 160106.123859.7162: ClientSetup: Standard Ouptput: Successfully flushed the DNS Resolver Cache.
[2136] 160106.123859.7162: ClientSetup: Standard Ouptput:
[896] 160106.123859.7162: ClientSetup: Standard Error:
[800] 160106.123859.7162: ClientSetup: The exit code of the process (C:\WINDOWS\system32\ipconfig.exe) is: 0
[800] 160106.123859.7162: ClientSetup: Running Task with Id=ClientDeploy.GetStandardUsers in 2nd iteration
[800] 160106.123859.7944: ClientSetup: Could not get domain user list, exception: ErrorCatalog:NetworkError ErrorCode:-1
BaseException: Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityException: MachineIdentityManager.GetStandardUserSids ---> System.ServiceModel.FaultException: The server was unable to process the request due to an internal error. For more information about the error, either turn on IncludeExceptionDetailInFaults (either from ServiceBehaviorAttribute or from the <serviceDebug> configuration behavior) on the server in order to send the exception information back to the client, or turn on tracing as per the Microsoft .NET Framework SDK documentation and inspect the server trace logs.
Server stack trace:
at System.ServiceModel.Channels.ServiceChannel.ThrowIfFaultUnderstood(Message reply, MessageFault fault, String action, MessageVersion version, FaultConverter faultConverter)
at System.ServiceModel.Channels.ServiceChannel.HandleReply(ProxyOperationRuntime operation, ProxyRpc& rpc)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.WindowsServerSolutions.Devices.Identity.CertWebService.ICertService.GetStandardUserSids(GetStandardUserSidsRequest request)
at Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.<>c__DisplayClass41.<GetStandardUserSids>b__40(CertServiceClient client)
at Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.InvokeCertServiceClient(String serverName, Func`2 func)
--- End of inner exception stack trace ---
at Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.InvokeCertServiceClient(String serverName, Func`2 func)
at Microsoft.WindowsServerSolutions.Devices.Identity.MachineIdentityManager.GetStandardUserSids(String serverName, String userName, String password)
at Microsoft.WindowsServerSolutions.ClientSetup.ClientDeploy.GetStandardUsersTask.Run(WizData data)
[800] 160106.123859.7944: ClientSetup: ProcessHelper.StartProcessWithRedirectOutput() Executing "C:\WINDOWS\system32\ipconfig.exe" /all
[896] 160106.123859.8256: ClientSetup: Standard Ouptput:
[896] 160106.123859.8256: ClientSetup: Standard Ouptput: Windows IP Configuration
[896] 160106.123859.8256: ClientSetup: Standard Ouptput:
I have worked through the various help pages which includes references to inconsistencies in the certificates as a possible cause of this problem, but re-issuing the certificate on the server and performing an IISRESET does not fix the issue.
There is a secondary issue which I think is unconnected, but may be related. When I run DCDIAG on the server I get the following error message:
Testing server: Default-First-Site-Name\xxxxxx
Starting test: Connectivity
The host 65ea9dbe-a481-4e83-b00d-8f7ceab7254f._msdcs.xxxx.local could
not be resolved to an IP address. Check the DNS server, DHCP, server
name, etc.
Got error while checking LDAP and RPC connectivity. Please check your
firewall settings.
......................... xxxxxxx failed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\xxxxxxxx
Skipping all tests, because server xxxxxxxx is not responding to
directory service requests.Again searching with google, I have been able to locate the cause of this error message as the RPC service is running. Does anyone have a step-by-step set of instructions to check/fix the above problem as I'm not sure what I should be looking for when
checking any firewall settings?