The warning is recorded because Windows 10 is configured to register its IP address in DNS and the DNS server responsible for the computer’s host name does not accept dynamic updates for that name from the computer’s Maybe I need to post in the server forum as well? Our clients get their IP addresses from our Windows DHCP server. I don't want to untick "Register this connection's addresses in DNS" as I don't see that as a fix, rather a band aid. Our DNS only accepts Secure updates.is this Windows 10 trying a non-secure update first? So, I don't know if this is a Windows 10\Domain Controller functional level "issue" (our Windows 7 machines do not have this message in their event logs). Some machines have more frequent instances of this event (several per The machines register in our forward and reverse zones just fine.so I don't know why the event log indicates the refusal. Our clientsĭo not have DNS issues (Internet, mail, etc. We are a single domain\forest with 2 domain controllers (2008 R2). It has since we started rolling out Win 10. However, unlike the poster in the link above, this event ID occurs on all of our Windows 10 machines (17 is what we have). My issue is similar to the one posted here at the link below.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |