Build a great reporting interface using Splunk, one of the leaders in the Security Information and Event Management (SIEM) field, linking the collected Windows events to www.eventid.net. The EventId.Net for Splunk Add-on assumes that Splunk is collecting information from Windows servers and workstation via the Splunk Universal Forwarder.
The system failed to register network adapter with settings:
Adapter Name : <adapter name>
Host Name : <host name>
Adapter-specific Domain Suffix : <domain suffix>
DNS server list : <ip>
Sent update to server : <ip>
IP Address(es) : <ip>
The system could not register the DNS update request because of a security related problem. This could happen for the following reasons: (a) the DNS domain name that your computer is trying to register could not be updated because your computer does not have the right permissions or (b) there might have been a problem negotiating valid credentials with the DNS server to update.
You can manually retry DNS registration of the network adapter and its settings by typing "ipconfig /registerdns" at the command prompt. If problems still persist contact your DNS server or network systems administrator. For specific error code information see the record data displayed below.
|English: Request a translation of the event description in plain English.|
In my case, I noticed the <domain suffix> area had a different name than the server name. Example: Adapter-specific Domain Suffix : unknownservername.domain.com. I searched through the registry and found "AlternateComputerNames" entries containing this "unknownservername" under:
After clearing these entries, the event warning ceased to occur.
|Private comment: Subscribers only. See example of private comment|
|Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links...|
Send comments or solutions
- Notify me when updated