| Event Id | 11153 |
| Source | DnaApi |
| Description | The system failed to register network adapter with settings: Adapter Name : {EFA042E1-E7E8-4D50-8E1D-69541C03F4AC} Host Name : <server name> Adapter-specific Domain Suffix : <domain name> DNS server list : <ip address>, <ip address> Sent update to server : <ip address> IP Address(es) : <ip address> The reason it could not register was because the DNS server refused the dynamic update request. This could happen for the following reasons: (a) current DNS update policies do not allow this computer to update the DNS domain name configured for this adapter, or (b) the authoritative DNS server for this DNS domain name does not support the DNS dynamic update protocol. To register a DNS host (A) resource record using the specific DNS domain name for this adapter, contact your DNS server or network systems administrator. Data: 0000: 2d 23 00 00 -#.. |
| Event Information | Newsgroup posts indicate that this problem may occur if there is no reverse-lookup zone configured in the DNS for the computer experiencing this issue. In one instance, this occurred when a server using an Active Directory DNS tried to register its name without being part of that Active Directory domain. Another situation according to new group post: The server experiencing the problem was an Exchange Server which did not have MX or A records in the forward lookup zone, or a PTR record in the reverse lookup zone of the DNS server. Added these records to the SOA DNS server. Also, there was no DNS reverse lookup zone for that subnet. We believe that this happened because the credentials provided when joining the computer into the AD were different from the ones used to attach to a server in AD (and used by the secure channel between the server and the Domain Controller). For example, you may have a drive mapped to a server in the AD and you provided some credentials (i.e. your user id/password) and then, when you joined the AD you used a different set of credentials (i.e the domain Administrator). Please check the following: 1. Under which user account did you try to join the computer into the AD? I assume that youre using local Administrator. 2. Do you have any mapped drive on the workstation to the DC? If so, please disconnect all of them and then try to join again. 3. If you cannot find any mapped drive from the workstation, launch Command Prompt and type this command: net use * /d Press Y to confirm when youre prompted. This command will terminate all the active session between this workstations and other computers (including the DC, of course). |
| Reference Links |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.