Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, January 11, 2016 11:15 PM
I have a stand-alone Windows Server 2012 R2 where I believe the DNS environment has become corrupted in so far I have the following problems:
DCDIAG is unable to communicate with any of the forwarded DNS IP addresses defined in the network adapter reporting that each of the DNS IP addresses used by the sites broadband router are invalid as well as the broadband router itself. [I'm not sure if the server should be configured to use the broadband router as the forwardDNS, or the IP addresses used by the broadband router.]
C:\Windows\system32>dcdiag /test:dns Directory Server Diagnosis Performing initial setup: Trying to find home server... Home Server = [x server x] * Identified AD Forest. Done gathering initial info. Doing initial required tests Testing server: Default-First-Site-Name\[x server x] Starting test: Connectivity An error that is usually temporary occurred during DNS host lookup. Please try again later. Got error while checking LDAP and RPC connectivity. Please check your firewall settings. ......................... [x server x] failed test Connectivity Doing primary tests Testing server: Default-First-Site-Name\[x server x] Starting test: DNS DNS Tests are running and not hung. Please wait a few minutes... ......................... [x server x] passed test DNS Running partition tests on : ForestDnsZones Running partition tests on : DomainDnsZones Running partition tests on : Schema Running partition tests on : Configuration Running partition tests on : [domain] Running enterprise tests on : [domain].local Starting test: DNS Test results for domain controllers: DC: [x server x].[domain].local Domain: [domain].local TEST: Basic (Basc) Error: No LDAP connectivity Error: can't read network adapter information through WMI Warning: The A record for this DC was not found Warning: The AAAA record for this DC was not found No host records (A or AAAA) were found for this DC TEST: Delegations (Del) Error: DNS server: [x server x].[domain].local. IP:192.168.1.250 [Broken delegated domain _msdcs.[domain].local.] TEST: Records registration (RReg) Error: Record registrations cannot be found for all the network adapters Summary of test results for DNS servers used by the above domain controllers: DNS server: 192.168.1.250 ([x server x].[domain].local.) 1 test failure on this DNS server Summary of DNS test results: Auth Basc Forw Del Dyn RReg Ext _________________________________________________________________ Domain: [domain].local [x server x] PASS FAIL PASS FAIL PASS FAIL n/a ......................... [domain].local failed test DNS
I have disabled the second NIC card, and the DNS entries on the main NIC are empty. The DNS has forwarders defined to the ISP's DNS servers and the broadband router with static A records for the broadband router and the server.
I suspect some SVR records and A/AAAA records are missing, but I cannot find out what is required to be set up as I have access to no other server to verify what should be present.
All replies (2)
Wednesday, January 13, 2016 6:52 AM ✅Answered
Hi,
>I have disabled the second NIC card.
As Windows Server 2012 R2 Essentials, only one NIC is supported on this server. Disable/remove any other NIC and only allow one NIC to be configured/available.
You have mentioned “stand-along”, which usually means it is not a domain member/DC, and functions more like workgroup servers. The “Dcdiag /test:DNSDNS” is mainly to be performed on one or all domain controllers in an Active Directory forest. If it is “stand-along” server, there might be errors returned by this commend.
If it is a domain environment, and I have misunderstood the “stand-along” which you have mentioned, please correct me.
Assume it is domain environment, the Essentials is the PDC(holds all FSMO), and you have successfully disable/remove another NIC on this server. Make sure that you have configured the TCP/IP correctly.
>I'm not sure if the server should be configured to use the broadband router as the forwardDNS, or the IP addresses used by the broadband router.
If your Essentials is located on the same subnet with the broadband router. And you have installed DNS role on Essentials server and use it as your internal DNS server. Just configured the “Default Gateway” as the broadband router’s IP address, and the “Preferred DNS server” as the Essentials’ IP address. Then, open DNS server console, configure the “forwarders” as the DNS servers’ IP address which is provided by your ISP.
Then, restart the server and Netlogon service on the server to re-register the DC related DNS records.
If the problem persist, please provide the “ipconfig /all” result of Essentials Server. And a simply description about your domain environment, such as servers, role installed, error message and etc.
Best Regards,
Eve Wang
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Monday, January 11, 2016 11:26 PM
One additional bit of information is that a number of ports are marked as NOT LiSTENING when I run the PortQry utility, but searching the web I've been unable to find any cause/what I need to do to fix these.
============================================= Starting portqry.exe -n 127.0.0.1 -e 135 -p TCP ... Querying target system called: 127.0.0.1 Attempting to resolve IP address to a name... IP address resolved to [x server x].[domain].local querying... TCP port 135 (epmap service): LISTENING Using ephemeral source port Querying Endpoint Mapper Database... Server's response: UUID: d95afe70-a6d5-4259-822e-2c84da1ddb0d ncacn_ip_tcp:127.0.0.1[49152] UUID: 50abc2a4-574d-40b3-9d66-ee4fd5fba076 ncacn_ip_tcp:127.0.0.1[60246] UUID: 897e2e5f-93f3-4376-9c9c-fd2277495c27 Frs2 Service ncacn_ip_tcp:127.0.0.1[50765] UUID: 367abb81-9844-35f1-ad32-98f038001003 ncacn_ip_tcp:127.0.0.1[65277] UUID: 91ae6020-9e3c-11cf-8d7c-00aa00c091be ncacn_np:127.0.0.1[\\pipe\\cert] UUID: 91ae6020-9e3c-11cf-8d7c-00aa00c091be ncacn_ip_tcp:127.0.0.1[65266] UUID: 12345678-1234-abcd-ef00-0123456789ab ncacn_ip_tcp:127.0.0.1[49164] UUID: 0b6edbfa-4a24-4fc6-8a23-942b1eca65d1 ncacn_ip_tcp:127.0.0.1[49164] UUID: ae33069b-a2a8-46ee-a235-ddfd339be281 ncacn_ip_tcp:127.0.0.1[49164] UUID: 4a452661-8290-4b36-8fbe-7f4093a94978 ncacn_ip_tcp:127.0.0.1[49164] UUID: 76f03f96-cdfd-44fc-a22c-64950a001209 ncacn_ip_tcp:127.0.0.1[49164] UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name ncacn_np:127.0.0.1[\\pipe\\lsass] UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name ncacn_ip_tcp:127.0.0.1[49155] UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface ncacn_np:127.0.0.1[\\pipe\\lsass] UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface ncacn_ip_tcp:127.0.0.1[49155] UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface ncacn_http:127.0.0.1[49159] UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface ncacn_np:127.0.0.1[\\pipe\\9eaeb0d45883cf69] UUID: 12345778-1234-abcd-ef00-0123456789ab ncacn_np:127.0.0.1[\\pipe\\lsass] UUID: 12345778-1234-abcd-ef00-0123456789ab ncacn_ip_tcp:127.0.0.1[49155] UUID: 12345778-1234-abcd-ef00-0123456789ab ncacn_http:127.0.0.1[49159] UUID: 12345778-1234-abcd-ef00-0123456789ab ncacn_np:127.0.0.1[\\pipe\\9eaeb0d45883cf69] UUID: 12345778-1234-abcd-ef00-0123456789ac ncacn_np:127.0.0.1[\\pipe\\lsass] UUID: 12345778-1234-abcd-ef00-0123456789ac ncacn_ip_tcp:127.0.0.1[49155] UUID: 12345778-1234-abcd-ef00-0123456789ac ncacn_http:127.0.0.1[49159] UUID: 12345778-1234-abcd-ef00-0123456789ac ncacn_np:127.0.0.1[\\pipe\\9eaeb0d45883cf69] UUID: 12345778-1234-abcd-ef00-0123456789ac ncacn_ip_tcp:127.0.0.1[49160] UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck ncacn_np:127.0.0.1[\\pipe\\lsass] UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck ncacn_ip_tcp:127.0.0.1[49155] UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck ncacn_http:127.0.0.1[49159] UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck ncacn_np:127.0.0.1[\\pipe\\9eaeb0d45883cf69] UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck ncacn_ip_tcp:127.0.0.1[49160] UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck ncacn_np:127.0.0.1[\\pipe\\efsrpc] UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck ncacn_np:127.0.0.1[\\pipe\\lsass] UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck ncacn_ip_tcp:127.0.0.1[49155] UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck ncacn_http:127.0.0.1[49159] UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck ncacn_np:127.0.0.1[\\pipe\\9eaeb0d45883cf69] UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck ncacn_ip_tcp:127.0.0.1[49160] UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck ncacn_np:127.0.0.1[\\pipe\\efsrpc] UUID: 12345678-1234-abcd-ef00-01234567cffb ncacn_np:127.0.0.1[\\pipe\\lsass] UUID: 12345678-1234-abcd-ef00-01234567cffb ncacn_ip_tcp:127.0.0.1[49155] UUID: 12345678-1234-abcd-ef00-01234567cffb ncacn_http:127.0.0.1[49159] UUID: 12345678-1234-abcd-ef00-01234567cffb ncacn_np:127.0.0.1[\\pipe\\9eaeb0d45883cf69] UUID: 12345678-1234-abcd-ef00-01234567cffb ncacn_ip_tcp:127.0.0.1[49160] UUID: 12345678-1234-abcd-ef00-01234567cffb ncacn_np:127.0.0.1[\\pipe\\efsrpc] UUID: b25a52bf-e5dd-4f4a-aea6-8ca7272a0e86 KeyIso ncacn_np:127.0.0.1[\\pipe\\lsass] UUID: b25a52bf-e5dd-4f4a-aea6-8ca7272a0e86 KeyIso ncacn_ip_tcp:127.0.0.1[49155] UUID: b25a52bf-e5dd-4f4a-aea6-8ca7272a0e86 KeyIso ncacn_http:127.0.0.1[49159] UUID: b25a52bf-e5dd-4f4a-aea6-8ca7272a0e86 KeyIso ncacn_np:127.0.0.1[\\pipe\\9eaeb0d45883cf69] UUID: b25a52bf-e5dd-4f4a-aea6-8ca7272a0e86 KeyIso ncacn_ip_tcp:127.0.0.1[49160] UUID: b25a52bf-e5dd-4f4a-aea6-8ca7272a0e86 KeyIso ncacn_np:127.0.0.1[\\pipe\\efsrpc] UUID: 7f1343fe-50a9-4927-a778-0c5859517bac DfsDs service ncacn_np:127.0.0.1[\\PIPE\\wkssvc] UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service ncacn_np:127.0.0.1[\\PIPE\\W32TIME_ALT] UUID: 1ff70682-0a51-30e8-076d-740be8cee98b ncacn_np:127.0.0.1[\\PIPE\\atsvc] UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f ncacn_np:127.0.0.1[\\PIPE\\atsvc] UUID: 86d35949-83c9-4044-b424-db363231fd0c ncacn_np:127.0.0.1[\\PIPE\\atsvc] UUID: 86d35949-83c9-4044-b424-db363231fd0c ncacn_ip_tcp:127.0.0.1[49154] UUID: 3a9ef155-691d-4449-8d05-09ad57031823 ncacn_np:127.0.0.1[\\PIPE\\atsvc] UUID: 3a9ef155-691d-4449-8d05-09ad57031823 ncacn_ip_tcp:127.0.0.1[49154] UUID: 552d076a-cb29-4e44-8b6a-d15e59e2c0af IP Transition Configuration endpoint ncacn_np:127.0.0.1[\\PIPE\\atsvc] UUID: 552d076a-cb29-4e44-8b6a-d15e59e2c0af IP Transition Configuration endpoint ncacn_ip_tcp:127.0.0.1[49154] UUID: 552d076a-cb29-4e44-8b6a-d15e59e2c0af IP Transition Configuration endpoint ncacn_np:127.0.0.1[\\PIPE\\srvsvc] UUID: 2e6035b2-e8f1-41a7-a044-656b439c4c34 Proxy Manager provider server endpoint ncacn_np:127.0.0.1[\\PIPE\\atsvc] UUID: 2e6035b2-e8f1-41a7-a044-656b439c4c34 Proxy Manager provider server endpoint ncacn_ip_tcp:127.0.0.1[49154] UUID: 2e6035b2-e8f1-41a7-a044-656b439c4c34 Proxy Manager provider server endpoint ncacn_np:127.0.0.1[\\PIPE\\srvsvc] UUID: c36be077-e14b-4fe9-8abc-e856ef4f048b Proxy Manager client server endpoint ncacn_np:127.0.0.1[\\PIPE\\atsvc] UUID: c36be077-e14b-4fe9-8abc-e856ef4f048b Proxy Manager client server endpoint ncacn_ip_tcp:127.0.0.1[49154] UUID: c36be077-e14b-4fe9-8abc-e856ef4f048b Proxy Manager client server endpoint ncacn_np:127.0.0.1[\\PIPE\\srvsvc] UUID: c49a5a70-8a7f-4e70-ba16-1e8f1f193ef1 Adh APIs ncacn_np:127.0.0.1[\\PIPE\\atsvc] UUID: c49a5a70-8a7f-4e70-ba16-1e8f1f193ef1 Adh APIs ncacn_ip_tcp:127.0.0.1[49154] UUID: c49a5a70-8a7f-4e70-ba16-1e8f1f193ef1 Adh APIs ncacn_np:127.0.0.1[\\PIPE\\srvsvc] UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name ncacn_np:127.0.0.1[\\PIPE\\atsvc] UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name ncacn_ip_tcp:127.0.0.1[49154] UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name ncacn_np:127.0.0.1[\\PIPE\\srvsvc] UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1 ncacn_np:127.0.0.1[\\PIPE\\atsvc] UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1 ncacn_ip_tcp:127.0.0.1[49154] UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1 ncacn_np:127.0.0.1[\\PIPE\\srvsvc] UUID: 7d814569-35b3-4850-bb32-83035fcebf6e IAS RPC server ncacn_np:127.0.0.1[\\PIPE\\atsvc] UUID: 7d814569-35b3-4850-bb32-83035fcebf6e IAS RPC server ncacn_ip_tcp:127.0.0.1[49154] UUID: 7d814569-35b3-4850-bb32-83035fcebf6e IAS RPC server ncacn_np:127.0.0.1[\\PIPE\\srvsvc] UUID: 7d814569-35b3-4850-bb32-83035fcebf6e IAS RPC server ncacn_np:127.0.0.1[\\pipe\\SessEnvPublicRpc] UUID: 201ef99a-7fa0-444c-9399-19ba84f12a1a AppInfo ncacn_np:127.0.0.1[\\PIPE\\atsvc] UUID: 201ef99a-7fa0-444c-9399-19ba84f12a1a AppInfo ncacn_ip_tcp:127.0.0.1[49154] UUID: 201ef99a-7fa0-444c-9399-19ba84f12a1a AppInfo ncacn_np:127.0.0.1[\\PIPE\\srvsvc] UUID: 201ef99a-7fa0-444c-9399-19ba84f12a1a AppInfo ncacn_np:127.0.0.1[\\pipe\\SessEnvPublicRpc] UUID: 5f54ce7d-5b79-4175-8584-cb65313a0e98 AppInfo ncacn_np:127.0.0.1[\\PIPE\\atsvc] UUID: 5f54ce7d-5b79-4175-8584-cb65313a0e98 AppInfo ncacn_ip_tcp:127.0.0.1[49154] UUID: 5f54ce7d-5b79-4175-8584-cb65313a0e98 AppInfo ncacn_np:127.0.0.1[\\PIPE\\srvsvc] UUID: 5f54ce7d-5b79-4175-8584-cb65313a0e98 AppInfo ncacn_np:127.0.0.1[\\pipe\\SessEnvPublicRpc] UUID: fd7a0523-dc70-43dd-9b2e-9c5ed48225b1 AppInfo ncacn_np:127.0.0.1[\\PIPE\\atsvc] UUID: fd7a0523-dc70-43dd-9b2e-9c5ed48225b1 AppInfo ncacn_ip_tcp:127.0.0.1[49154] UUID: fd7a0523-dc70-43dd-9b2e-9c5ed48225b1 AppInfo ncacn_np:127.0.0.1[\\PIPE\\srvsvc] UUID: fd7a0523-dc70-43dd-9b2e-9c5ed48225b1 AppInfo ncacn_np:127.0.0.1[\\pipe\\SessEnvPublicRpc] UUID: 58e604e8-9adb-4d2e-a464-3b0683fb1480 AppInfo ncacn_np:127.0.0.1[\\PIPE\\atsvc] UUID: 58e604e8-9adb-4d2e-a464-3b0683fb1480 AppInfo ncacn_ip_tcp:127.0.0.1[49154] UUID: 58e604e8-9adb-4d2e-a464-3b0683fb1480 AppInfo ncacn_np:127.0.0.1[\\PIPE\\srvsvc] UUID: 58e604e8-9adb-4d2e-a464-3b0683fb1480 AppInfo ncacn_np:127.0.0.1[\\pipe\\SessEnvPublicRpc] UUID: a398e520-d59a-4bdd-aa7a-3c1e0303a511 IKE/Authip API ncacn_np:127.0.0.1[\\PIPE\\atsvc] UUID: a398e520-d59a-4bdd-aa7a-3c1e0303a511 IKE/Authip API ncacn_ip_tcp:127.0.0.1[49154] UUID: a398e520-d59a-4bdd-aa7a-3c1e0303a511 IKE/Authip API ncacn_np:127.0.0.1[\\PIPE\\srvsvc] UUID: a398e520-d59a-4bdd-aa7a-3c1e0303a511 IKE/Authip API ncacn_np:127.0.0.1[\\pipe\\SessEnvPublicRpc] UUID: 98716d03-89ac-44c7-bb8c-285824e51c4a XactSrv service ncacn_np:127.0.0.1[\\PIPE\\atsvc] UUID: 98716d03-89ac-44c7-bb8c-285824e51c4a XactSrv service ncacn_ip_tcp:127.0.0.1[49154] UUID: 98716d03-89ac-44c7-bb8c-285824e51c4a XactSrv service ncacn_np:127.0.0.1[\\PIPE\\srvsvc] UUID: 98716d03-89ac-44c7-bb8c-285824e51c4a XactSrv service ncacn_np:127.0.0.1[\\pipe\\SessEnvPublicRpc] UUID: 1a0d010f-1c33-432c-b0f5-8cf4e8053099 IdSegSrv service ncacn_np:127.0.0.1[\\PIPE\\atsvc] UUID: 1a0d010f-1c33-432c-b0f5-8cf4e8053099 IdSegSrv service ncacn_ip_tcp:127.0.0.1[49154] UUID: 1a0d010f-1c33-432c-b0f5-8cf4e8053099 IdSegSrv service ncacn_np:127.0.0.1[\\PIPE\\srvsvc] UUID: 1a0d010f-1c33-432c-b0f5-8cf4e8053099 IdSegSrv service ncacn_np:127.0.0.1[\\pipe\\SessEnvPublicRpc] UUID: f6beaff7-1e19-4fbb-9f8f-b89e2018337c Event log TCPIP ncacn_np:127.0.0.1[\\pipe\\eventlog] UUID: f6beaff7-1e19-4fbb-9f8f-b89e2018337c Event log TCPIP ncacn_ip_tcp:127.0.0.1[49153] UUID: 30adc50c-5cbc-46ce-9a0e-91914789e23c NRP server endpoint ncacn_np:127.0.0.1[\\pipe\\eventlog] UUID: 30adc50c-5cbc-46ce-9a0e-91914789e23c NRP server endpoint ncacn_ip_tcp:127.0.0.1[49153] UUID: abfb6ca3-0c5e-4734-9285-0aee72fe8d1c Wcm Service ncacn_np:127.0.0.1[\\pipe\\eventlog] UUID: abfb6ca3-0c5e-4734-9285-0aee72fe8d1c Wcm Service ncacn_ip_tcp:127.0.0.1[49153] UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d6 DHCPv6 Client LRPC Endpoint ncacn_np:127.0.0.1[\\pipe\\eventlog] UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d6 DHCPv6 Client LRPC Endpoint ncacn_ip_tcp:127.0.0.1[49153] UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint ncacn_np:127.0.0.1[\\pipe\\eventlog] UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint ncacn_ip_tcp:127.0.0.1[49153] UUID: 697dcda9-3ba9-4eb2-9247-e11f1901b0d2 ncacn_np:127.0.0.1[\\pipe\\LSM_API_service] UUID: 9b008953-f195-4bf9-bde0-4471971e58ed ncacn_np:127.0.0.1[\\pipe\\LSM_API_service] UUID: 76f226c3-ec14-4325-8a99-6a46348418af ncacn_np:127.0.0.1[\\PIPE\\InitShutdown] UUID: d95afe70-a6d5-4259-822e-2c84da1ddb0d ncacn_np:127.0.0.1[\\PIPE\\InitShutdown] Total endpoints found: 122 ==== End of RPC Endpoint Mapper query response ==== portqry.exe -n 127.0.0.1 -e 135 -p TCP exits with return code 0x00000000. ============================================= Starting portqry.exe -n 127.0.0.1 -e 389 -p BOTH ... Querying target system called: 127.0.0.1 Attempting to resolve IP address to a name... IP address resolved to [x server x].[domain].local querying... TCP port 389 (ldap service): LISTENING Using ephemeral source port Sending LDAP query to TCP port 389... LDAP query response: currentdate: 01/11/2016 23:18:40 (unadjusted GMT) subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=[domain],DC=local dsServiceName: CN=NTDS Settings,CN=[x server x],CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=[domain],DC=local namingContexts: DC=[domain],DC=local defaultNamingContext: DC=[domain],DC=local schemaNamingContext: CN=Schema,CN=Configuration,DC=[domain],DC=local configurationNamingContext: CN=Configuration,DC=[domain],DC=local rootDomainNamingContext: DC=[domain],DC=local supportedControl: 1.2.840.113556.1.4.319 supportedLDAPVersion: 3 supportedLDAPPolicies: MaxPoolThreads highestCommittedUSN: 94424 supportedSASLMechanisms: GSSAPI dnsHostName: [x server x].[domain].local ldapServiceName: [domain].local:[x server x]$@[domain].LOCAL serverName: CN=[x server x],CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=[domain],DC=local supportedCapabilities: 1.2.840.113556.1.4.800 isSynchronized: TRUE isGlobalCatalogReady: TRUE domainFunctionality: 6 forestFunctionality: 6 domainControllerFunctionality: 6 ======== End of LDAP query response ======== UDP port 389 (unknown service): LISTENING or FILTERED Using ephemeral source port Sending LDAP query to UDP port 389... LDAP query response: currentdate: 01/11/2016 23:18:44 (unadjusted GMT) subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=[domain],DC=local dsServiceName: CN=NTDS Settings,CN=[x server x],CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=[domain],DC=local namingContexts: DC=[domain],DC=local defaultNamingContext: DC=[domain],DC=local schemaNamingContext: CN=Schema,CN=Configuration,DC=[domain],DC=local configurationNamingContext: CN=Configuration,DC=[domain],DC=local rootDomainNamingContext: DC=[domain],DC=local supportedControl: 1.2.840.113556.1.4.319 supportedLDAPVersion: 3 supportedLDAPPolicies: MaxPoolThreads highestCommittedUSN: 94424 supportedSASLMechanisms: GSSAPI dnsHostName: [x server x].[domain].local ldapServiceName: [domain].local:[x server x]$@[domain].LOCAL serverName: CN=[x server x],CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=[domain],DC=local supportedCapabilities: 1.2.840.113556.1.4.800 isSynchronized: TRUE isGlobalCatalogReady: TRUE domainFunctionality: 6 forestFunctionality: 6 domainControllerFunctionality: 6 ======== End of LDAP query response ======== UDP port 389 is LISTENING portqry.exe -n 127.0.0.1 -e 389 -p BOTH exits with return code 0x00000000. ============================================= Starting portqry.exe -n 127.0.0.1 -e 636 -p TCP ... Querying target system called: 127.0.0.1 Attempting to resolve IP address to a name... IP address resolved to [x server x].[domain].local querying... TCP port 636 (ldaps service): LISTENING portqry.exe -n 127.0.0.1 -e 636 -p TCP exits with return code 0x00000000. ============================================= Starting portqry.exe -n 127.0.0.1 -e 3268 -p TCP ... Querying target system called: 127.0.0.1 Attempting to resolve IP address to a name... IP address resolved to [x server x].[domain].local querying... TCP port 3268 (msft-gc service): LISTENING Using ephemeral source port Sending LDAP query to TCP port 3268... LDAP query response: currentdate: 01/11/2016 23:18:44 (unadjusted GMT) subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=[domain],DC=local dsServiceName: CN=NTDS Settings,CN=[x server x],CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=[domain],DC=local namingContexts: DC=[domain],DC=local defaultNamingContext: DC=[domain],DC=local schemaNamingContext: CN=Schema,CN=Configuration,DC=[domain],DC=local configurationNamingContext: CN=Configuration,DC=[domain],DC=local rootDomainNamingContext: DC=[domain],DC=local supportedControl: 1.2.840.113556.1.4.319 supportedLDAPVersion: 3 supportedLDAPPolicies: MaxPoolThreads highestCommittedUSN: 94424 supportedSASLMechanisms: GSSAPI dnsHostName: [x server x].[domain].local ldapServiceName: [domain].local:[x server x]$@[domain].LOCAL serverName: CN=[x server x],CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=[domain],DC=local supportedCapabilities: 1.2.840.113556.1.4.800 isSynchronized: TRUE isGlobalCatalogReady: TRUE domainFunctionality: 6 forestFunctionality: 6 domainControllerFunctionality: 6 ======== End of LDAP query response ======== portqry.exe -n 127.0.0.1 -e 3268 -p TCP exits with return code 0x00000000. ============================================= Starting portqry.exe -n 127.0.0.1 -e 3269 -p TCP ... Querying target system called: 127.0.0.1 Attempting to resolve IP address to a name... IP address resolved to [x server x].[domain].local querying... TCP port 3269 (msft-gc-ssl service): LISTENING portqry.exe -n 127.0.0.1 -e 3269 -p TCP exits with return code 0x00000000. ============================================= Starting portqry.exe -n 127.0.0.1 -e 53 -p BOTH ... Querying target system called: 127.0.0.1 Attempting to resolve IP address to a name... IP address resolved to [x server x].[domain].local querying... TCP port 53 (domain service): LISTENING UDP port 53 (domain service): LISTENING portqry.exe -n 127.0.0.1 -e 53 -p BOTH exits with return code 0x00000000. ============================================= Starting portqry.exe -n 127.0.0.1 -e 88 -p BOTH ... Querying target system called: 127.0.0.1 Attempting to resolve IP address to a name... IP address resolved to [x server x].[domain].local querying... TCP port 88 (kerberos service): LISTENING UDP port 88 (kerberos service): NOT LISTENING portqry.exe -n 127.0.0.1 -e 88 -p BOTH exits with return code 0x00000001. ============================================= Starting portqry.exe -n 127.0.0.1 -e 445 -p TCP ... Querying target system called: 127.0.0.1 Attempting to resolve IP address to a name... IP address resolved to [x server x].[domain].local querying... TCP port 445 (microsoft-ds service): LISTENING portqry.exe -n 127.0.0.1 -e 445 -p TCP exits with return code 0x00000000. ============================================= Starting portqry.exe -n 127.0.0.1 -e 137 -p UDP ... Querying target system called: 127.0.0.1 Attempting to resolve IP address to a name... IP address resolved to [x server x].[domain].local querying... UDP port 137 (netbios-ns service): NOT LISTENING portqry.exe -n 127.0.0.1 -e 137 -p UDP exits with return code 0x00000001. ============================================= Starting portqry.exe -n 127.0.0.1 -e 138 -p UDP ... Querying target system called: 127.0.0.1 Attempting to resolve IP address to a name... IP address resolved to [x server x].[domain].local querying... UDP port 138 (netbios-dgm service): NOT LISTENING portqry.exe -n 127.0.0.1 -e 138 -p UDP exits with return code 0x00000001. ============================================= Starting portqry.exe -n 127.0.0.1 -e 139 -p TCP ... Querying target system called: 127.0.0.1 Attempting to resolve IP address to a name... IP address resolved to [x server x].[domain].local querying... TCP port 139 (netbios-ssn service): NOT LISTENING portqry.exe -n 127.0.0.1 -e 139 -p TCP exits with return code 0x00000001. ============================================= Starting portqry.exe -n 127.0.0.1 -e 42 -p TCP ... Querying target system called: 127.0.0.1 Attempting to resolve IP address to a name... IP address resolved to [x server x].[domain].local querying... TCP port 42 (nameserver service): NOT LISTENING portqry.exe -n 127.0.0.1 -e 42 -p TCP exits with return code 0x00000001.
Basically everything seems to be OK, but the dcdiag test fails and I'm unable to connect windows 10 clients to the server.