We help IT Professionals succeed at work.

NSLOOKUP failing on second dns server

Patrick Wrigley
on
189 Views
Last Modified: 2020-10-20
I have 2 dns servers on our network
server13
       windows server 2008 R2
server18
       windows server 2008 R2

server13 is our primary dns server and everything is working normally
   
server18 has the following problem

1. PING www.google.com works normally = 216.239.38.120
2. nslookup www.google.com 208.67.220.220 works normally
3. nslookup www.google.com returns

          Server:  server18.jbcnet.loc
Address:  10.10.40.25

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to server18.jbcnet.loc timed-out

4. forwarders are
       8.8.8.8
       8.8.4.4
       local isp dns
       local isp dns # 2

5. root hints are enabled and working

6. it has a static ip address pointing to itself as the primary dns
7. it also points to server13 as its secondary dns address



nslookup degug out follows


Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.


Default Server:  server18.jbcnet.loc
Address:  10.10.40.25

> set debug
www.google.com
Server:  server18.jbcnet.loc
Address:  10.10.40.25

------------
Got answer:
    HEADER:
        opcode = QUERY, id = 2, rcode = NXDOMAIN
        header flags:  response, auth. answer, want recursion, recursion avail.
        questions = 1,  answers = 0,  authority records = 1,  additional = 0

    QUESTIONS:
        www.google.com.jbcnet.loc, type = A, class = IN
    AUTHORITY RECORDS:
    ->  jbcnet.loc
        ttl = 3600 (1 hour)
        primary name server = server18.jbcnet.loc
        responsible mail addr = hostmaster.jbcnet.loc
        serial  = 343409
        refresh = 900 (15 mins)
        retry   = 600 (10 mins)
        expire  = 86400 (1 day)
        default TTL = 3600 (1 hour)

------------
------------
Got answer:
    HEADER:
        opcode = QUERY, id = 3, rcode = NXDOMAIN
        header flags:  response, auth. answer, want recursion, recursion avail.
        questions = 1,  answers = 0,  authority records = 1,  additional = 0

    QUESTIONS:
        www.google.com.jbcnet.loc, type = AAAA, class = IN
    AUTHORITY RECORDS:
    ->  jbcnet.loc
        ttl = 3600 (1 hour)
        primary name server = server18.jbcnet.loc
        responsible mail addr = hostmaster.jbcnet.loc
        serial  = 343409
        refresh = 900 (15 mins)
        retry   = 600 (10 mins)
        expire  = 86400 (1 day)
        default TTL = 3600 (1 hour)

------------
DNS request timed out.
    timeout was 2 seconds.
timeout (2 secs)
DNS request timed out.
    timeout was 2 seconds.
timeout (2 secs)
*** Request to server18.jbcnet.loc timed-out
>
Comment
Watch Question

MaheshArchitect
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
Try only keeping google dns servers in forwarders on both servers and check.
Patrick WrigleyNetwork Manager

Author

Commented:
I did as requested
restarted dns service
flushdns cache
results were same
Server:  server18.jbcnet.loc
Address:  10.10.40.25

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to server18.jbcnet.loc timed-out
David FavorFractional CTO
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
As Mahesh suggested, probably best to remove your local servers from your forwarders list.

And... having local forwarders shouldn't create problem you're seeing.

Get onto the physical 10.10.40.25 machine + test.

If this works, then moving to the server13 machine fails, likely guess is a firewall problem.
Patrick WrigleyNetwork Manager

Author

Commented:
for comparision sake here is the dns server that ns look works on
Server:  server13.jbcnet.loc
Address:  10.10.40.5

Non-authoritative answer:
Name:    www.google.com
Addresses:  2607:f8b0:4009:80e::2004
          216.239.38.120
MaheshArchitect
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
when you added google dns servers under forwarders are they turned into green?

and did you get any issues on workstations or on domain controllers for normal dns resolution operations

I did some testing on my DC and I also got timed out some times but it did not affect anything on operations as name resolution is still working

It seems that nslookup www.google.com did not responded in timely manner
Patrick WrigleyNetwork Manager

Author

Commented:
1. yes all server have the green check mark
2. no issues with workstations
3. both controllers can resolve names vie a web browser
4. just nslookup is failing on server18
server18 points to server 13 for its secondary dns server in the tcp settings IF i remove the server13 address then server18 resoloves all internal addresses via ipv6 NOT ipv4. but heres the thing we use IPV4 not IPV6 for dhcp ect


PING WITH secondary DNS server set to the server13 address

Pinging server26.jbcnet.loc [10.10.40.109] with 32 bytes of data:
Reply from 10.10.40.109: bytes=32 time=1ms TTL=128
Reply from 10.10.40.109: bytes=32 time<1ms TTL=128
Reply from 10.10.40.109: bytes=32 time<1ms TTL=128
Reply from 10.10.40.109: bytes=32 time<1ms TTL=128

Ping statistics for 10.10.40.109:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 1ms, Average = 0ms



