Greetings, I am taking over systems admin for a Windows Server 2003 based company, we will call it "acme" to protect the innocent. The first issue that I would like to solve manifests itself as very slow login to the domain, aproximately 4 minutes for any account trying to log in. I have been reading and searching for answers and I am inclined to believe that (among other things....) the DNS setup doesn't make sense. The server has two NIC's one with an ip of 192.168.1.42 and the other of 192.168.1.43. These are statically assigned with a DNS of 192.168.1.1, the address of the router that is connected via Comcast to the internet. When I look at the DNS settings they look like this: Name Type Data _msdcs _sites _tcp _udp DomainDnsZones ForestDnsZones (same as parent folder) Start of Authority (SOA) [51], acmeserver.acme1., hostmaster. (same as parent folder) Name Server (NS) acmeserver.acme1. (same as parent folder) Host (A) 192.168.1.159 companyweb Alias (CNAME) acmeserver.acme.local. ACMESERVER Host (A) 192.168.1.161 Since there has been no sys admin, well, for 10 years, and the previous employee tasked with server admin is no longer with the company I have no explanation why (or when) the .159 and .161 ip's were chosen and even if there was a server at one time using these ip's. My goal is to not cause any more trouble, but shouldn't these ip's be of the actual Win server? knowing that they are .42 and .43 what should the DNS records look like? This company does nothing from this site that is publicly accessible. Their website is hosted by a 3rd party and has no connection to this network. There is no customer access to this site. They run a program off the server using a SQl database that talks to the workstations(clients). The workstations and server are able to resolve to the internet as you would guess.

Hello, this sounds like DNS settings on the machines, please post an unedited ipconfig /all from all DC/DNS servers and a problem client with slow logon. A DC should never have 2 ip addresses, this is called multi-homing and result in multiple problems. And x.x.x.42 and x.x.x.43 are the current ip addresses these must be registered in the DNS zones, correct. Is the DHCP client service started and set to automatic on the DC/DNS server, required for DNS registration?Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Thank you Meinolf, here are the ipconfig /all results from the one and only server and a slow client. DHCP service is provided by the Comcast modem/gateway/router and not used for company owned equipment. I believe also DHCP is turned off on the Win 2003 Server. Server ---------------------------------- C:\Documents and Settings\Administrator> ipconfig /all Windows IP Configuration Host Name . . . . . .: ACMESERVER Primary Dns Suffix . . . .: acme1 Node Type . . . . . .: Hybrid IP Routing Enabled . . . .: Yes WINS Proxy Enabled . . . .: No DNS Suffix Search List . . . .: acme1 Ethernet adapter Server Local Area Connection: Connection-specific DNS Suffix . .: Description . . . . . .:Broadcom NeXtreme Gigabit Ethernet Physical Address . . . . .: 00-1E-4F-3F-CB-60 DHCP Enabled . . . . .: No IP Address . . . . . .: 192.168.1.42 Subnet Mask . . . . . .: 255.255.255.0 Default Gateway . . . . .: 192.168.1.1 DNS Servers . . . . . .: 192.168.1.1 Ethernet Network Connection: Connection-specific DNS Suffix . .: Description . . . . . .:Broadcom NeXtreme Gigabit Ethernet #2 Physical Address . . . . .: 00-1E-4F-3F-CB-61 DHCP Enabled . . . . .: No IP Address . . . . . .: 192.168.1.43 Subnet Mask . . . . . .: 255.255.255.0 Default Gateway . . . . .: 192.168.1.1 DNS Servers . . . . . .: 192.168.1.199 NetBIOS over Tcpip . . . .: Disabled ---------------------------------------------------------------------------- Slow logon client: C:\Documents and Settings\front desk.ACMEFITNESS.000> ipconfig /all Windows IP Configuration Host Name . . . . . .: AcmeFront Primary Dns Suffix . . . .: acmefitness.local Node Type . . . . . .: Unknown IP Routing Enabled . . . .: No WINS Proxy Enabled . . . .: No DNS Suffix Search List . . . .: acmefitness.local Ethernet adapter Server Local Area Connection 2: Connection-specific DNS Suffix . .: Description . . . . . .:Intel<R> Pro/1000 GT Desktop Adapter Physical Address . . . . .: 00-1B-21-38-03-0A DHCP Enabled . . . . .: No IP Address . . . . . .: 192.168.1.14 Subnet Mask . . . . . .: 255.255.255.0 Default Gateway . . . . .: 192.168.1.1 DNS Servers . . . . . .: 192.168.1.1

Hello, as already said the server is multi-homed. Please remove one of the ip addresses on the NIC and also the records ion the DNS zones from it. Then run ipconfig /flushdns and ipconfig /registerdns and restart the netlogon service on the DC. Additional DISABLE RRAS on the DC. If that is done and the DNS zones show only the correct A and Nameserver record for the DC/DNS server then go on with the workstation. Here remove the default gateway ip address as DNS server on the NIC and add the DC/DNS server ONLY. Then run also ipconfig /flushdns and ipconfig /registerdns and restart the client. Make sure the machines register correct in the DNS zone on the server. If you need internet access for the domain machines then configure the FORWARDERS in the DNS server properties in the DNS management console on the DC/DNS server with the ISPs DNS server or use the root hints. BUT do NOT use the DHCP server as DNS server, this one can NTO resolve the domain name from the internet in your private ip range and so the logon is taking long time.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Greetings, I think I made most (not all) of the changes you suggested: 1) On the server I disabled the second NIC and changed the DNS entries as follows: Name Type Data _msdcs _sites _tcp _udp DomainDnsZones ForestDnsZones (same as parent folder) Start of Authority (SOA) [54], acmeserver.acme1., hostmaster. (same as parent folder) Name Server (NS) acmeserver.acme1. (same as parent folder) Host (A) 192.168.1.42 companyweb Alias (CNAME) acmeserver.acmefitness.local. ACMESERVER Host (A) 192.168.1.42 2) Did the "ipconfig /flushdns" and "ipconfig /registerdns" on the server 3) Restarted the netlogon service I am still confused here, here is the "ipconfig /all" currently from the SERVER: Windows IP Configuration Host Name . . . . . . . . . . . . : ACMESERVER Primary Dns Suffix . . . . . . . : acme1 Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : Yes WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : acme1 Ethernet adapter Server Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet Physical Address. . . . . . . . . : 00-1E-4F-3F-CB-60 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.1.42 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 192.168.1.1 Should I change the Default Gateway and the DNS Servers setting on the SERVER to 192.168.1.42 ? Also should the Default Gateway and DNS Server both be set to 192.168.1.42 on the WORKSTATIONS ? I am, however, not wanting to further degrade services so I have not turned off RRAS yet. I went through all the records I could find in the DNS settings and found several other places where what I guess are now bogus .159 and .160 ip's that no longer exist on this network. In the DomainDNSZones settings I found this, I have not changed anything here, what should this look like ? Name Type Data _sites _tcp (same as parent folder) Host (A) 192.168.1.160 (same as parent folder) Host (A) 192.168.1.159 In the ForestDnsZones I found this, I have not changed anything here, what should this look like ? Name Type Data _sites _tcp (same as parent folder) Host (A) 192.168.1.42 (same as parent folder) Host (A) 192.168.1.159 The msdcs records look like this, all OK? Name Type Data dc domains gc pdc (same as parent folder) Start of Authority (SOA) [16], acmeserver.acme1., hostmaster. (same as parent folder) Name Server (NS) acmeserver.acme1. 74fe93dd-97c6-48f3-a7a6-33bbbaeb48c4 Alias (CNAME) acmeserver.acmefitness.local. 85b2bbf3-b667-441f-bdfa-63d7ac3c3734 Alias (CNAME) acmeserver.acmeitness.local. Finally the root hints is listing the bogus .161 should I change this to .42, and the forwarders is listing 192.168.1.1 for All other DNS domains? Meinolf I do appreciate you taking the time to help me with this it is more complicated than I realized, thanks!

Hello, RRAS is still enabled. Please disable it. IP Address. . . . . . . . . . . . : 192.168.1.42 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 192.168.1.1 The DC is using your default gateway as a DNS server. Here I suppose that the DC is a DNS server. So, use the following: IP Address. . . . . . . . . . . . : 192.168.1.42 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 192.168.1.42 Once done, run ipconfig /registerdns and restart netlogon on the DC. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified IT Professional: Enterprise Administrator

Hi and thanks Mr. X, Disabled RRAS and set the DC's DNS to itself, flushed and registered DNS, restarted netlogon: Windows IP Configuration Host Name . . . . . . . . . . . . : ACMESERVER Primary Dns Suffix . . . . . . . : acme1 Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : acme1 Ethernet adapter Server Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet Physical Address. . . . . . . . . : 00-1E-4F-3F-CB-60 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.1.42 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 192.168.1.42This did not cause any problems but did not seem to fix the slow logon problems. When I ran nslookup from the DC/DNS serverit looked like this:*** Can't find server name for address 192.168.1.42: Non-existent domain Default Server: UnKnown Address: 192.168.1.42 Does this look right? I know I am getting closer but to aid troubleshooting I built a clean Win 7 system to join to the DC and I could not get it to connect as I keep getting a Path not found error to the server. I have this system plugged directly into the same switch as the server and it has 192.168.1.42 as the DNS, a static ip of 192.168.1.20 a gateway of 192.168.1.1 and I have disabled IPV6.I am assuming this problem is related the the DNS issues and the UnKown domain from the the nslookup?Again I thank you for your help as we figure this out.