PING WITHOUT secondary DNS server set to server13 address


Pinging Server26 [fe80::59b0:4d7c:6e73:de77%11] with 32 bytes of data:
Reply from fe80::59b0:4d7c:6e73:de77%11: time=667ms
Reply from fe80::59b0:4d7c:6e73:de77%11: time<1ms
Reply from fe80::59b0:4d7c:6e73:de77%11: time<1ms
Reply from fe80::59b0:4d7c:6e73:de77%11: time<1ms

Ping statistics for fe80::59b0:4d7c:6e73:de77%11:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 0ms, Maximum = 667ms, Average = 166ms

also if i remove the secondary dns entry from servber18 it cannot resolve ANY web addresses
Patrick WrigleyNetwork Manager

Author

Commented:
upadte when i remove the static entry on server18 for its secondary dns it still returns the ipv4 address from all workstations that ping it even after a dns flush.  BUT when i ping out from server18 it uses IPV6 to return a value in so long as the secondary dns server entry in its ipv4 configuration is left blank so that it only ponts to itself for DNS resolution
Patrick WrigleyNetwork Manager

Author

Commented:
update # 2
sysvol is only syncing from server18 to server13

server18 is showing the following

The DFS Namespace service could not initialize cross forest trust information on this domain controller, but it will periodically retry the operation. The return code is in the record data.

I have applied the regedit fix to expand the staging area size to 1.5 G but this has not resolved the NtFrs error

could this be related?
MaheshArchitect
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
can you check that google dns forwarders are set on both servers
If yes, they should be able to resolve internet names without secondary dns address
you can untick ipv6 from network card on both servers and then start netlogon and dns server services on both servers one by one and check if name resolution is working
also reinstate another server entry as alternate dns on both servers
Sysvol issue is not related to internet name resolution
Patrick WrigleyNetwork Manager

Author

Commented:
i increased the staging file size max to E4E1C0
15 Gig

lets see if that helps????
Patrick WrigleyNetwork Manager

Author

Commented:
Server18 is just pretty much dead in the water without having server13 set as its secondary dns
server13-WITHOUT-a-secondary-dns-ent.jpg
server13_dns_forward.jpg
server18-ipv6-disables-AND-no-second.jpg
server18_dns_forward.jpg
Patrick WrigleyNetwork Manager

Author

Commented:
MaheshArchitect
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
check from server 18 you can telnet google dns servers on TCP 53 port?

I suspect something blocking on external firewall from serer 18 towards name resolution
Patrick WrigleyNetwork Manager

Author

Commented:
telnet sits at this screen and drops back to normal command propmt when attempting to connect to
telnet 8.8.8.8 53
telnet-attempt.jpg
Patrick WrigleyNetwork Manager

Author

Commented:
but to be fair i get the exact same response from my local machine
Patrick WrigleyNetwork Manager

Author

Commented:
NETSTAT -ano shows the following.  IS the dns service running on the ipv6 address????
netstat.txt
Bruno PACIIT Consultant
CERTIFIED EXPERT

Commented:
Hi,

The nslookup debug result show that the DNS server tries to resolve the name www.google.com.jbcnet.loc instead of www.google.com.

So probably you have misconfigured DNS search suffixes on the computer from where you launch the nslookup...


Can you check the result adding a dot "." at the end of the name, like this: "www.google.com." ?


Have a good day
Patrick WrigleyNetwork Manager

Author

Commented:
From the working dns server it is using
www.google.com.jbcnet.loc
and it is returning the record just fine, how would this work if the suffix was misconfigured?


Default Server:  server13.jbcnet.loc
Address:  10.10.40.5

> set debug
www.google.com
Server:  server13.jbcnet.loc
Address:  10.10.40.5

------------
Got answer:
    HEADER:
        opcode = QUERY, id = 2, rcode = NXDOMAIN
        header flags:  response, auth. answer, want recursion, recursion avail.
        questions = 1,  answers = 0,  authority records = 1,  additional = 0

    QUESTIONS:
        www.google.com.jbcnet.loc, type = A, class = IN
    AUTHORITY RECORDS:
    ->  jbcnet.loc
        ttl = 3600 (1 hour)
        primary name server = server13.jbcnet.loc
        responsible mail addr = hostmaster.jbcnet.loc
        serial  = 344025
        refresh = 900 (15 mins)
        retry   = 600 (10 mins)
        expire  = 86400 (1 day)
        default TTL = 3600 (1 hour)

------------
------------
Got answer:
    HEADER:
        opcode = QUERY, id = 3, rcode = NXDOMAIN
        header flags:  response, auth. answer, want recursion, recursion avail.
        questions = 1,  answers = 0,  authority records = 1,  additional = 0

    QUESTIONS:
        www.google.com.jbcnet.loc, type = AAAA, class = IN
    AUTHORITY RECORDS:
    ->  jbcnet.loc
        ttl = 3600 (1 hour)
        primary name server = server13.jbcnet.loc
        responsible mail addr = hostmaster.jbcnet.loc
        serial  = 344025
        refresh = 900 (15 mins)
        retry   = 600 (10 mins)
        expire  = 86400 (1 day)
        default TTL = 3600 (1 hour)

------------
------------
Got answer:
    HEADER:
        opcode = QUERY, id = 4, rcode = NOERROR
        header flags:  response, want recursion, recursion avail.
        questions = 1,  answers = 1,  authority records = 0,  additional = 0

    QUESTIONS:
        www.google.com, type = A, class = IN
    ANSWERS:
    ->  www.google.com
        internet address = 216.239.38.120
        ttl = 129 (2 mins 9 secs)

------------
Non-authoritative answer:
------------
Got answer:
    HEADER:
        opcode = QUERY, id = 5, rcode = NOERROR
        header flags:  response, want recursion, recursion avail.
        questions = 1,  answers = 1,  authority records = 0,  additional = 0

    QUESTIONS:
        www.google.com, type = AAAA, class = IN
    ANSWERS:
    ->  www.google.com
        AAAA IPv6 address = 2607:f8b0:4009:803::2004
        ttl = 204 (3 mins 24 secs)

------------
Name:    www.google.com
Addresses:  2607:f8b0:4009:803::2004
          216.239.38.120

>
Patrick WrigleyNetwork Manager

Author

Commented:
what is missing form the non working dns server is the following.

BOTH the working DNS server AND the non working DNS server get the first 2 "Got answer" returns HOWEVER the non working DNS server never gets the the following non authoritative answer


------------
Non-authoritative answer:
------------
Got answer:
    HEADER:
        opcode = QUERY, id = 5, rcode = NOERROR
        header flags:  response, want recursion, recursion avail.
        questions = 1,  answers = 1,  authority records = 0,  additional = 0


    QUESTIONS:
        www.google.com, type = AAAA, class = IN
    ANSWERS:
    ->  www.google.com
        AAAA IPv6 address = 2607:f8b0:4009:803::2004
        ttl = 204 (3 mins 24 secs)

------------
Name:    www.google.com
Addresses:  2607:f8b0:4009:803::2004
          216.239.38.120

>
Patrick WrigleyNetwork Manager

Author

Commented:
Bruno here is the result of adding the trailing "." to the end of the nslookup


C:\Users>nslookup www.google.com.
Server:  server18.jbcnet.loc
Address:  10.10.40.25

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to server18.jbcnet.loc timed-out
Patrick WrigleyNetwork Manager

Author

Commented:
if I manually set the default DNS server to look at google 8.8.8.8 the nslookup works just fine from the problem server. It only drops the ball when looking at itself. all of the forwarders and root hint show the green check mark on the DNS properties of the server however.

Server:  server18.jbcnet.loc
Address:  10.10.40.25

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to server18.jbcnet.loc timed-out

C:\Users>nslookup
Default Server:  server18.jbcnet.loc
Address:  10.10.40.25

> server 8.8.8.8
Default Server:  google-public-dns-a.google.com
Address:  8.8.8.8

www.google.com
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
Name:    www.google.com
Addresses:  2607:f8b0:4009:80d::2004
          216.239.38.120

>
Patrick WrigleyNetwork Manager

Author

Commented:
Even though it shows that it is configured to use forwarders and root hints it does not appear to be actually doing it.
MaheshArchitect
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
The question is going in bit different tangent

If you could run dcdiag /v and repadmin /showrepl on problematic DC from elevated cmd and post results here
Patrick WrigleyNetwork Manager

Author

Commented:
ok this look bad


Directory Server Diagnosis


Performing initial setup:

   Trying to find home server...

   * Verifying that the local machine Server18, is a Directory Server. 
   Home Server = Server18

   * Connecting to directory service on server Server18.

   * Identified AD Forest. 
   Collecting AD specific global data 
   * Collecting site info.

   Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=jbcnet,DC=loc,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
   The previous call succeeded 
   Iterating through the sites 
   Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=jbcnet,DC=loc
   Getting ISTG and options for the site
   * Identifying all servers.

   Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=jbcnet,DC=loc,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
   The previous call succeeded....
   The previous call succeeded
   Iterating through the list of servers 
   Getting information for the server CN=NTDS Settings,CN=SERVER13,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=jbcnet,DC=loc 
   objectGuid obtained
   InvocationID obtained
   dnsHostname obtained
   site info obtained
   All the info for the server collected
   Getting information for the server CN=NTDS Settings,CN=SERVER18,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=jbcnet,DC=loc 
   objectGuid obtained
   InvocationID obtained
   dnsHostname obtained
   site info obtained
   All the info for the server collected
   * Identifying all NC cross-refs.

   * Found 2 DC(s). Testing 1 of them.

   Done gathering initial info.


Doing initial required tests

   
   Testing server: Default-First-Site-Name\SERVER18

      Starting test: Connectivity

         * Active Directory LDAP Services Check
         Determining IP4 connectivity 
         * Active Directory RPC Services Check
         ......................... SERVER18 passed test Connectivity



Doing primary tests

   
   Testing server: Default-First-Site-Name\SERVER18

      Starting test: Advertising

         The DC SERVER18 is advertising itself as a DC and having a DS.
         The DC SERVER18 is advertising as an LDAP server
         The DC SERVER18 is advertising as having a writeable directory
         The DC SERVER18 is advertising as a Key Distribution Center
         The DC SERVER18 is advertising as a time server
         The DS SERVER18 is advertising as a GC.
         ......................... SERVER18 passed test Advertising

      Test omitted by user request: CheckSecurityError

      Test omitted by user request: CutoffServers

      Starting test: FrsEvent

         * The File Replication Service Event log test 
         ......................... SERVER18 passed test FrsEvent

      Starting test: DFSREvent

         The DFS Replication Event Log. 
         Skip the test because the server is running FRS.

         ......................... SERVER18 passed test DFSREvent

      Starting test: SysVolCheck

         * The File Replication Service SYSVOL ready test 
         File Replication Service's SYSVOL is ready 
         ......................... SERVER18 passed test SysVolCheck

      Starting test: KccEvent

         * The KCC Event log test
         Found no KCC errors in "Directory Service" Event log in the last 15 minutes.
         ......................... SERVER18 passed test KccEvent

      Starting test: KnowsOfRoleHolders

         Role Schema Owner = CN=NTDS Settings,CN=SERVER13,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=jbcnet,DC=loc
         Role Domain Owner = CN=NTDS Settings,CN=SERVER13,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=jbcnet,DC=loc
         Role PDC Owner = CN=NTDS Settings,CN=SERVER13,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=jbcnet,DC=loc
         Role Rid Owner = CN=NTDS Settings,CN=SERVER13,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=jbcnet,DC=loc
         Role Infrastructure Update Owner = CN=NTDS Settings,CN=SERVER13,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=jbcnet,DC=loc
         ......................... SERVER18 passed test KnowsOfRoleHolders

      Starting test: MachineAccount

         Checking machine account for DC SERVER18 on DC SERVER18.
         * SPN found :LDAP/Server18.jbcnet.loc/jbcnet.loc
         * SPN found :LDAP/Server18.jbcnet.loc
         * SPN found :LDAP/SERVER18
         * SPN found :LDAP/Server18.jbcnet.loc/JBCNET
         * SPN found :LDAP/2ab535c9-67e6-4be6-8363-bc0d173e18df._msdcs.jbcnet.loc
         * SPN found :E3514235-4B06-11D1-AB04-00C04FC2DCD2/2ab535c9-67e6-4be6-8363-bc0d173e18df/jbcnet.loc
         * SPN found :HOST/Server18.jbcnet.loc/jbcnet.loc
         * SPN found :HOST/Server18.jbcnet.loc
         * SPN found :HOST/SERVER18
         * SPN found :HOST/Server18.jbcnet.loc/JBCNET
         * SPN found :GC/Server18.jbcnet.loc/jbcnet.loc
         ......................... SERVER18 passed test MachineAccount

      Starting test: NCSecDesc

         * Security Permissions check for all NC's on DC SERVER18.
         * Security Permissions Check for

           DC=ForestDnsZones,DC=jbcnet,DC=loc
            (NDNC,Version 3)
         * Security Permissions Check for

           DC=DomainDnsZones,DC=jbcnet,DC=loc
            (NDNC,Version 3)
         * Security Permissions Check for

           CN=Schema,CN=Configuration,DC=jbcnet,DC=loc
            (Schema,Version 3)
         * Security Permissions Check for

           CN=Configuration,DC=jbcnet,DC=loc
            (Configuration,Version 3)
         * Security Permissions Check for

           DC=jbcnet,DC=loc
            (Domain,Version 3)
         ......................... SERVER18 passed test NCSecDesc

      Starting test: NetLogons

         * Network Logons Privileges Check
         Verified share \\SERVER18\netlogon
         Verified share \\SERVER18\sysvol
         ......................... SERVER18 passed test NetLogons

      Starting test: ObjectsReplicated

         SERVER18 is in domain DC=jbcnet,DC=loc
         Checking for CN=SERVER18,OU=Domain Controllers,DC=jbcnet,DC=loc in domain DC=jbcnet,DC=loc on 1 servers
            Object is up-to-date on all servers.
         Checking for CN=NTDS Settings,CN=SERVER18,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=jbcnet,DC=loc in domain CN=Configuration,DC=jbcnet,DC=loc on 1 servers
            Object is up-to-date on all servers.
         ......................... SERVER18 passed test ObjectsReplicated

      Test omitted by user request: OutboundSecureChannels

      Starting test: Replications

         * Replications Check
         * Replication Latency Check
            DC=ForestDnsZones,DC=jbcnet,DC=loc
               Latency information for 4 entries in the vector were ignored.
                  4 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC).  
            DC=DomainDnsZones,DC=jbcnet,DC=loc
               Latency information for 4 entries in the vector were ignored.
                  4 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC).  
            CN=Schema,CN=Configuration,DC=jbcnet,DC=loc
               Latency information for 4 entries in the vector were ignored.
                  4 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC).  
            CN=Configuration,DC=jbcnet,DC=loc
               Latency information for 4 entries in the vector were ignored.
                  4 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC).  
            DC=jbcnet,DC=loc
               Latency information for 4 entries in the vector were ignored.
                  4 were retired Invocations.  0 were either: read-only replicas and are not verifiably latent, or dc's no longer replicating this nc.  0 had no latency information (Win2K DC).  
         ......................... SERVER18 passed test Replications

      Starting test: RidManager

         * Available RID Pool for the Domain is 5104 to 1073741823
         * Server13.jbcnet.loc is the RID Master
         * DsBind with RID Master was successful
         * rIDAllocationPool is 4104 to 4603
         * rIDPreviousAllocationPool is 4104 to 4603
         * rIDNextRID: 4313
         ......................... SERVER18 passed test RidManager

      Starting test: Services

         * Checking Service: EventSystem
         * Checking Service: RpcSs
         * Checking Service: NTDS
         * Checking Service: DnsCache
         * Checking Service: NtFrs
         * Checking Service: IsmServ
         * Checking Service: kdc
         * Checking Service: SamSs
         * Checking Service: LanmanServer
         * Checking Service: LanmanWorkstation
         * Checking Service: w32time
         * Checking Service: NETLOGON
         ......................... SERVER18 passed test Services

      Starting test: SystemLog

         * The System Event log test
         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:36:35

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:37:12

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:37:49

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:37:50

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:37:56

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         A warning event occurred.  EventID: 0x00001695

            Time Generated: 02/25/2019   11:38:06

            Event String:

            Dynamic registration or deletion of one or more DNS records associated with DNS domain 'jbcnet.loc.' failed.  These records are used by other computers to locate this server as a domain controller (if the specified domain is an Active Directory domain) or as an LDAP server (if the specified domain is an application partition).  

            

            Possible causes of failure include:  

            - TCP/IP properties of the network connections of this computer contain wrong IP address(es) of the preferred and alternate DNS servers 

            - Specified preferred and alternate DNS servers are not running 

            - DNS server(s) primary for the records to be registered is not running 

            - Preferred or alternate DNS servers are configured with wrong root hints 

            - Parent DNS zone contains incorrect delegation to the child zone authoritative for the DNS records that failed registration  

            

            USER ACTION  

            Fix possible misconfiguration(s) specified above and initiate registration or deletion of the DNS records by running 'nltest.exe /dsregdns' from the command prompt on the domain controller or by restarting Net Logon service on the domain controller.

         A warning event occurred.  EventID: 0x00001695

            Time Generated: 02/25/2019   11:38:06

            Event String:

            Dynamic registration or deletion of one or more DNS records associated with DNS domain 'DomainDnsZones.jbcnet.loc.' failed.  These records are used by other computers to locate this server as a domain controller (if the specified domain is an Active Directory domain) or as an LDAP server (if the specified domain is an application partition).  

            

            Possible causes of failure include:  

            - TCP/IP properties of the network connections of this computer contain wrong IP address(es) of the preferred and alternate DNS servers 

            - Specified preferred and alternate DNS servers are not running 

            - DNS server(s) primary for the records to be registered is not running 

            - Preferred or alternate DNS servers are configured with wrong root hints 

            - Parent DNS zone contains incorrect delegation to the child zone authoritative for the DNS records that failed registration  

            

            USER ACTION  

            Fix possible misconfiguration(s) specified above and initiate registration or deletion of the DNS records by running 'nltest.exe /dsregdns' from the command prompt on the domain controller or by restarting Net Logon service on the domain controller.

         A warning event occurred.  EventID: 0x00001695

            Time Generated: 02/25/2019   11:38:06

            Event String:

            Dynamic registration or deletion of one or more DNS records associated with DNS domain 'ForestDnsZones.jbcnet.loc.' failed.  These records are used by other computers to locate this server as a domain controller (if the specified domain is an Active Directory domain) or as an LDAP server (if the specified domain is an application partition).  

            

            Possible causes of failure include:  

            - TCP/IP properties of the network connections of this computer contain wrong IP address(es) of the preferred and alternate DNS servers 

            - Specified preferred and alternate DNS servers are not running 

            - DNS server(s) primary for the records to be registered is not running 

            - Preferred or alternate DNS servers are configured with wrong root hints 

            - Parent DNS zone contains incorrect delegation to the child zone authoritative for the DNS records that failed registration  

            

            USER ACTION  

            Fix possible misconfiguration(s) specified above and initiate registration or deletion of the DNS records by running 'nltest.exe /dsregdns' from the command prompt on the domain controller or by restarting Net Logon service on the domain controller.

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:38:38

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:39:15

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:39:52

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:39:58

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:40:41

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:41:18

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:41:55

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:42:01

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:42:33

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:43:10

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:43:47

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:44:25

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:44:25

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:44:31

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:45:04

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:45:41

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:46:18

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:46:55

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:46:56

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:47:02

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:47:35

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:48:12

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:48:49

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:49:26

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:49:27

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:49:33

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:50:05

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:50:42

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:51:19

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:51:57

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:51:58

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:52:03

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:52:36

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:53:13

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:53:50

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:54:27

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:54:28

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:54:34

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:55:06

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:55:43

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:56:21

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:56:58

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:56:58

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:57:04

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:57:37

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:58:14

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:58:51

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:59:28

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:59:29

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   11:59:35

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:00:08

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:00:55

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:01:32

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:01:38

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:02:10

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:02:47

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:03:24

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:04:02

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:04:02

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:04:08

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:04:41

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:05:18

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:05:55

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:06:32

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:06:33

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:06:39

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:07:11

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:07:48

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:08:26

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:09:03

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:09:04

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:09:10

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:09:42

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:10:19

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:10:56

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:11:33

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:11:34

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:11:40

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:12:13

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:12:50

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:13:27

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:14:04

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:14:05

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:14:11

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:14:44

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:15:21

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:15:58

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:16:35

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:16:36

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:16:42

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:17:14

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:17:51

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:18:28

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:19:06

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:19:06

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:19:12

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:19:45

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:20:22

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:21:09

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:21:15

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:21:47

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:22:24

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:23:01

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:23:39

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:23:40

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:23:45

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:24:18

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:24:55

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:25:32

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:26:09

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:26:10

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:26:16

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:26:49

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:27:26

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:28:03

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:28:40

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:28:41

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:28:47

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:29:19

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:29:56

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:30:43

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:30:49

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:31:22

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:31:59

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:32:36

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:33:14

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:33:15

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:33:21

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Windows\System32\Driverquery.exe.

            

         An error event occurred.  EventID: 0xE03D000F

            Time Generated: 02/25/2019   12:33:53

            Event String:

            The on-access driver was unable to create an impersonation token for file \Device\HarddiskVolume4\Program Files\Hewlett-Packard\AMS\Service\GetNVMEDriveInfo.exe.

            

         ......................... SERVER18 failed test SystemLog

      Test omitted by user request: Topology

      Test omitted by user request: VerifyEnterpriseReferences

      Starting test: VerifyReferences

         The system object reference (serverReference)

         CN=SERVER18,OU=Domain Controllers,DC=jbcnet,DC=loc and backlink on

         CN=SERVER18,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=jbcnet,DC=loc

         are correct. 
         The system object reference (serverReferenceBL)

         CN=SERVER18,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=jbcnet,DC=loc

         and backlink on

         CN=NTDS Settings,CN=SERVER18,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=jbcnet,DC=loc

         are correct. 
         The system object reference (frsComputerReferenceBL)

         CN=SERVER18,CN=Domain System Volume (SYSVOL share),CN=File Replication Service,CN=System,DC=jbcnet,DC=loc

         and backlink on CN=SERVER18,OU=Domain Controllers,DC=jbcnet,DC=loc are

         correct. 
         ......................... SERVER18 passed test VerifyReferences

      Test omitted by user request: VerifyReplicas

   
      Test omitted by user request: DNS

      Test omitted by user request: DNS

   
   Running partition tests on : ForestDnsZones

      Starting test: CheckSDRefDom

         ......................... ForestDnsZones passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... ForestDnsZones passed test

         CrossRefValidation

   
   Running partition tests on : DomainDnsZones

      Starting test: CheckSDRefDom

         ......................... DomainDnsZones passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... DomainDnsZones passed test

         CrossRefValidation

   
   Running partition tests on : Schema

      Starting test: CheckSDRefDom

         ......................... Schema passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... Schema passed test CrossRefValidation

   
   Running partition tests on : Configuration

      Starting test: CheckSDRefDom

         ......................... Configuration passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... Configuration passed test CrossRefValidation

   
   Running partition tests on : jbcnet

      Starting test: CheckSDRefDom

         ......................... jbcnet passed test CheckSDRefDom

      Starting test: CrossRefValidation

         ......................... jbcnet passed test CrossRefValidation

   
   Running enterprise tests on : jbcnet.loc

      Test omitted by user request: DNS

      Test omitted by user request: DNS

      Starting test: LocatorCheck

         GC Name: \\Server18.jbcnet.loc

         Locator Flags: 0xe00031fc
         PDC Name: \\Server13.jbcnet.loc
         Locator Flags: 0xe00033fd
         Time Server Name: \\Server18.jbcnet.loc
         Locator Flags: 0xe00031fc
         Preferred Time Server Name: \\Server13.jbcnet.loc
         Locator Flags: 0xe00033fd
         KDC Name: \\Server18.jbcnet.loc
         Locator Flags: 0xe00031fc
         ......................... jbcnet.loc passed test LocatorCheck

      Starting test: Intersite

         Skipping site Default-First-Site-Name, this site is outside the scope

         provided by the command line arguments provided. 
         ......................... jbcnet.loc passed test Intersite