Hello, if your client still use the wrong DNS servers as mentioned above: IP Address . . . . . .: 192.168.1.14 Subnet Mask . . . . . .: 255.255.255.0 Default Gateway . . . . .: 192.168.1.1 DNS Servers . . . . . .: 192.168.1.1 then what you see is expected. Configure the client to use the domain DNS server on the NIC and NOT the router. If this is for internet connectivity then configure the FORWARDERS in the DNS server properties to the ISPs DNS sever in the DNS management console.Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Hi Meinholf, Yes the client that received the "no path to server" error was using .42 , the DC/DNS Server, as its DNS server. And the FORWARDERS does list 192.168.1.1 (the router/gateway/cable modem ip address). Do I need to hard code the ISP's real DNS ip's in the forwarders or is 192.168.1.1 correct? Also, as of yesterday when I turned of RRAS and set the Server's own DNS to itself I have 18 pages (and growing) of this error message in the App logs: 8063 MSExchangeAL N/A 6/9/2011 6:53 AM ACMESERVER Category: Service Control Message: Could not read the root entry on directory 'ACMESERVER.acmefitness.local'. Cannot access configuration information. DC=acmefitness,DC=local For more information, click http://www.microsoft.com/contentredirect.asp. We don't do email nor do we run an exchange server at this site, or is this error telling me that we do (we did at one time) and now things are out of whack? Finally the root hints is listing a bogus .161 should I change this to .42, and the forwarders is listing 192.168.1.1 for All other DNS domains?

Hello, please post again an up to date ipconfig /all from the server and a machine with problems. I would use the Forwarders to connect to the ISP instead of your router. Running Exchange on DCs is not recommended, even not from Microsoft. Is this the SBS version from Windows server?Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties or guarantees , and confers no rights.

Greetings, Yes, this is a SBS Win 2003 Server. This whole system just keeps getting more confusing. As an update here is the current ipconfig /all from the server which is the DC and the DNS: ----------------------------------------------------------------------- Windows IP Configuration Host Name . . . . . . . . . . . . : ACMESERVER Primary Dns Suffix . . . . . . . : acme1 Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : acme1 Ethernet adapter Server Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet Physical Address. . . . . . . . . : 00-1E-4F-3F-CB-60 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.1.42 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 192.168.1.42 -------------------------------------------------------------------------- and here is the current ipconfig /all from a workstation that takes 4,5,6,7,8 minutes to login: Windows IP Configuration Host Name . . . . . . . . . . . . : TRAINER1 Primary Dns Suffix . . . . . . . : acmefitness.local Node Type . . . . . . . . . . . . : Unknown IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : acmefitness.local Ethernet adapter Local Area Connection 2: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) PRO/1000 GT Desktop Adapter Physical Address. . . . . . . . . : 00-1B-21-21-DA-60 Dhcp Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.1.16 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 192.168.1.42 As I am learning more about the issues here I have been reading logs on the the server for hints to the situation, here though are some pieces of the log from the same workstation (TRAINER1) that I listed the ipconfig /all right above. TRAINER1 Log from yesterday: ---------------------------------------------------------------------------- There is more to the log but I did not copy records that looked like the "normal" Windows startup. This is a reverse order where I rebooted the system. - 6/9/11 2:34:38 PM DnsApi Warning None 11164 N/A TRAINER1 "The system failed to register host (A) resource records (RRs) for network adapter with settings: Adapter Name : {5D14C8BE-78F3-40A9-A3FF-CC8125BC6FF7} Host Name : TRAINER1 Primary Domain Suffix : acmefitness.local DNS server list : 192.168.1.42 Sent update to server : <?> IP Address(es) : 192.168.1.16 The reason the system could not register these RRs was because either (a) the DNS server does not support the DNS dynamic update protocol, or (b) the authoritative zone for the specified DNS domain name does not accept dynamic updates. To register the DNS host (A) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator." - 6/9/11 2:18:17 PM NETLOGON Error None 5719 N/A TRAINER1 "No Domain Controller is available for domain ACMEFITNESS due to the following: The RPC server is unavailable. . Make sure that the computer is connected to the network and try again. If the problem persists, please contact your domain administrator." - 6/9/11 2:13:41 PM LSASRV Warning SPNEGO (Negotiator) 40961 N/A TRAINER1 The Security System could not establish a secured connection with the server cifs/acmeserver.acmefitness.local. No authentication protocol was available. - 6/9/11 2:13:41 PM LSASRV Warning SPNEGO (Negotiator) 40960 N/A TRAINER1 "The Security System detected an attempted downgrade attack for server cifs/acmeserver.acmefitness.local. The failure code from authentication protocol Kerberos was ""There are currently no logon servers available to service the logon request. (0xc000005e)""." --------------------------------------------------------------------------------- Again I am surprised anything works when I read that there is no Domain controller/RPC and the issues with the Dnsapi. Any help would be greatly appreciated, thanks….

Bump...sorry.

This is making me a little crazy as I can't figure out how fix this but I believe whatever the fix turns out to be that it will fix all the symptoms. Thanks to those that have offered advice previously. ACME FITNESS Windows SBS Server 2003 Fully updated Single NIC (does have 2 NIC's but one is disabled) Domain and DNS Server SQL Server for main business application Rebooted today after weeks of no luck in troubleshooting. All systems have Domain/DNS server as the DNS server as well as a static ip address. Symptoms: 1) Slow logon from workstations. 5-10 minutes to desktop from entering account and hitting return. 2) Two new systems both Win 7, one 64-bit and one 32-bit CANNOT join to domain. Error consistently "no path to host". 3) Logs on several workstations show the following: --------------------------------------------------------------------------- No Domain Controller is available for domain ACMEFITNESS due to the following: The RPC server is unavailable. . Make sure that the computer is connected to the network and try again. If the problem persists, please contact your domain administrator. --------------------------------------------------------------------------- followed by this: The time provider NtpClient failed to establish a trust relationship between this computer and the acmefitness.local domain in order to securely synchronize time. NtpClient will try again in 15 minutes. The error was: The trust relationship between this workstation and the primary domain failed. (0x800706FD) and this: --------------------------------------------------------------------------- The system failed to register host (A) resource records (RRs) for network adapter with settings: Adapter Name : {5D14C8BE-78F3-40A9-A3FF-CC8125BC6FF7} Host Name : CUSTOMER1 Primary Domain Suffix : acmefitness.local DNS server list : 192.168.1.42 Sent update to server : <?> IP Address(es) : 192.168.1.12 The reason the system could not register these RRs was because either (a) the DNS server does not support the DNS dynamic update protocol, or (b) the authoritative zone for the specified DNS domain name does not accept dynamic updates. To register the DNS host (A) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator. ------------------------------------------------------------------------------ ACMESERVER ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : ACMESERVER Primary Dns Suffix . . . . . . . : acme1 Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : acme1 Ethernet adapter Server Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet Physical Address. . . . . . . . . : 00-1E-4F-3F-CB-60 DHCP Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.1.42 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 192.168.1.42 ------------------------------------------------------------------------------ CUSTOMER1 (a representative workstation) ipconfig /all Windows IP Configuration Host Name . . . . . . . . . . . . : Customer1 Primary Dns Suffix . . . . . . . : acmefitness.local Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : acmefitness.local Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Intel(R) 82562V-2 10/100 Network Connection Physical Address. . . . . . . . . : 00-1D-09-99-AF-CF Dhcp Enabled. . . . . . . . . . . : No IP Address. . . . . . . . . . . . : 192.168.1.12 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.1.1 DNS Servers . . . . . . . . . . . : 192.168.1.42 Primary WINS Server . . . . . . . : 192.168.1.42 ------------------------------------------------------------------------------ portquery results from ACMESERVER today before reboot, not sure if this is helpful: ---------------------- ============================================= 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 ACMESERVER.acme1 querying... TCP port 135 (epmap service): LISTENING Using ephemeral source port Querying Endpoint Mapper Database... Server's response: UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint ncalrpc:[DNSResolver] UUID: f1ec59ab-4ca9-4c30-b2d0-54ef1db441b7 Isolation Communication Endpoint ncalrpc:[LRPC00001d2c.00000001] UUID: f1ec59ab-4ca9-4c30-b2d0-54ef1db441b7 Isolation Communication Endpoint ncalrpc:[LRPC00001fa0.00000001] UUID: f1ec59ab-4ca9-4c30-b2d0-54ef1db441b7 Isolation Communication Endpoint ncalrpc:[LRPC00001b2c.00000001] UUID: f1ec59ab-4ca9-4c30-b2d0-54ef1db441b7 Isolation Communication Endpoint ncalrpc:[LRPC0000134c.00000001] UUID: f1ec59ab-4ca9-4c30-b2d0-54ef1db441b7 Isolation Communication Endpoint ncalrpc:[LRPC00001d28.00000001] UUID: f1ec59ab-4ca9-4c30-b2d0-54ef1db441b7 Isolation Communication Endpoint ncalrpc:[LRPC00001a78.00000001] UUID: f1ec59ab-4ca9-4c30-b2d0-54ef1db441b7 Isolation Communication Endpoint ncalrpc:[LRPC0000154c.00000001] UUID: f1ec59ab-4ca9-4c30-b2d0-54ef1db441b7 Isolation Communication Endpoint ncalrpc:[LRPC000014b8.00000001] UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service ncalrpc:[W32TIME_ALT] UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service ncacn_np:\\\\ACMESERVER[\\PIPE\\W32TIME_ALT] UUID: 2f5f6521-cb55-1059-b446-00df0bce31db Unimodem LRPC Endpoint ncacn_np:\\\\ACMESERVER[\\pipe\\tapsrv] UUID: 2f5f6521-cb55-1059-b446-00df0bce31db Unimodem LRPC Endpoint ncalrpc:[tapsrvlpc] UUID: 2f5f6521-cb55-1059-b446-00df0bce31db Unimodem LRPC Endpoint ncalrpc:[unimdmsvc] UUID: a4f1db00-ca47-1067-b31e-00dd010662da Exchange Server STORE ADMIN Interface ncacn_np:\\\\ACMESERVER[\\pipe\\B6AA47922DC89E00] UUID: a4f1db00-ca47-1067-b31e-00dd010662da Exchange Server STORE ADMIN Interface ncalrpc:[MSExchangeIS_LPC] UUID: a4f1db00-ca47-1067-b31e-00dd010662da Exchange Server STORE ADMIN Interface ncacn_ip_tcp:127.0.0.1[1233] UUID: a4f1db00-ca47-1067-b31e-00dd010662da Exchange Server STORE ADMIN Interface ncadg_ip_udp:127.0.0.1[1234] UUID: a4f1db00-ca47-1067-b31e-00dd010662da Exchange Server STORE ADMIN Interface ncacn_http:127.0.0.1[6001] UUID: 89742ace-a9ed-11cf-9c0c-08002be7ae86 Exchange Server STORE ADMIN Interface ncacn_np:\\\\ACMESERVER[\\pipe\\B6AA47922DC89E00] UUID: 89742ace-a9ed-11cf-9c0c-08002be7ae86 Exchange Server STORE ADMIN Interface ncalrpc:[MSExchangeIS_LPC] UUID: 89742ace-a9ed-11cf-9c0c-08002be7ae86 Exchange Server STORE ADMIN Interface ncacn_ip_tcp:127.0.0.1[1233] UUID: 89742ace-a9ed-11cf-9c0c-08002be7ae86 Exchange Server STORE ADMIN Interface ncadg_ip_udp:127.0.0.1[1234] UUID: 89742ace-a9ed-11cf-9c0c-08002be7ae86 Exchange Server STORE ADMIN Interface ncacn_http:127.0.0.1[6001] UUID: 99e64010-b032-11d0-97a4-00c04fd6551d Exchange Server STORE ADMIN Interface ncacn_np:\\\\ACMESERVER[\\pipe\\B6AA47922DC89E00] UUID: 99e64010-b032-11d0-97a4-00c04fd6551d Exchange Server STORE ADMIN Interface ncalrpc:[MSExchangeIS_LPC] UUID: 99e64010-b032-11d0-97a4-00c04fd6551d Exchange Server STORE ADMIN Interface ncacn_ip_tcp:127.0.0.1[1233] UUID: 99e64010-b032-11d0-97a4-00c04fd6551d Exchange Server STORE ADMIN Interface ncadg_ip_udp:127.0.0.1[1234] UUID: 99e64010-b032-11d0-97a4-00c04fd6551d Exchange Server STORE ADMIN Interface ncacn_http:127.0.0.1[6001] UUID: 99e64010-b032-11d0-97a4-00c04fd6551d Exchange Server STORE ADMIN Interface ncacn_np:\\\\ACMESERVER[\\pipe\\B6AA47922DC89E00] UUID: 99e64010-b032-11d0-97a4-00c04fd6551d Exchange Server STORE ADMIN Interface ncalrpc:[MSExchangeIS_LPC] UUID: 99e64010-b032-11d0-97a4-00c04fd6551d Exchange Server STORE ADMIN Interface ncacn_ip_tcp:127.0.0.1[1233] UUID: 99e64010-b032-11d0-97a4-00c04fd6551d Exchange Server STORE ADMIN Interface ncadg_ip_udp:127.0.0.1[1234] UUID: 99e64010-b032-11d0-97a4-00c04fd6551d Exchange Server STORE ADMIN Interface ncacn_http:127.0.0.1[6001] UUID: 10f24e8e-0fa6-11d2-a910-00c04f990f3b Microsoft Information Store ncacn_np:\\\\ACMESERVER[\\pipe\\B6AA47922DC89E00] UUID: 10f24e8e-0fa6-11d2-a910-00c04f990f3b Microsoft Information Store ncalrpc:[MSExchangeIS_LPC] UUID: 10f24e8e-0fa6-11d2-a910-00c04f990f3b Microsoft Information Store ncacn_ip_tcp:127.0.0.1[1233] UUID: 10f24e8e-0fa6-11d2-a910-00c04f990f3b Microsoft Information Store ncalrpc:[OLE4E34F54653054B32AE20C6078F2A] UUID: 1453c42c-0fa6-11d2-a910-00c04f990f3b Microsoft Information Store ncacn_np:\\\\ACMESERVER[\\pipe\\B6AA47922DC89E00] UUID: 1453c42c-0fa6-11d2-a910-00c04f990f3b Microsoft Information Store ncalrpc:[MSExchangeIS_LPC] UUID: 1453c42c-0fa6-11d2-a910-00c04f990f3b Microsoft Information Store ncacn_ip_tcp:127.0.0.1[1233] UUID: 1453c42c-0fa6-11d2-a910-00c04f990f3b Microsoft Information Store ncalrpc:[OLE4E34F54653054B32AE20C6078F2A] UUID: 0e4a0156-dd5d-11d2-8c2f-00c04fb6bcde Microsoft Information Store ncacn_np:\\\\ACMESERVER[\\pipe\\B6AA47922DC89E00] UUID: 0e4a0156-dd5d-11d2-8c2f-00c04fb6bcde Microsoft Information Store ncalrpc:[MSExchangeIS_LPC] UUID: 0e4a0156-dd5d-11d2-8c2f-00c04fb6bcde Microsoft Information Store ncacn_ip_tcp:127.0.0.1[1233] UUID: 0e4a0156-dd5d-11d2-8c2f-00c04fb6bcde Microsoft Information Store ncalrpc:[OLE4E34F54653054B32AE20C6078F2A] UUID: a4f1db00-ca47-1067-b31f-00dd010662da Exchange 2003 Server STORE EMSMDB Interface ncacn_np:\\\\ACMESERVER[\\pipe\\B6AA47922DC89E00] UUID: a4f1db00-ca47-1067-b31f-00dd010662da Exchange 2003 Server STORE EMSMDB Interface ncalrpc:[MSExchangeIS_LPC] UUID: a4f1db00-ca47-1067-b31f-00dd010662da Exchange 2003 Server STORE EMSMDB Interface ncacn_ip_tcp:127.0.0.1[1233] UUID: a4f1db00-ca47-1067-b31f-00dd010662da Exchange 2003 Server STORE EMSMDB Interface ncadg_ip_udp:127.0.0.1[1234] UUID: a4f1db00-ca47-1067-b31f-00dd010662da Exchange 2003 Server STORE EMSMDB Interface ncacn_http:127.0.0.1[6001] UUID: a4f1db00-ca47-1067-b31f-00dd010662da Exchange 2003 Server STORE EMSMDB Interface ncalrpc:[OLE4E34F54653054B32AE20C6078F2A] UUID: 50abc2a4-574d-40b3-9d66-ee4fd5fba076 ncacn_ip_tcp:127.0.0.1[1199] UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe ncalrpc:[OLED32A00C29F694DC7AB7BA1DA62EA] UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe ncacn_ip_tcp:127.0.0.1[1192] UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe ncalrpc:[LRPC00000928.00000001] UUID: 45f52c28-7f9f-101a-b52b-08002b2efabe ncacn_np:\\\\ACMESERVER[\\pipe\\WinsPipe] UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45 ncalrpc:[OLED32A00C29F694DC7AB7BA1DA62EA] UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45 ncacn_ip_tcp:127.0.0.1[1192] UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45 ncalrpc:[LRPC00000928.00000001] UUID: 811109bf-a4e1-11d1-ab54-00a0c91e9b45 ncacn_np:\\\\ACMESERVER[\\pipe\\WinsPipe] UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service ncalrpc:[OLE21E3D1CFD18848429EA8E19CCEBA] UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service ncacn_ip_tcp:127.0.0.1[1190] UUID: f5cc59b4-4264-101a-8c59-08002b2f8426 NtFrs Service ncalrpc:[LRPC00000780.00000001] UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API ncalrpc:[OLE21E3D1CFD18848429EA8E19CCEBA] UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API ncacn_ip_tcp:127.0.0.1[1190] UUID: d049b186-814f-11d1-9a3c-00c04fc9b232 NtFrs API ncalrpc:[LRPC00000780.00000001] UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE ncalrpc:[OLE21E3D1CFD18848429EA8E19CCEBA] UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE ncacn_ip_tcp:127.0.0.1[1190] UUID: a00c021c-2be2-11d2-b678-0000f87a8f8e PERFMON SERVICE ncalrpc:[LRPC00000780.00000001] UUID: 469d6ec0-0d87-11ce-b13f-00aa003bac6c MS Exchange System Attendant Public Interface ncacn_np:\\\\ACMESERVER[\\pipe\\1E2DD63E86E4D747] UUID: 469d6ec0-0d87-11ce-b13f-00aa003bac6c MS Exchange System Attendant Public Interface ncalrpc:[LRPC000009c8.00000001] UUID: 469d6ec0-0d87-11ce-b13f-00aa003bac6c MS Exchange System Attendant Public Interface ncacn_ip_tcp:127.0.0.1[1036] UUID: 469d6ec0-0d87-11ce-b13f-00aa003bac6c MS Exchange System Attendant Public Interface ncadg_ip_udp:127.0.0.1[1037] UUID: 469d6ec0-0d87-11ce-b13f-00aa003bac6c MS Exchange System Attendant Public Interface ncacn_http:127.0.0.1[6002] UUID: 83d72bf0-0d89-11ce-b13f-00aa003bac6c MS Exchange System Attendant Private Interface ncacn_np:\\\\ACMESERVER[\\pipe\\1E2DD63E86E4D747] UUID: 83d72bf0-0d89-11ce-b13f-00aa003bac6c MS Exchange System Attendant Private Interface ncalrpc:[LRPC000009c8.00000001] UUID: 83d72bf0-0d89-11ce-b13f-00aa003bac6c MS Exchange System Attendant Private Interface ncacn_ip_tcp:127.0.0.1[1036] UUID: 83d72bf0-0d89-11ce-b13f-00aa003bac6c MS Exchange System Attendant Private Interface ncadg_ip_udp:127.0.0.1[1037] UUID: 83d72bf0-0d89-11ce-b13f-00aa003bac6c MS Exchange System Attendant Private Interface ncacn_http:127.0.0.1[6002] UUID: f930c514-1215-11d3-99a5-00a0c9b61b04 MS Exchange System Attendant Cluster Interface ncacn_np:\\\\ACMESERVER[\\pipe\\1E2DD63E86E4D747] UUID: f930c514-1215-11d3-99a5-00a0c9b61b04 MS Exchange System Attendant Cluster Interface ncalrpc:[LRPC000009c8.00000001] UUID: f930c514-1215-11d3-99a5-00a0c9b61b04 MS Exchange System Attendant Cluster Interface ncacn_ip_tcp:127.0.0.1[1036] UUID: f930c514-1215-11d3-99a5-00a0c9b61b04 MS Exchange System Attendant Cluster Interface ncadg_ip_udp:127.0.0.1[1037] UUID: f930c514-1215-11d3-99a5-00a0c9b61b04 MS Exchange System Attendant Cluster Interface ncacn_http:127.0.0.1[6002] UUID: 1544f5e0-613c-11d1-93df-00c04fd7bd09 MS Exchange Directory RFR Interface ncacn_np:\\\\ACMESERVER[\\pipe\\1E2DD63E86E4D747] UUID: 1544f5e0-613c-11d1-93df-00c04fd7bd09 MS Exchange Directory RFR Interface ncalrpc:[LRPC000009c8.00000001] UUID: 1544f5e0-613c-11d1-93df-00c04fd7bd09 MS Exchange Directory RFR Interface ncacn_ip_tcp:127.0.0.1[1036] UUID: 1544f5e0-613c-11d1-93df-00c04fd7bd09 MS Exchange Directory RFR Interface ncadg_ip_udp:127.0.0.1[1037] UUID: 1544f5e0-613c-11d1-93df-00c04fd7bd09 MS Exchange Directory RFR Interface ncacn_http:127.0.0.1[6002] UUID: 82ad4280-036b-11cf-972c-00aa006887b0 ncalrpc:[OLEE19F3830869B42EABFD75350B112] UUID: 82ad4280-036b-11cf-972c-00aa006887b0 ncalrpc:[INETINFO_LPC] UUID: 82ad4280-036b-11cf-972c-00aa006887b0 ncalrpc:[KNETINFO_LPC] UUID: 82ad4280-036b-11cf-972c-00aa006887b0 ncacn_ip_tcp:127.0.0.1[1033] UUID: 82ad4280-036b-11cf-972c-00aa006887b0 ncacn_ip_tcp:127.0.0.1[1034] UUID: 82ad4280-036b-11cf-972c-00aa006887b0 ncacn_np:\\\\ACMESERVER[\\PIPE\\INETINFO] UUID: 97f83d5c-1994-11d1-a90d-00c04fb960f8 ncalrpc:[OLEE19F3830869B42EABFD75350B112] UUID: 97f83d5c-1994-11d1-a90d-00c04fb960f8 ncalrpc:[INETINFO_LPC] UUID: 97f83d5c-1994-11d1-a90d-00c04fb960f8 ncalrpc:[KNETINFO_LPC] UUID: 97f83d5c-1994-11d1-a90d-00c04fb960f8 ncacn_ip_tcp:127.0.0.1[1033] UUID: 97f83d5c-1994-11d1-a90d-00c04fb960f8 ncacn_ip_tcp:127.0.0.1[1034] UUID: 97f83d5c-1994-11d1-a90d-00c04fb960f8 ncacn_np:\\\\ACMESERVER[\\PIPE\\INETINFO] UUID: 97f83d5c-1994-11d1-a90d-00c04fb960f8 ncacn_np:\\\\ACMESERVER[\\PIPE\\KNETINFO] UUID: a520d06e-11de-11d2-ab59-00c04fa3590c ncalrpc:[OLEE19F3830869B42EABFD75350B112] UUID: a520d06e-11de-11d2-ab59-00c04fa3590c ncalrpc:[INETINFO_LPC] UUID: a520d06e-11de-11d2-ab59-00c04fa3590c ncalrpc:[KNETINFO_LPC] UUID: a520d06e-11de-11d2-ab59-00c04fa3590c ncacn_ip_tcp:127.0.0.1[1033] UUID: a520d06e-11de-11d2-ab59-00c04fa3590c ncacn_ip_tcp:127.0.0.1[1034] UUID: a520d06e-11de-11d2-ab59-00c04fa3590c ncacn_np:\\\\ACMESERVER[\\PIPE\\INETINFO] UUID: a520d06e-11de-11d2-ab59-00c04fa3590c ncacn_np:\\\\ACMESERVER[\\PIPE\\KNETINFO] UUID: a520d06e-11de-11d2-ab59-00c04fa3590c ncalrpc:[RESVC_LPC] UUID: a520d06e-11de-11d2-ab59-00c04fa3590c ncacn_ip_tcp:127.0.0.1[1035] UUID: a520d06e-11de-11d2-ab59-00c04fa3590c ncacn_np:\\\\ACMESERVER[\\PIPE\\RESVC] UUID: 8cfb5d70-31a4-11cf-a7d8-00805f48a135 ncalrpc:[OLEE19F3830869B42EABFD75350B112] UUID: 8cfb5d70-31a4-11cf-a7d8-00805f48a135 ncalrpc:[INETINFO_LPC] UUID: 8cfb5d70-31a4-11cf-a7d8-00805f48a135 ncalrpc:[KNETINFO_LPC] UUID: 8cfb5d70-31a4-11cf-a7d8-00805f48a135 ncacn_ip_tcp:127.0.0.1[1033] UUID: 8cfb5d70-31a4-11cf-a7d8-00805f48a135 ncacn_ip_tcp:127.0.0.1[1034] UUID: 8cfb5d70-31a4-11cf-a7d8-00805f48a135 ncacn_np:\\\\ACMESERVER[\\PIPE\\INETINFO] UUID: 8cfb5d70-31a4-11cf-a7d8-00805f48a135 ncacn_np:\\\\ACMESERVER[\\PIPE\\KNETINFO] UUID: 8cfb5d70-31a4-11cf-a7d8-00805f48a135 ncalrpc:[RESVC_LPC] UUID: 8cfb5d70-31a4-11cf-a7d8-00805f48a135 ncacn_ip_tcp:127.0.0.1[1035] UUID: 8cfb5d70-31a4-11cf-a7d8-00805f48a135 ncacn_np:\\\\ACMESERVER[\\PIPE\\RESVC] UUID: 8cfb5d70-31a4-11cf-a7d8-00805f48a135 ncalrpc:[SMTPSVC_LPC] UUID: 8cfb5d70-31a4-11cf-a7d8-00805f48a135 ncacn_ip_tcp:127.0.0.1[1038] UUID: 8cfb5d70-31a4-11cf-a7d8-00805f48a135 ncacn_np:\\\\ACMESERVER[\\PIPE\\SMTPSVC] UUID: bfa951d1-2f0e-11d3-bfd1-00c04fa3490a ncalrpc:[OLEE19F3830869B42EABFD75350B112] UUID: bfa951d1-2f0e-11d3-bfd1-00c04fa3490a ncalrpc:[INETINFO_LPC] UUID: bfa951d1-2f0e-11d3-bfd1-00c04fa3490a ncalrpc:[KNETINFO_LPC] UUID: bfa951d1-2f0e-11d3-bfd1-00c04fa3490a ncacn_ip_tcp:127.0.0.1[1033] UUID: bfa951d1-2f0e-11d3-bfd1-00c04fa3490a ncacn_ip_tcp:127.0.0.1[1034] UUID: bfa951d1-2f0e-11d3-bfd1-00c04fa3490a ncacn_np:\\\\ACMESERVER[\\PIPE\\INETINFO] UUID: bfa951d1-2f0e-11d3-bfd1-00c04fa3490a ncacn_np:\\\\ACMESERVER[\\PIPE\\KNETINFO] UUID: bfa951d1-2f0e-11d3-bfd1-00c04fa3490a ncalrpc:[RESVC_LPC] UUID: bfa951d1-2f0e-11d3-bfd1-00c04fa3490a ncacn_ip_tcp:127.0.0.1[1035] UUID: bfa951d1-2f0e-11d3-bfd1-00c04fa3490a ncacn_np:\\\\ACMESERVER[\\PIPE\\RESVC] UUID: bfa951d1-2f0e-11d3-bfd1-00c04fa3490a ncalrpc:[SMTPSVC_LPC] UUID: bfa951d1-2f0e-11d3-bfd1-00c04fa3490a ncacn_ip_tcp:127.0.0.1[1038] UUID: bfa951d1-2f0e-11d3-bfd1-00c04fa3490a ncacn_np:\\\\ACMESERVER[\\PIPE\\SMTPSVC] UUID: bfa951d1-2f0e-11d3-bfd1-00c04fa3490a ncacn_np:\\\\ACMESERVER[\\pipe\\395FCB9B3BC77147] UUID: bfa951d1-2f0e-11d3-bfd1-00c04fa3490a ncalrpc:[LRPC00000664.00000001] UUID: bfa951d1-2f0e-11d3-bfd1-00c04fa3490a ncacn_ip_tcp:127.0.0.1[1041] UUID: bfa951d1-2f0e-11d3-bfd1-00c04fa3490a ncadg_ip_udp:127.0.0.1[1042] UUID: 342cfd40-3c6c-11ce-a893-08002b2e9c6d License Logging Server llsrpc Endpoint ncalrpc:[llslpc] UUID: 342cfd40-3c6c-11ce-a893-08002b2e9c6d License Logging Server llsrpc Endpoint ncacn_np:\\\\ACMESERVER[\\pipe\\llsrpc] UUID: 57674cd0-5200-11ce-a897-08002b2e9c6d License Logging Server lsapirpc Endpoint ncalrpc:[llslpc] UUID: 57674cd0-5200-11ce-a897-08002b2e9c6d License Logging Server lsapirpc Endpoint ncacn_np:\\\\ACMESERVER[\\pipe\\llsrpc] UUID: 906b0ce0-c70b-1067-b317-00dd010662da ncalrpc:[LRPC000004d8.00000001] UUID: 906b0ce0-c70b-1067-b317-00dd010662da ncalrpc:[LRPC000004d8.00000001] UUID: 906b0ce0-c70b-1067-b317-00dd010662da ncalrpc:[LRPC000004d8.00000001] UUID: 906b0ce0-c70b-1067-b317-00dd010662da ncalrpc:[LRPC000004d8.00000001] UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface ncacn_np:\\\\ACMESERVER[\\PIPE\\lsass] UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface ncalrpc:[audit] UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface ncalrpc:[securityevent] UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface ncalrpc:[protected_storage] UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface ncacn_np:\\\\ACMESERVER[\\PIPE\\protected_storage] UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface ncalrpc:[dsrole] UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface ncacn_ip_tcp:127.0.0.1[1025] UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface ncalrpc:[NTDS_LPC] UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface ncacn_http:127.0.0.1[1027] UUID: e3514235-4b06-11d1-ab04-00c04fc2dcd2 MS NT Directory DRS Interface ncacn_http:127.0.0.1[6004] UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface ncacn_np:\\\\ACMESERVER[\\PIPE\\lsass] UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface ncalrpc:[audit] UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface ncalrpc:[securityevent] UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface ncalrpc:[protected_storage] UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface ncacn_np:\\\\ACMESERVER[\\PIPE\\protected_storage] UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface ncalrpc:[dsrole] UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface ncacn_ip_tcp:127.0.0.1[1025] UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface ncalrpc:[NTDS_LPC] UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface ncacn_http:127.0.0.1[1027] UUID: f5cc5a18-4264-101a-8c59-08002b2f8426 MS NT Directory NSP Interface ncacn_http:127.0.0.1[6004] UUID: 12345778-1234-abcd-ef00-0123456789ab ncacn_np:\\\\ACMESERVER[\\PIPE\\lsass] UUID: 12345778-1234-abcd-ef00-0123456789ab ncalrpc:[audit] UUID: 12345778-1234-abcd-ef00-0123456789ab ncalrpc:[securityevent] UUID: 12345778-1234-abcd-ef00-0123456789ab ncalrpc:[protected_storage] UUID: 12345778-1234-abcd-ef00-0123456789ab ncacn_np:\\\\ACMESERVER[\\PIPE\\protected_storage] UUID: 12345778-1234-abcd-ef00-0123456789ab ncalrpc:[dsrole] UUID: 12345778-1234-abcd-ef00-0123456789ab ncacn_ip_tcp:127.0.0.1[1025] UUID: 12345778-1234-abcd-ef00-0123456789ab ncalrpc:[NTDS_LPC] UUID: 12345778-1234-abcd-ef00-0123456789ab ncacn_http:127.0.0.1[1027] UUID: 12345778-1234-abcd-ef00-0123456789ab ncacn_http:127.0.0.1[6004] UUID: 12345778-1234-abcd-ef00-0123456789ac ncacn_np:\\\\ACMESERVER[\\PIPE\\lsass] UUID: 12345778-1234-abcd-ef00-0123456789ac ncalrpc:[audit] UUID: 12345778-1234-abcd-ef00-0123456789ac ncalrpc:[securityevent] UUID: 12345778-1234-abcd-ef00-0123456789ac ncalrpc:[protected_storage] UUID: 12345778-1234-abcd-ef00-0123456789ac ncacn_np:\\\\ACMESERVER[\\PIPE\\protected_storage] UUID: 12345778-1234-abcd-ef00-0123456789ac ncalrpc:[dsrole] UUID: 12345778-1234-abcd-ef00-0123456789ac ncacn_ip_tcp:127.0.0.1[1025] UUID: 12345778-1234-abcd-ef00-0123456789ac ncalrpc:[NTDS_LPC] UUID: 12345778-1234-abcd-ef00-0123456789ac ncacn_http:127.0.0.1[1027] UUID: 12345778-1234-abcd-ef00-0123456789ac ncacn_http:127.0.0.1[6004] UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface ncacn_np:\\\\ACMESERVER[\\PIPE\\lsass] UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface ncalrpc:[audit] UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface ncalrpc:[securityevent] UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface ncalrpc:[protected_storage] UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface ncacn_np:\\\\ACMESERVER[\\PIPE\\protected_storage] UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface ncalrpc:[dsrole] UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface ncacn_ip_tcp:127.0.0.1[1025] UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface ncalrpc:[NTDS_LPC] UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface ncacn_http:127.0.0.1[1027] UUID: ecec0d70-a603-11d0-96b1-00a0c91ece30 NTDS Backup Interface ncacn_http:127.0.0.1[6004] UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface ncacn_np:\\\\ACMESERVER[\\PIPE\\lsass] UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface ncalrpc:[audit] UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface ncalrpc:[securityevent] UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface ncalrpc:[protected_storage] UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface ncacn_np:\\\\ACMESERVER[\\PIPE\\protected_storage] UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface ncalrpc:[dsrole] UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface ncacn_ip_tcp:127.0.0.1[1025] UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface ncalrpc:[NTDS_LPC] UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface ncacn_http:127.0.0.1[1027] UUID: 16e0cf3a-a604-11d0-96b1-00a0c91ece30 NTDS Restore Interface ncacn_http:127.0.0.1[6004] UUID: 12345678-1234-abcd-ef00-01234567cffb ncacn_np:\\\\ACMESERVER[\\PIPE\\lsass] UUID: 12345678-1234-abcd-ef00-01234567cffb ncalrpc:[audit] UUID: 12345678-1234-abcd-ef00-01234567cffb ncalrpc:[securityevent] UUID: 12345678-1234-abcd-ef00-01234567cffb ncalrpc:[protected_storage] UUID: 12345678-1234-abcd-ef00-01234567cffb ncacn_np:\\\\ACMESERVER[\\PIPE\\protected_storage] UUID: 12345678-1234-abcd-ef00-01234567cffb ncalrpc:[dsrole] UUID: 12345678-1234-abcd-ef00-01234567cffb ncacn_ip_tcp:127.0.0.1[1025] UUID: 12345678-1234-abcd-ef00-01234567cffb ncalrpc:[NTDS_LPC] UUID: 12345678-1234-abcd-ef00-01234567cffb ncacn_http:127.0.0.1[1027] UUID: 12345678-1234-abcd-ef00-01234567cffb ncacn_http:127.0.0.1[6004] UUID: 12345678-1234-abcd-ef00-01234567cffb ncalrpc:[OLE22DBE5F51D09422F977C43896C94] UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint ncacn_np:\\\\ACMESERVER[\\PIPE\\lsass] UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint ncalrpc:[audit] UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint ncalrpc:[securityevent] UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint ncalrpc:[protected_storage] UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint ncacn_np:\\\\ACMESERVER[\\PIPE\\protected_storage] UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint ncalrpc:[dsrole] UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint ncacn_ip_tcp:127.0.0.1[1025] UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint ncalrpc:[NTDS_LPC] UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint ncacn_http:127.0.0.1[1027] UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint ncacn_http:127.0.0.1[6004] UUID: 12345678-1234-abcd-ef00-0123456789ab IPSec Policy agent endpoint ncalrpc:[OLE22DBE5F51D09422F977C43896C94] UUID: 1ff70682-0a51-30e8-076d-740be8cee98b ncalrpc:[OLE2A5B433581924049A7921863F6BD] UUID: 1ff70682-0a51-30e8-076d-740be8cee98b ncalrpc:[LRPC00000374.00000001] UUID: 1ff70682-0a51-30e8-076d-740be8cee98b ncacn_np:\\\\ACMESERVER[\\PIPE\\atsvc] UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f ncalrpc:[OLE2A5B433581924049A7921863F6BD] UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f ncalrpc:[LRPC00000374.00000001] UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f ncacn_np:\\\\ACMESERVER[\\PIPE\\atsvc] UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53 ncalrpc:[OLE2A5B433581924049A7921863F6BD] UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53 ncalrpc:[LRPC00000374.00000001] UUID: 0a74ef1c-41a4-4e06-83ae-dc74fb1cdd53 ncacn_np:\\\\ACMESERVER[\\PIPE\\atsvc] UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint ncalrpc:[dhcpcsvc] Total endpoints found: 243 ==== 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 ACMESERVER.acme1 querying... TCP port 389 (ldap service): LISTENING Using ephemeral source port Sending LDAP query to TCP port 389... LDAP query response: currentdate: 06/12/2011 16:46:48 (unadjusted GMT) subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=acmefitness,DC=local dsServiceName: CN=NTDS Settings,CN=ACMESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=acmefitness,DC=local namingContexts: DC=acmefitness,DC=local defaultNamingContext: DC=acmefitness,DC=local schemaNamingContext: CN=Schema,CN=Configuration,DC=acmefitness,DC=local configurationNamingContext: CN=Configuration,DC=acmefitness,DC=local rootDomainNamingContext: DC=acmefitness,DC=local supportedControl: 1.2.840.113556.1.4.319 supportedLDAPVersion: 3 supportedLDAPPolicies: MaxPoolThreads highestCommittedUSN: 371630 supportedSASLMechanisms: GSSAPI dnsHostName: ACMESERVER.acme1 ldapServiceName: acmefitness.local:acmeserver$@ACMEFITNESS.LOCAL serverName: CN=ACMESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=acmefitness,DC=local supportedCapabilities: 1.2.840.113556.1.4.800 isSynchronized: TRUE isGlobalCatalogReady: TRUE domainFunctionality: 0 forestFunctionality: 0 domainControllerFunctionality: 2 ======== End of LDAP query response ======== UDP port 389 (unknown service): NOT LISTENING portqry.exe -n 127.0.0.1 -e 389 -p BOTH exits with return code 0x00000001. ============================================= 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 ACMESERVER.acme1 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 ACMESERVER.acme1 querying... TCP port 3268 (msft-gc service): LISTENING Using ephemeral source port Sending LDAP query to TCP port 3268... LDAP query response: currentdate: 06/12/2011 16:46:48 (unadjusted GMT) subschemaSubentry: CN=Aggregate,CN=Schema,CN=Configuration,DC=acmefitness,DC=local dsServiceName: CN=NTDS Settings,CN=ACMESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=acmefitness,DC=local namingContexts: DC=acmefitness,DC=local defaultNamingContext: DC=acmefitness,DC=local schemaNamingContext: CN=Schema,CN=Configuration,DC=acmefitness,DC=local configurationNamingContext: CN=Configuration,DC=acmefitness,DC=local rootDomainNamingContext: DC=acmefitness,DC=local supportedControl: 1.2.840.113556.1.4.319 supportedLDAPVersion: 3 supportedLDAPPolicies: MaxPoolThreads highestCommittedUSN: 371630 supportedSASLMechanisms: GSSAPI dnsHostName: ACMESERVER.acme1 ldapServiceName: acmefitness.local:acmeserver$@ACMEFITNESS.LOCAL serverName: CN=ACMESERVER,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=acmefitness,DC=local supportedCapabilities: 1.2.840.113556.1.4.800 isSynchronized: TRUE isGlobalCatalogReady: TRUE domainFunctionality: 0 forestFunctionality: 0 domainControllerFunctionality: 2 ======== 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 ACMESERVER.acme1 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 ACMESERVER.acme1 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 ACMESERVER.acme1 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 ACMESERVER.acme1 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 ACMESERVER.acme1 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. ============================================= Star