Open in new window

Patrick WrigleyNetwork Manager

Author

Commented:
C:\Users>repadmin /showrepl

Repadmin: running command /showrepl against full DC localhost
Default-First-Site-Name\SERVER18
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: 2ab535c9-67e6-4be6-8363-bc0d173e18df
DSA invocationID: b88ea881-e5ee-4d32-97ce-48b893a4866e

==== INBOUND NEIGHBORS ======================================

DC=jbcnet,DC=loc
    Default-First-Site-Name\SERVER13 via RPC
        DSA object GUID: 1a2ee317-501a-47eb-8f6d-e0c380b16eb3
        Last attempt @ 2019-02-25 12:04:36 was successful.

CN=Configuration,DC=jbcnet,DC=loc
    Default-First-Site-Name\SERVER13 via RPC
        DSA object GUID: 1a2ee317-501a-47eb-8f6d-e0c380b16eb3
        Last attempt @ 2019-02-25 11:57:39 was successful.

CN=Schema,CN=Configuration,DC=jbcnet,DC=loc
    Default-First-Site-Name\SERVER13 via RPC
        DSA object GUID: 1a2ee317-501a-47eb-8f6d-e0c380b16eb3
        Last attempt @ 2019-02-25 11:57:39 was successful.

DC=DomainDnsZones,DC=jbcnet,DC=loc
    Default-First-Site-Name\SERVER13 via RPC
        DSA object GUID: 1a2ee317-501a-47eb-8f6d-e0c380b16eb3
        Last attempt @ 2019-02-25 11:57:39 was successful.