nltest outputs: sc_query failed nltest output from DC/DNS 192.168.1.42 - nltest /dsgetsite Default-First-Site-Name The command completed successfully - nltest /dsgetdc: DC: \\ACMESERVER Address: \\192.168.1.42 Dom Guid: e62d9ae3-8490-4c97-8ba1-8d391a445d52 Dom Name: ACMEFITNESS Forest Name: acmefitness.local Dc Site Name: Default-First-Site-Name Our Site Name: Default-First-Site-Name Flags: PDC GC DS LDAP KDC TIMESERV WRITABLE DNS_FOREST CLOSE_SITE The command completed successfully - nltest /sc_query:acmefitness I_NetLogonControl failed: Status = 1355 0x54b ERROR_NO_SUCH_DOMAIN - nltest /dclist: Get list of DCs in domain 'acmefitness' from '\\ACMESERVER'. ACMESERVER.acme1 [PDC] [DS] Site: Default-First-Site-Name The command completed successfully

portion of netdiag output, there are errors here clearly I have not got the DNS setup like I thought I did, just where (and what) do I change. The non .42 ip's are wrong, right? --------------------------------------------------------------------------------------------------------- DNS test . . . . . . . . . . . . . : Failed Interface {8D77C091-32B3-4580-9F22-C7009660C9CC} DNS Domain: DNS Servers: 192.168.1.42 IP Address: Expected registration with PDN (primary DNS domain name): Hostname: ACMESERVER.acme1. [WARNING] Cannot find a primary authoritative DNS server for the name 'ACMESERVER.acme1.'. [RCODE_SERVER_FAILURE] The name 'ACMESERVER.acme1.' may not be registered in DNS. Check the DNS registration for DCs entries on DNS server '192.168.1.42' ********** * ********** * ********** * ********** * ********** * * CHECK NAME acmefitness.local. on DNS server 192.168.1.42 ********** * ********** * ********** * ********** * ********** * The Record is correct on DNS server '192.168.1.42'. ********** * ********** * ********** * ********** * ********** * * CHECK NAME _ldap._tcp.acmefitness.local. on DNS server 192.168.1.42 ********** * ********** * ********** * ********** * ********** * The Record is different on DNS server '192.168.1.42'. +------------------------------------------------------+ The record on your DC is: DNS NAME = _ldap._tcp.acmefitness.local. DNS DATA = SRV 0 100 389 ACMESERVER.acme1. The record on DNS server 192.168.1.42 is: DNS NAME = _ldap._tcp.acmefitness.local DNS DATA = SRV 0 100 389 acmeserver.acmefitness.local +------------------------------------------------------+ ********** * ********** * ********** * ********** * ********** * * CHECK NAME _ldap._tcp.Default-First-Site-Name._sites.acmefitness.local. on DNS server 192.168.1.42 ********** * ********** * ********** * ********** * ********** * The Record is different on DNS server '192.168.1.42'. +------------------------------------------------------+ The record on your DC is: DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.acmefitness.local. DNS DATA = SRV 0 100 389 ACMESERVER.acme1. The record on DNS server 192.168.1.42 is: DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.acmefitness.local DNS DATA = SRV 0 100 389 acmeserver.acmefitness.local +------------------------------------------------------+ ********** * ********** * ********** * ********** * ********** * * CHECK NAME _ldap._tcp.pdc._msdcs.acmefitness.local. on DNS server 192.168.1.42 ********** * ********** * ********** * ********** * ********** * The Record is different on DNS server '192.168.1.42'. +------------------------------------------------------+ The record on your DC is: DNS NAME = _ldap._tcp.pdc._msdcs.acmefitness.local. DNS DATA = SRV 0 100 389 ACMESERVER.acme1. The record on DNS server 192.168.1.42 is: DNS NAME = _ldap._tcp.pdc._msdcs.acmefitness.local DNS DATA = SRV 0 100 389 acmeserver.acmefitness.local +------------------------------------------------------+ ********** * ********** * ********** * ********** * ********** * * CHECK NAME _ldap._tcp.gc._msdcs.acmefitness.local. on DNS server 192.168.1.42 ********** * ********** * ********** * ********** * ********** * The Record is different on DNS server '192.168.1.42'. +------------------------------------------------------+ The record on your DC is: DNS NAME = _ldap._tcp.gc._msdcs.acmefitness.local. DNS DATA = SRV 0 100 3268 ACMESERVER.acme1. The record on DNS server 192.168.1.42 is: DNS NAME = _ldap._tcp.gc._msdcs.acmefitness.local DNS DATA = SRV 0 100 3268 acmeserver.acmefitness.local +------------------------------------------------------+ ********** * ********** * ********** * ********** * ********** * * CHECK NAME _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.acmefitness.local. on DNS server 192.168.1.42 ********** * ********** * ********** * ********** * ********** * The Record is different on DNS server '192.168.1.42'. +------------------------------------------------------+ The record on your DC is: DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.acmefitness.local. DNS DATA = SRV 0 100 3268 ACMESERVER.acme1. The record on DNS server 192.168.1.42 is: DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.acmefitness.local DNS DATA = SRV 0 100 3268 acmeserver.acmefitness.local +------------------------------------------------------+ ********** * ********** * ********** * ********** * ********** * * CHECK NAME _ldap._tcp.e62d9ae3-8490-4c97-8ba1-8d391a445d52.domains._msdcs.acmefitness.local. on DNS server 192.168.1.42 ********** * ********** * ********** * ********** * ********** * The Record is different on DNS server '192.168.1.42'. +------------------------------------------------------+ The record on your DC is: DNS NAME = _ldap._tcp.e62d9ae3-8490-4c97-8ba1-8d391a445d52.domains._msdcs.acmefitness.local. DNS DATA = SRV 0 100 389 ACMESERVER.acme1. The record on DNS server 192.168.1.42 is: DNS NAME = _ldap._tcp.e62d9ae3-8490-4c97-8ba1-8d391a445d52.domains._msdcs.acmefitness.local DNS DATA = SRV 0 100 389 acmeserver.acmefitness.local +------------------------------------------------------+ ********** * ********** * ********** * ********** * ********** * * CHECK NAME gc._msdcs.acmefitness.local. on DNS server 192.168.1.42 ********** * ********** * ********** * ********** * ********** * The Record is different on DNS server '192.168.1.42'. +------------------------------------------------------+ The record on your DC is: DNS NAME = gc._msdcs.acmefitness.local. DNS DATA = A 192.168.1.42 The record on DNS server 192.168.1.42 is: DNS NAME = gc._msdcs.acmefitness.local DNS DATA = A 192.168.1.160 A 192.168.1.159 +------------------------------------------------------+ ********** * ********** * ********** * ********** * ********** * * CHECK NAME 85b2bbf3-b667-441f-bdfa-63d7ac3c3734._msdcs.acmefitness.local. on DNS server 192.168.1.42 ********** * ********** * ********** * ********** * ********** * The Record is different on DNS server '192.168.1.42'. +------------------------------------------------------+ The record on your DC is: DNS NAME = 85b2bbf3-b667-441f-bdfa-63d7ac3c3734._msdcs.acmefitness.local. DNS DATA = CNAME ACMESERVER.acme1. The record on DNS server 192.168.1.42 is: DNS NAME = 85b2bbf3-b667-441f-bdfa-63d7ac3c3734._msdcs.acmefitness.local DNS DATA = CNAME acmeserver.acmefitness.local +------------------------------------------------------+ ********** * ********** * ********** * ********** * ********** * * CHECK NAME _kerberos._tcp.dc._msdcs.acmefitness.local. on DNS server 192.168.1.42 ********** * ********** * ********** * ********** * ********** * The Record is different on DNS server '192.168.1.42'. +------------------------------------------------------+ The record on your DC is: DNS NAME = _kerberos._tcp.dc._msdcs.acmefitness.local. DNS DATA = SRV 0 100 88 ACMESERVER.acme1. The record on DNS server 192.168.1.42 is: DNS NAME = _kerberos._tcp.dc._msdcs.acmefitness.local DNS DATA = SRV 0 100 88 acmeserver.acmefitness.local +------------------------------------------------------+ ********** * ********** * ********** * ********** * ********** * * CHECK NAME _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.acmefitness.local. on DNS server 192.168.1.42 ********** * ********** * ********** * ********** * ********** * The Record is different on DNS server '192.168.1.42'. +------------------------------------------------------+ The record on your DC is: DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.acmefitness.local. DNS DATA = SRV 0 100 88 ACMESERVER.acme1. The record on DNS server 192.168.1.42 is: DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.acmefitness.local DNS DATA = SRV 0 100 88 acmeserver.acmefitness.local +------------------------------------------------------+ ********** * ********** * ********** * ********** * ********** * * CHECK NAME _ldap._tcp.dc._msdcs.acmefitness.local. on DNS server 192.168.1.42 ********** * ********** * ********** * ********** * ********** * The Record is different on DNS server '192.168.1.42'. +------------------------------------------------------+ The record on your DC is: DNS NAME = _ldap._tcp.dc._msdcs.acmefitness.local. DNS DATA = SRV 0 100 389 ACMESERVER.acme1. The record on DNS server 192.168.1.42 is: DNS NAME = _ldap._tcp.dc._msdcs.acmefitness.local DNS DATA = SRV 0 100 389 acmeserver.acmefitness.local +------------------------------------------------------+ ********** * ********** * ********** * ********** * ********** * * CHECK NAME _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.acmefitness.local. on DNS server 192.168.1.42 ********** * ********** * ********** * ********** * ********** * The Record is different on DNS server '192.168.1.42'. +------------------------------------------------------+ The record on your DC is: DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.acmefitness.local. DNS DATA = SRV 0 100 389 ACMESERVER.acme1. The record on DNS server 192.168.1.42 is: DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.acmefitness.local DNS DATA = SRV 0 100 389 acmeserver.acmefitness.local +------------------------------------------------------+ ********** * ********** * ********** * ********** * ********** * * CHECK NAME _kerberos._tcp.acmefitness.local. on DNS server 192.168.1.42 ********** * ********** * ********** * ********** * ********** * The Record is different on DNS server '192.168.1.42'. +------------------------------------------------------+ The record on your DC is: DNS NAME = _kerberos._tcp.acmefitness.local. DNS DATA = SRV 0 100 88 ACMESERVER.acme1. The record on DNS server 192.168.1.42 is: DNS NAME = _kerberos._tcp.acmefitness.local DNS DATA = SRV 0 100 88 acmeserver.acmefitness.local +------------------------------------------------------+ ********** * ********** * ********** * ********** * ********** * * CHECK NAME _kerberos._tcp.Default-First-Site-Name._sites.acmefitness.local. on DNS server 192.168.1.42 ********** * ********** * ********** * ********** * ********** * The Record is different on DNS server '192.168.1.42'. +------------------------------------------------------+ The record on your DC is: DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.acmefitness.local. DNS DATA = SRV 0 100 88 ACMESERVER.acme1. The record on DNS server 192.168.1.42 is: DNS NAME = _kerberos._tcp.Default-First-Site-Name._sites.acmefitness.local DNS DATA = SRV 0 100 88 acmeserver.acmefitness.local +------------------------------------------------------+ ********** * ********** * ********** * ********** * ********** * * CHECK NAME _gc._tcp.acmefitness.local. on DNS server 192.168.1.42 ********** * ********** * ********** * ********** * ********** * The Record is different on DNS server '192.168.1.42'. +------------------------------------------------------+ The record on your DC is: DNS NAME = _gc._tcp.acmefitness.local. DNS DATA = SRV 0 100 3268 ACMESERVER.acme1. The record on DNS server 192.168.1.42 is: DNS NAME = _gc._tcp.acmefitness.local DNS DATA = SRV 0 100 3268 acmeserver.acmefitness.local +------------------------------------------------------+ ********** * ********** * ********** * ********** * ********** * * CHECK NAME _gc._tcp.Default-First-Site-Name._sites.acmefitness.local. on DNS server 192.168.1.42 ********** * ********** * ********** * ********** * ********** * The Record is different on DNS server '192.168.1.42'. +------------------------------------------------------+ The record on your DC is: DNS NAME = _gc._tcp.Default-First-Site-Name._sites.acmefitness.local. DNS DATA = SRV 0 100 3268 ACMESERVER.acme1. The record on DNS server 192.168.1.42 is: DNS NAME = _gc._tcp.Default-First-Site-Name._sites.acmefitness.local DNS DATA = SRV 0 100 3268 acmeserver.acmefitness.local +------------------------------------------------------+ ********** * ********** * ********** * ********** * ********** * * CHECK NAME _kerberos._udp.acmefitness.local. on DNS server 192.168.1.42 ********** * ********** * ********** * ********** * ********** * The Record is different on DNS server '192.168.1.42'. +------------------------------------------------------+ The record on your DC is: DNS NAME = _kerberos._udp.acmefitness.local. DNS DATA = SRV 0 100 88 ACMESERVER.acme1. The record on DNS server 192.168.1.42 is: DNS NAME = _kerberos._udp.acmefitness.local DNS DATA = SRV 0 100 88 acmeserver.acmefitness.local +------------------------------------------------------+ ********** * ********** * ********** * ********** * ********** * * CHECK NAME _kpasswd._tcp.acmefitness.local. on DNS server 192.168.1.42 ********** * ********** * ********** * ********** * ********** * The Record is different on DNS server '192.168.1.42'. +------------------------------------------------------+ The record on your DC is: DNS NAME = _kpasswd._tcp.acmefitness.local. DNS DATA = SRV 0 100 464 ACMESERVER.acme1. The record on DNS server 192.168.1.42 is: DNS NAME = _kpasswd._tcp.acmefitness.local DNS DATA = SRV 0 100 464 acmeserver.acmefitness.local +------------------------------------------------------+ ********** * ********** * ********** * ********** * ********** * * CHECK NAME _kpasswd._udp.acmefitness.local. on DNS server 192.168.1.42 ********** * ********** * ********** * ********** * ********** * The Record is different on DNS server '192.168.1.42'. +------------------------------------------------------+ The record on your DC is: DNS NAME = _kpasswd._udp.acmefitness.local. DNS DATA = SRV 0 100 464 ACMESERVER.acme1. The record on DNS server 192.168.1.42 is: DNS NAME = _kpasswd._udp.acmefitness.local DNS DATA = SRV 0 100 464 acmeserver.acmefitness.local +------------------------------------------------------+ ********** * ********** * ********** * ********** * ********** * * CHECK NAME ForestDnsZones.acmefitness.local. on DNS server 192.168.1.42 ********** * ********** * ********** * ********** * ********** * The Record is different on DNS server '192.168.1.42'. DNS server has more than one entries for this name, usually this means there are multiple DCs for this domain. Your DC entry is one of them on DNS server '192.168.1.42', no need to re-register. +------------------------------------------------------+ The record on your DC is: DNS NAME = ForestDnsZones.acmefitness.local. DNS DATA = A 192.168.1.42 The record on DNS server 192.168.1.42 is: DNS NAME = ForestDnsZones.acmefitness.local DNS DATA = A 192.168.1.159 A 192.168.1.42 +------------------------------------------------------+ ********** * ********** * ********** * ********** * ********** * * CHECK NAME _ldap._tcp.ForestDnsZones.acmefitness.local. on DNS server 192.168.1.42 ********** * ********** * ********** * ********** * ********** * The Record is different on DNS server '192.168.1.42'. +------------------------------------------------------+ The record on your DC is: DNS NAME = _ldap._tcp.ForestDnsZones.acmefitness.local. DNS DATA = SRV 0 100 389 ACMESERVER.acme1. The record on DNS server 192.168.1.42 is: DNS NAME = _ldap._tcp.ForestDnsZones.acmefitness.local DNS DATA = SRV 0 100 389 acmeserver.acmefitness.local +------------------------------------------------------+ ********** * ********** * ********** * ********** * ********** * * CHECK NAME _ldap._tcp.Default-First-Site-Name._sites.ForestDnsZones.acmefitness.local. on DNS server 192.168.1.42 ********** * ********** * ********** * ********** * ********** * The Record is different on DNS server '192.168.1.42'. +------------------------------------------------------+ The record on your DC is: DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.ForestDnsZones.acmefitness.local. DNS DATA = SRV 0 100 389 ACMESERVER.acme1. The record on DNS server 192.168.1.42 is: DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.ForestDnsZones.acmefitness.local DNS DATA = SRV 0 100 389 acmeserver.acmefitness.local +------------------------------------------------------+ ********** * ********** * ********** * ********** * ********** * * CHECK NAME DomainDnsZones.acmefitness.local. on DNS server 192.168.1.42 ********** * ********** * ********** * ********** * ********** * The Record is different on DNS server '192.168.1.42'. +------------------------------------------------------+ The record on your DC is: DNS NAME = DomainDnsZones.acmefitness.local. DNS DATA = A 192.168.1.42 The record on DNS server 192.168.1.42 is: DNS NAME = DomainDnsZones.acmefitness.local DNS DATA = A 192.168.1.160 A 192.168.1.159 +------------------------------------------------------+ ********** * ********** * ********** * ********** * ********** * * CHECK NAME _ldap._tcp.DomainDnsZones.acmefitness.local. on DNS server 192.168.1.42 ********** * ********** * ********** * ********** * ********** * The Record is different on DNS server '192.168.1.42'. +------------------------------------------------------+ The record on your DC is: DNS NAME = _ldap._tcp.DomainDnsZones.acmefitness.local. DNS DATA = SRV 0 100 389 ACMESERVER.acme1. The record on DNS server 192.168.1.42 is: DNS NAME = _ldap._tcp.DomainDnsZones.acmefitness.local DNS DATA = SRV 0 100 389 acmeserver.acmefitness.local +------------------------------------------------------+ ********** * ********** * ********** * ********** * ********** * * CHECK NAME _ldap._tcp.Default-First-Site-Name._sites.DomainDnsZones.acmefitness.local. on DNS server 192.168.1.42 ********** * ********** * ********** * ********** * ********** * The Record is different on DNS server '192.168.1.42'. +------------------------------------------------------+ The record on your DC is: DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.DomainDnsZones.acmefitness.local. DNS DATA = SRV 0 100 389 ACMESERVER.acme1. The record on DNS server 192.168.1.42 is: DNS NAME = _ldap._tcp.Default-First-Site-Name._sites.DomainDnsZones.acmefitness.local DNS DATA = SRV 0 100 389 acmeserver.acmefitness.local +------------------------------------------------------+ ** ** Check DC DNS NAME FINAL RESULT ** ** [WARNING] The DNS entries for this DC are not registered correctly on DNS server '192.168.1.42'. Please wait for 30 minutes for DNS server replication. [FATAL] No DNS servers have the DNS records for this DC registered.

what stands out for me, is that your DC has a primary DNS suffix of "acme1", whilst your clients and the seemingly valid DNS zones all refer to acmefitness.local (the name of your forest) ?? Don

Exactly Don! This is a SBS Server and has 2 NIC's! Nothing like me waking up at 3AM figuring out part of the problem... Since whomever did the original setup put some of the services on one of the NIC's and the rest on the other this is most likely the root of the problem. Up above Meinolf does enquire about the wisdom of running Exchange and asks if this system is a SBS server, yes, yes it is. Now I am off to research SBS and how the DNS is setup/split between a single server with 2 NIC's. If anybody has insight to this I would be most appreciative. Thanks.

This is a superb article on this issues and some answers for the problem I am having: http://msmvps.com/blogs/acefekay/archive/2009/08/17/ad-and-its-reliance-on-dns.aspx In this article it is mentioned that I must enable DHCP on the SBS even if all the systems/printers are statically assigned. There is a wireless access point on this network with a built-in DHCP server enabled for customers that come and go, if I turn on the DHCP on the SBS won't this mess up the WAP DHCP server? Paging Ace... :-)

Bob, Ace actually says "...Can Cause Issues with AD Communications........DHCP Client service disabled on the DCs (a required service even if statically configured)" Note he refers to DHCP client, not DHCP server. Also note that SBS is a rather complicated beast and in general be cautious about using generalised solutions in an SBS system.Don