DC=ForestDnsZones,DC=jbcnet,DC=loc
    Default-First-Site-Name\SERVER13 via RPC
        DSA object GUID: 1a2ee317-501a-47eb-8f6d-e0c380b16eb3
        Last attempt @ 2019-02-25 12:03:52 was successful.

Open in new window

Patrick WrigleyNetwork Manager

Author

Commented:
I think we may be getting somewhere look at this


C:\Users>dcdiag /test:dns

Directory Server Diagnosis

Performing initial setup:
   Trying to find home server...
   Home Server = Server18
   * Identified AD Forest.
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\SERVER18
      Starting test: Connectivity
         ......................... SERVER18 passed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\SERVER18

      Starting test: DNS

         DNS Tests are running and not hung. Please wait a few minutes...
         ......................... SERVER18 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 : jbcnet

   Running enterprise tests on : jbcnet.loc
      Starting test: DNS
         Test results for domain controllers:

            DC: Server18.jbcnet.loc
            Domain: jbcnet.loc


               TEST: Dynamic update (Dyn)
                  Warning: Failed to delete the test record dcdiag-test-record i
n zone jbcnet.loc

               TEST: Records registration (RReg)
                  Network Adapter
                  [00000007] HP Ethernet 1Gb 4-port 331i Adapter:
                     Warning:
                     Missing A record at DNS server 10.10.40.25:
                     Server18.jbcnet.loc

                     Warning:
                     Missing A record at DNS server 10.10.40.25:
                     gc._msdcs.jbcnet.loc

               Error: Record registrations cannot be found for all the network
               adapters

         Summary of DNS test results:

                                            Auth Basc Forw Del  Dyn  RReg Ext
            _________________________________________________________________
            Domain: jbcnet.loc
               Server18                     PASS PASS PASS PASS WARN FAIL n/a

         ......................... jbcnet.loc failed test DNS