Thanks Don, I had misread that distinction. After an inspection of the wiring to the server (192.168.1.42) there is now no way to make both NIC's active with one pointing inside and the other out. Currently all workstations/printers have static ip addresses and point to 192.168.1.42 for their DNS. I have disabled the other NIC. My thinking is now I need to run the CEICW Wizard and follow the steps to "fix" the routing/DNS issues? Will this wizard rewrite and remove the stale DNS records and put the services back all under one NIC, the only active NIC? Anything else that I should worry about before I try this? Thanks again.

Bob, I got your email with reference to this thread. Here's what we need to do and what you need to provide: First, and reading through the thread, I couldn't find if you are using DHCP services on the router or the server. if the router is your DHCP server. disable it. Configure the DHCP service on the SBS server with a scope. Add the following DHC Options: Option 003 = 192.168.1.1 Option 006 = 192.168.1.42 Option 015 = acmefitness.local More importantly, if the Primary DNS suffix is acme1, then of course it's a Single Label Name issue. However, when you open ADUC, and if the DNS Domain Name shows up as acmefitness.local, then it's not a Single Label Name issue, rather a Disjointed Namespace issue. Therefore, before suggesting/recommending which direction to go to fix this, we'll need to know this info. If you can post a screenshot of your ADUC so we can see the top left navigation screen to see the actual name that shows up, it would definitely help to figure it out. Thanks, AceAce Fekay MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003 Microsoft Certified Trainer Microsoft MVP - Directory Services This posting is provided AS-IS with no warranties or guarantees and confers no rights.

Thanks Don, I had misread that distinction. After an inspection of the wiring to the server (192.168.1.42) there is now no way to make both NIC's active with one pointing inside and the other out. Currently all workstations/printers have static ip addresses and point to 192.168.1.42 for their DNS. I have disabled the other NIC. My thinking is now I need to run the CEICW Wizard and follow the steps to "fix" the routing/DNS issues? Will this wizard rewrite and remove the stale DNS records and put the services back all under one NIC, the only active NIC? Anything else that I should worry about before I try this? Thanks again. Bob, Just to address this post, the CEICW will not rewrite or remove any DNS records. Here's what it does: Understanding the Configure E-mail and Internet Connection Wizard http://technet.microsoft.com/en-us/library/cc747305(WS.10).aspx The way SBS works, you MUST use the CEICW to configure an SBS server. It's also recommended, as has been pointed out, to not multihome a DC, which also applies to SBS, since it is a DC. Also, since this is SBS, this should have really been posted in the SBS forum where the SBS gurus can help specifically with SBS questions, since SBS is a different animal than regular Windows Server. Here's the link to the forum. http://social.technet.microsoft.com/Forums/en-US/smallbusinessserver/threads Maybe a moderator can move this thread to the SBS forum, this way you don't have to create a new thread, and the reference to this thread will still remain for your account and you will still get notifications when tehre is an update so you don't have to search for it. AceAce Fekay MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003 Microsoft Certified Trainer Microsoft MVP - Directory Services This posting is provided AS-IS with no warranties or guarantees and confers no rights.