Open in new window

Architect
CERTIFIED EXPERT
Distinguished Expert 2019
Commented:
This problem has been solved!
(Unlock this solution with a 7-day Free Trial)
UNLOCK SOLUTION
Patrick WrigleyNetwork Manager

Author

Commented:
the working DC was originally a
RAS server and  has 2 ip address assigned to it could this be the issue?
MaheshArchitect
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
so working DC having 2nd NIC with public IP address ?

OR

it is having 2nd NIC in isolated subnet ?

Still don't find any relation why dns resolution is failing on other DC?
Patrick WrigleyNetwork Manager

Author

Commented:
working DC had 2 private IP

the second IP address was from a now dead subnet

old subnet address has been removed from the reverse lookup zone has been removed
MaheshArchitect
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
you need to remove 2nd NIC dynamic entries from DNS including NS records and also need to set 2nd NIC not to register in DNS from NIC properties
I believe queries are going to dead NS record and there its failing
Patrick WrigleyNetwork Manager

Author

Commented:
Okay.

there were several bad ip addresses listed on the NS they have been removed and i am l3edt with tbhis

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\pwrigley>dcdiag /test:dns

Directory Server Diagnosis

Performing initial setup:
   Trying to find home server...
   Home Server = Server18
   * Identified AD Forest.
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\SERVER18
      Starting test: Connectivity
         ......................... SERVER18 passed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\SERVER18

      Starting test: DNS

         DNS Tests are running and not hung. Please wait a few minutes...
         ......................... SERVER18 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 : jbcnet

   Running enterprise tests on : jbcnet.loc
      Starting test: DNS
         Test results for domain controllers:

            DC: Server18.jbcnet.loc
            Domain: jbcnet.loc


               TEST: Dynamic update (Dyn)
                  Warning: Failed to delete the test record dcdiag-test-record i
n zone jbcnet.loc

               TEST: Records registration (RReg)
                  Network Adapter
                  [00000007] HP Ethernet 1Gb 4-port 331i Adapter:
                     Warning:
                     Missing A record at DNS server 10.10.40.25:
                     Server18.jbcnet.loc

                     Warning:
                     Missing A record at DNS server 10.10.40.25:
                     gc._msdcs.jbcnet.loc

               Error: Record registrations cannot be found for all the network
               adapters

         Summary of DNS test results:

                                            Auth Basc Forw Del  Dyn  RReg Ext
            _________________________________________________________________
            Domain: jbcnet.loc
               Server18                     PASS PASS PASS PASS WARN FAIL n/a

         ......................... jbcnet.loc failed test DNS

C:\Users\pwrigley>dcdiag /test:dns

Open in new window

Patrick WrigleyNetwork Manager

Author

Commented:
checking event logs shows this

The DNS server was unable to add or write an update of domain name server18 in zone jbcnet.loc to the Active Directory.  Check that the Active Directory is functioning properly and add or update this domain name using the DNS console. The extended error debug information (which may be empty) is "". The event data contains the error.
Patrick WrigleyNetwork Manager

Author

Commented:
okay i think i may have th eproblem narrowed doen.

1 server13 is the FSMO role holder and the PDC emulator
2 server18 is a secondary DC
3 server13 is the SOA for DNS in the domain
4 server18 is pointing to itself as the SOA as well for DNS in the domain
5 i spun up a 3rd DNS server, copied the zones as secondary zones and nslookup works as expected on this dns server

do i need to and if so how do i modify the DNS zones on server18 to be secondary to server13??
MaheshArchitect
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
For AD normally all dns servers also host active directory and also authoritative for dns zone, no need to set it as secondary dns
Remove dead nic entries (same as parent folder) and under nic advanced properties ensure that you will remove checkbox "do not register this address in dns"
Patrick WrigleyNetwork Manager

Author

Commented:
here is what I have done
registar-dns.jpg
Patrick WrigleyNetwork Manager

Author

Commented:
now we are getting this error

C:\Users\pwrigley>dcdiag /test:dns

Directory Server Diagnosis

Performing initial setup:
   Trying to find home server...
   Home Server = Server18
   * Identified AD Forest.
   Done gathering initial info.

Doing initial required tests

   Testing server: Default-First-Site-Name\SERVER18
      Starting test: Connectivity
         The host 2ab535c9-67e6-4be6-8363-bc0d173e18df._msdcs.jbcnet.loc could
         not be resolved to an IP address. Check the DNS server, DHCP, server
         name, etc.
         Got error while checking LDAP and RPC connectivity. Please check your
         firewall settings.
         ......................... SERVER18 failed test Connectivity

Doing primary tests

   Testing server: Default-First-Site-Name\SERVER18

      Starting test: DNS

         DNS Tests are running and not hung. Please wait a few minutes...
Patrick WrigleyNetwork Manager

Author

Commented:
we put the check mark back into the "register this connections address in DNS"

still getting the above error
MaheshArchitect
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
Sorry man, I suggest you to hire somebody, could not resolve issue without checking out servers
Patrick WrigleyNetwork Manager

Author

Commented:
understood, thank you for the huge amount of time you have spent on this for me sir!
MaheshArchitect
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
That's not an issue
However it looks like we are missing some basic config or issue is very weird
Probably another expert can help you further

I can help further by remoting your servers, but don't want to do it for free
Patrick WrigleyNetwork Manager

Author

Commented:
We would be interested in this, how should I contact you?
MaheshArchitect
CERTIFIED EXPERT
Distinguished Expert 2019

Commented:
You can drop me message from EE itself for live session

Gain unlimited access to on-demand training courses with an Experts Exchange subscription.

Get Access
Why Experts Exchange?

Experts Exchange always has the answer, or at the least points me in the correct direction! It is like having another employee that is extremely experienced.

Jim Murphy
Programmer at Smart IT Solutions

When asked, what has been your best career decision?

Deciding to stick with EE.

Mohamed Asif
Technical Department Head

Being involved with EE helped me to grow personally and professionally.

Carl Webster
CTP, Sr Infrastructure Consultant
Empower Your Career
Did You Know?

We've partnered with two important charities to provide clean water and computer science education to those who need it most. READ MORE

Ask ANY Question

Connect with Certified Experts to gain insight and support on specific technology challenges including:

  • Troubleshooting
  • Research
  • Professional Opinions