Thanks for your help! I disabled the DHCP on the router and then tried to add the server 192.168.1.42 as a DHCP server, the errors were that the server could not connect: acmeserver.acme1 [192.168.1.42] Not Connected Cannot find the DHCP server. I also tried 127.0.0.1 and received the same results. There was an already authorized server with the address 192.168.16.2 with OEMSBSCN-3935.OEMSBSDN-3935.local listed. I am assuming this was the OEM SBS out of the box configuration. Regardless there is no .16.x namespace to be had on this network. Here is a screenshot of the ADUC. Drilling down into the acmefitness.local<Computers section I can see all of the "old" (not added by me...) computers. Farther down in the MyBusiness<Computers I can see the 3 "new" (added by me) computers. Also in the MyBusiness<Users<SBSUsers folder lists all the users including the new created by me users. I am feeling (without knowing yet...) that all of these mismatches are due to this once being a two NIC system that was never reconfigured back to a one NIC system....

Thanks for your help! I disabled the DNS on the router and then tried to add the server 192.168.1.42 as a DHCP server, the errors were that the server could not connect: acmeserver.acme1 [192.168.1.42] Not Connected Cannot find the DHCP server. I also tried 127.0.0.1 and received the same results. There was an already authorized server with the address 192.168.16.2 with OEMSBSCN-3935.OEMSBSDN-3935.local listed. I am assuming this was the OEM SBS out of the box configuration. Regardless there is no .16.x namespace to be had on this network. Here is a screenshot of the ADUC. Drilling down into the acmefitness.local<Computers section I can see all of the "old" (not added by me...) computers. Farther down in the MyBusiness<Computers I can see the 3 "new" (added by me) computers. Also in the MyBusiness<Users<SBSUsers folder lists all the users including the new created by me users. I am feeling (without knowing yet...) that all of these mismatches are due to this once being a two NIC system that was never reconfigured back to a one NIC system....

Yikes, I was sure that the CEICW had to be used to update the DNS, thanks for stopping me from messing this up further. Yes, the multihomed nature has been fixed. The previous attempt (not by me) was just to unplug the ethernet cable. I have disabled the NIC. And to show how little I know, I did not even know that there was a specific SBS server forum. :-( I am hopeful a helpful mod can make the thread move....

Hi Ace, I read this and have looked at the ADUC shot I posted but I still can't tell if this is a Single Label Name issue or a Disjointed namespace issue. I do see a suffix of .acme1 but I see .local as well. Sorry about being obtuse.

I am getting closer to figuring this out however I am very reticent to screw things up even more. I have not been able to find an answer about what wiz/program/script actually writes the DNS records and/or rewrites them upon a requested change. This is a truncated netdiag from the server. It shows what I think are the root of the problem with the DNS, I have no idea how to go about fixing this: Output from netdiag on SBS Server 192.168.1.42 Computer Name: ACMESERVER DNS Host Name: ACMESERVER.acme1 System info : Microsoft Windows Server 2003 (Build 3790) Processor : x86 Family 6 Model 15 Stepping 11, GenuineIntel Per interface results: Adapter : Server Local Area Connection Netcard queries test . . . : Passed Host Name. . . . . . . . . : ACMESERVER IP Address . . . . . . . . : 192.168.1.42 Subnet Mask. . . . . . . . : 255.255.255.0 Default Gateway. . . . . . : 192.168.1.1 Dns Servers. . . . . . . . : 192.168.1.42 AutoConfiguration results. . . . . . : Passed Default gateway test . . . : Passed NetBT name test. . . . . . : Passed [WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenger Service', <20> 'WINS' names is missing. No remote names have been found. WINS service test. . . . . : Skipped There are no WINS servers configured for this interface. DNS test . . . . . . . . . . . . . : Failed [WARNING] Cannot find a primary authoritative DNS server for the name 'ACMESERVER.acme1.'. [RCODE_SERVER_FAILURE] The name 'ACMESERVER.acme1.' may not be registered in DNS. [WARNING] The DNS entries for this DC are not registered correctly on DNS server '192.168.1.42'. Please wait for 30 minutes for DNS server replication. [FATAL] No DNS servers have the DNS records for this DC registered. ---------------------------- Does it matter that the server shows this: Host Name . . . . . . . . . . . . : ACMESERVER Primary Dns Suffix . . . . . . . : acme1 while a workstation shows this?: Host Name . . . . . . . . . . . . : Customer1 Primary Dns Suffix . . . . . . . : acmefitness.local

If the Primary DNS Suffis is acme1, but the AD DNS Domain name is acmefitness.local, then you have a Disjointed Namespace. To fix it: Try the following: Make sure the zone is set to allow updates. Then reboot. Check the event log error. Re-run netidag and dcdiag. Post back your results, please (only errors). AceAce Fekay MVP, MCT, MCITP EA, MCTS Windows 2008 & Exchange 2007 & Exchange 2010, Exchange 2010 Enterprise Administrator, MCSE & MCSA 2003/2000, MCSA Messaging 2003 Microsoft Certified Trainer Microsoft MVP - Directory Services This posting is provided AS-IS with no warranties or guarantees and confers no rights.