100 | Parametre |
Parameters |
101 | DNS-klient |
DNS Client |
102 | Ved hjælp af tjenesten DNS Client (dnscache) cachelagres DNS-navne (Domain Name System), og det fulde computernavn for denne computer registreres. Hvis tjenesten stoppes, oversættes DNS-navne fortsat. Resultaterne af forespørgsler om DNS-navne cachelagres imidlertid ikke, og computerens navn registreres ikke. Hvis tjenesten deaktiveres, kan tjenester, der er direkte afhængige af den, ikke starte. |
The DNS Client service (dnscache) caches Domain Name System (DNS) names and registers the full computer name for this computer. If the service is stopped, DNS names will continue to be resolved. However, the results of DNS name queries will not be cached and the computer's name will not be registered. If the service is disabled, any services that explicitly depend on it will fail to start. |
103 | Tillid til DNS-server (Domain Name System) |
Domain Name System (DNS) Server Trust |
0x3F0 | Det primære DNS-suffiks for denne computer mangler. Da der mangler et primært DNS-suffiks, kan korte ikke-kvalificerede navne muligvis ikke fortolkes via DNS |
The primary DNS suffix for this machine is missing. In the absence of a primary DNS suffix, short unqualified names may not resolve through DNS |
0x3F2 | Det primære DNS-suffiks for denne computer (%1) stemmer ikke overens med det Active Directory-domæne (%2), som det er knyttet til. |
The primary DNS suffix for this machine (%1) does not match the Active Directory domain (%2) that it is currently joined to. |
0x3F4 | Der opstod en fejl under forsøg på at læse den lokale hosts-fil. |
There was an error while attempting to read the local hosts file. |
0x3F6 | Der opstod en timeout for navnefortolkningen for navnet %1, da ingen af de konfigurerede DNS-servere svarede. |
Name resolution for the name %1 timed out after none of the configured DNS servers responded. |
0x3FF | Tabellen med politikker for navneoversættelse er beskadiget. DNS-oversættelse lykkes først, når problemet er løst. Kontakt netværksadministratoren. Du kan finde flere oplysninger ved at læse politiktabellen for reglen %1 mislykkedes med fejlen %2 |
Name resolution policy table has been corrupted. DNS resolution will fail until it is fixed. Contact your network administrator. For more information: read policy table for rule %1 failed with error %2 |
0x1F41 | Tjenesten DNS Client kunne ikke startes. RPC-grænsefladen (Remote Procedure Call) for denne tjeneste kunne ikke startes. Du kan løse problemet ved at genstarte tjenesterne RPC og DNS Client. Hvis du vil gøre dette, skal du bruge følgende kommandoer i en kommandoprompt: (1) skriv \"net start rpc\" for at starte RPC-tjenesten, og (2) skriv \"net start dnscache\" for at starte tjenesten DNS Client. Se hændelsesoplysningerne for at få specifikke fejlkodeoplysninger. |
Unable to start DNS Client service. Could not start the Remote Procedure Call (RPC) interface for this service. To correct the problem, you may restart the RPC and DNS Client services. To do so, use the following commands at a command prompt: (1) type 'net start rpc' to start the RPC service, and (2) type 'net start dnscache' to start the DNS Client service. See event details for specific error code information. |
0x1F42 | Tjenesten DNS Client kunne ikke startes, fordi systemet ikke kunne allokere hukommelse og muligvis ikke har tilstrækkelig hukommelse. Luk alle unødvendige programmer, eller genstart computeren. Se hændelsesoplysningerne for at få specifikke fejlkodeoplysninger. |
Unable to start DNS Client service because the system failed to allocate memory and may be out of available memory. Try closing any applications not in use or reboot the computer. See event details for specific error code information. |
0x1F43 | The system failed to register network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS Server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe cause of this DNS registration failure was because the DNS update request timed out after being sent to the specified DNS Server. This is probably because the authoritative DNS server for the name being updated is not running.%n%nYou can manually retry registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your network systems administrator to verify network conditions. |
The system failed to register network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS Server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe cause of this DNS registration failure was because the DNS update request timed out after being sent to the specified DNS Server. This is probably because the authoritative DNS server for the name being updated is not running.%n%nYou can manually retry registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your network systems administrator to verify network conditions. |
0x1F44 | The system failed to register network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe cause of this DNS registration failure was because of DNS server failure. This may be due to a zone transfer that has locked the DNS server for the applicable zone that your computer needs to register itself with.%n%n(The applicable zone should typically correspond to the Adapter-specific Domain Suffix that was indicated above.) You can manually retry registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your network systems administrator to verify network conditions. |
The system failed to register network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe cause of this DNS registration failure was because of DNS server failure. This may be due to a zone transfer that has locked the DNS server for the applicable zone that your computer needs to register itself with.%n%n(The applicable zone should typically correspond to the Adapter-specific Domain Suffix that was indicated above.) You can manually retry registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your network systems administrator to verify network conditions. |
0x1F45 | The system failed to register network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason it could not register was because either: (a) the DNS server does not support the DNS dynamic update protocol, or (b) the primary zone authoritative for the registering names does not currently accept dynamic updates.%n%nTo add or register a DNS host (A or AAAA) resource record using the specific DNS name for this adapter, contact your DNS server or network systems administrator. |
The system failed to register network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason it could not register was because either: (a) the DNS server does not support the DNS dynamic update protocol, or (b) the primary zone authoritative for the registering names does not currently accept dynamic updates.%n%nTo add or register a DNS host (A or AAAA) resource record using the specific DNS name for this adapter, contact your DNS server or network systems administrator. |
0x1F46 | The system failed to register network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe 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.%n%nTo register a DNS host (A or AAAA) resource record using the specific DNS domain name for this adapter, contact your DNS server or network systems administrator. |
The system failed to register network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe 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.%n%nTo register a DNS host (A or AAAA) resource record using the specific DNS domain name for this adapter, contact your DNS server or network systems administrator. |
0x1F47 | The system failed to register network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe 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.%n%nYou 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. See event details for specific error code information. |
The system failed to register network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe 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.%n%nYou 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. See event details for specific error code information. |
0x1F48 | The system failed to register network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason the DNS update request could not be completed was because of a system problem. 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. See event details for specific error code information. |
The system failed to register network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason the DNS update request could not be completed was because of a system problem. 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. See event details for specific error code information. |
0x1F49 | The system failed to register pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address :%n %6%n%nThe reason that the system could not register these RRs was because the update request that was sent to the specified DNS server timed out. This is probably because the authoritative DNS server for the name being registered is not running.%n%nYou 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. See event details for specific error code information. |
The system failed to register pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address :%n %6%n%nThe reason that the system could not register these RRs was because the update request that was sent to the specified DNS server timed out. This is probably because the authoritative DNS server for the name being registered is not running.%n%nYou 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. See event details for specific error code information. |
0x1F4A | The system failed to register pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address :%n %6%n%nThe cause was DNS server failure. This may be because the reverse lookup zone is busy or missing on the DNS server that your computer needs to update. In most cases, this is a minor problem because it does not affect normal (forward) name resolution.%n%nIf reverse (address-to-name) resolution is required for your computer, 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. See event details for specific error code information. |
The system failed to register pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address :%n %6%n%nThe cause was DNS server failure. This may be because the reverse lookup zone is busy or missing on the DNS server that your computer needs to update. In most cases, this is a minor problem because it does not affect normal (forward) name resolution.%n%nIf reverse (address-to-name) resolution is required for your computer, 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. See event details for specific error code information. |
0x1F4B | The system failed to register pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address :%n %6%n%nThe reason that the system could not register these RRs was because (a) either the DNS server does not support the DNS dynamic update protocol, or (b) the authoritative zone where these records are to be registered does not allow dynamic updates.%n%nTo register DNS pointer (PTR) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator. |
The system failed to register pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address :%n %6%n%nThe reason that the system could not register these RRs was because (a) either the DNS server does not support the DNS dynamic update protocol, or (b) the authoritative zone where these records are to be registered does not allow dynamic updates.%n%nTo register DNS pointer (PTR) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator. |
0x1F4C | The system failed to register pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address :%n %6%n%nThe reason that the system could not register these RRs was because the DNS server refused the update request. The cause of this could be (a) your computer is not allowed to update the adapter-specified DNS domain name, or (b) because the DNS server authoritative for the specified name does not support the DNS dynamic update protocol.%n%nTo register the DNS pointer (PTR) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator. |
The system failed to register pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address :%n %6%n%nThe reason that the system could not register these RRs was because the DNS server refused the update request. The cause of this could be (a) your computer is not allowed to update the adapter-specified DNS domain name, or (b) because the DNS server authoritative for the specified name does not support the DNS dynamic update protocol.%n%nTo register the DNS pointer (PTR) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator. |
0x1F4D | The system failed to register pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address :%n %6%n%nThe reason that the system could not register these RRs was because of a security related problem. The cause of this could be (a) your computer does not have permissions to register and update the specific DNS domain name set for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request.%n%nYou 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. |
The system failed to register pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address :%n %6%n%nThe reason that the system could not register these RRs was because of a security related problem. The cause of this could be (a) your computer does not have permissions to register and update the specific DNS domain name set for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request.%n%nYou 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. |
0x1F4E | The system failed to register pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address :%n %6%n%nThe reason the system could not register these RRs during the update request was because of a system problem. 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. See event details for specific error code information. |
The system failed to register pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address :%n %6%n%nThe reason the system could not register these RRs during the update request was because of a system problem. 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. See event details for specific error code information. |
0x1F4F | The system failed to register host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason the system could not register these RRs was because the update request it sent to the DNS server timed out. The most likely cause of this is that the DNS server authoritative for the name it was attempting to register or update is not running at this time.%n%nYou 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. |
The system failed to register host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason the system could not register these RRs was because the update request it sent to the DNS server timed out. The most likely cause of this is that the DNS server authoritative for the name it was attempting to register or update is not running at this time.%n%nYou 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. |
0x1F50 | The system failed to register host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason the system could not register these RRs was because the DNS server failed the update request. The most likely cause of this is that the authoritative DNS server required to process this update request has a lock in place on the zone, probably because a zone transfer is in progress.%n%nYou 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. |
The system failed to register host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason the system could not register these RRs was because the DNS server failed the update request. The most likely cause of this is that the authoritative DNS server required to process this update request has a lock in place on the zone, probably because a zone transfer is in progress.%n%nYou 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. |
0x1F51 | The system failed to register host (A or AAAA) resource records for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nEither the DNS server does not support the DNS dynamic update protocol or the authoritative zone for the specified DNS domain name does not accept dynamic updates.%n%nTo register the DNS host (A or AAAA) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator. |
The system failed to register host (A or AAAA) resource records for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nEither the DNS server does not support the DNS dynamic update protocol or the authoritative zone for the specified DNS domain name does not accept dynamic updates.%n%nTo register the DNS host (A or AAAA) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator. |
0x1F52 | The system failed to register host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason the system could not register these RRs was because the DNS server contacted refused the update request. The reasons for this might be (a) you are not allowed to update the specified DNS domain name, or (b) because the DNS server authoritative for this name does not support the DNS dynamic update protocol.%n%nTo register the DNS host (A or AAAA) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator. |
The system failed to register host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason the system could not register these RRs was because the DNS server contacted refused the update request. The reasons for this might be (a) you are not allowed to update the specified DNS domain name, or (b) because the DNS server authoritative for this name does not support the DNS dynamic update protocol.%n%nTo register the DNS host (A or AAAA) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator. |
0x1F53 | The system failed to register host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason the system could not register these RRs was because of a security related problem. The cause of this could be (a) your computer does not have permissions to register and update the specific DNS domain name set for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request.%n%nYou 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. See event details for specific error code information. |
The system failed to register host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason the system could not register these RRs was because of a security related problem. The cause of this could be (a) your computer does not have permissions to register and update the specific DNS domain name set for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request.%n%nYou 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. See event details for specific error code information. |
0x1F54 | The system failed to register host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason the system could not register these RRs during the update request was because of a system problem. 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. See event details for specific error code information. |
The system failed to register host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason the system could not register these RRs during the update request was because of a system problem. 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. See event details for specific error code information. |
0x1F55 | The system failed to update and remove registration for the network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason for this failure is because the DNS server it sent the update request to timed out. The most likely cause of this failure is that the DNS server authoritative for the zone where the registration was originally made is either not running or unreachable through the network at this time. |
The system failed to update and remove registration for the network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason for this failure is because the DNS server it sent the update request to timed out. The most likely cause of this failure is that the DNS server authoritative for the zone where the registration was originally made is either not running or unreachable through the network at this time. |
0x1F56 | The system failed to update and remove registration for the network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason for this failure is because the DNS server it sent the update to failed the update request. A possible cause of this failure is that the DNS server required to process this update request has a lock in place on the zone, probably because a zone transfer is in progress.%n%n |
The system failed to update and remove registration for the network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason for this failure is because the DNS server it sent the update to failed the update request. A possible cause of this failure is that the DNS server required to process this update request has a lock in place on the zone, probably because a zone transfer is in progress.%n%n |
0x1F57 | The system failed to update and remove registration for the network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason for this failure is because the DNS server sent the update either (a) does not support the DNS dynamic update protocol, or (b) the authoritative zone for the specified DNS domain name does not currently accept DNS dynamic updates. |
The system failed to update and remove registration for the network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason for this failure is because the DNS server sent the update either (a) does not support the DNS dynamic update protocol, or (b) the authoritative zone for the specified DNS domain name does not currently accept DNS dynamic updates. |
0x1F58 | The system failed to update and remove registration for the network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason the system could not perform the update request was the DNS server contacted refused update request. The cause of this is (a) this computer is not allowed to update the specified DNS domain name, or (b) because the DNS server authoritative for the zone that requires updating does not support the DNS dynamic update protocol. |
The system failed to update and remove registration for the network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason the system could not perform the update request was the DNS server contacted refused update request. The cause of this is (a) this computer is not allowed to update the specified DNS domain name, or (b) because the DNS server authoritative for the zone that requires updating does not support the DNS dynamic update protocol. |
0x1F59 | The system failed to update and remove registration for the network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason the system could not perform the update request was because of a security related problem. The cause of this could be (a) your computer does not have permissions to register and update the specific DNS domain name set for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request.%n%nSee event details for specific error code information. |
The system failed to update and remove registration for the network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason the system could not perform the update request was because of a security related problem. The cause of this could be (a) your computer does not have permissions to register and update the specific DNS domain name set for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request.%n%nSee event details for specific error code information. |
0x1F5A | The system failed to update and remove the DNS registration for the network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe system could not update to remove this DNS registration because of a system problem. See event details for specific error code information. |
The system failed to update and remove the DNS registration for the network adapter with settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe system could not update to remove this DNS registration because of a system problem. See event details for specific error code information. |
0x1F5B | The system failed to update and remove pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address :%n %6%n%nThe system could not remove these PTR RRs because the update request timed out while awaiting a response from the DNS server. This is probably because the DNS server authoritative for the zone that requires update is not running. |
The system failed to update and remove pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address :%n %6%n%nThe system could not remove these PTR RRs because the update request timed out while awaiting a response from the DNS server. This is probably because the DNS server authoritative for the zone that requires update is not running. |
0x1F5C | The system failed to update and remove pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address : %6%n%nThe system could not remove these PTR RRs because the DNS server failed the update request. A possible cause is that a zone transfer is in progress, causing a lock for the zone at the DNS server authorized to perform the updates for these RRs. |
The system failed to update and remove pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address : %6%n%nThe system could not remove these PTR RRs because the DNS server failed the update request. A possible cause is that a zone transfer is in progress, causing a lock for the zone at the DNS server authorized to perform the updates for these RRs. |
0x1F5D | The system failed to update and remove pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address :%n %6%n%nThe system could not remove these PTR RRs because either the DNS server does not support the DNS dynamic update protocol or the authoritative zone that contains these RRs does not accept dynamic updates. |
The system failed to update and remove pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address :%n %6%n%nThe system could not remove these PTR RRs because either the DNS server does not support the DNS dynamic update protocol or the authoritative zone that contains these RRs does not accept dynamic updates. |
0x1F5E | The system failed to update and remove pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address :%n %6%n%nThe system could not remove these PTR RRs because the DNS server refused the update request. The cause of this might be (a) this computer is not allowed to update the specified DNS domain name specified by these settings, or (b) because the DNS server authorized to perform updates for the zone that contains these RRs does not support the DNS dynamic update protocol. |
The system failed to update and remove pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address :%n %6%n%nThe system could not remove these PTR RRs because the DNS server refused the update request. The cause of this might be (a) this computer is not allowed to update the specified DNS domain name specified by these settings, or (b) because the DNS server authorized to perform updates for the zone that contains these RRs does not support the DNS dynamic update protocol. |
0x1F5F | The system failed to update and remove pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address :%n %6%n%nThe system could not remove these PTR RRs because of a security related problem. The cause of this could be that (a) your computer does not have permissions to remove and update the specific DNS domain name or IP addresses configured for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request. See event details for specific error code information. |
The system failed to update and remove pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address :%n %6%n%nThe system could not remove these PTR RRs because of a security related problem. The cause of this could be that (a) your computer does not have permissions to remove and update the specific DNS domain name or IP addresses configured for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request. See event details for specific error code information. |
0x1F60 | The system failed to update and remove pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address :%n %6%n%nThe system could not remove these PTR RRs because because of a system problem. See event details for specific error code information. |
The system failed to update and remove pointer (PTR) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Adapter-specific Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address :%n %6%n%nThe system could not remove these PTR RRs because because of a system problem. See event details for specific error code information. |
0x1F61 | The system failed to update and remove host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%n The system could not remove these host (A or AAAA) RRs because the update request timed out while awaiting a response from the DNS server. This is probably because the DNS server authoritative for the zone where these RRs need to be updated is either not currently running or reachable on the network. |
The system failed to update and remove host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%n The system could not remove these host (A or AAAA) RRs because the update request timed out while awaiting a response from the DNS server. This is probably because the DNS server authoritative for the zone where these RRs need to be updated is either not currently running or reachable on the network. |
0x1F62 | The system failed to update and remove host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe system could not remove these host (A or AAAA) RRs because the DNS server failed the update request. A possible cause is that a zone transfer is in progress, causing a lock for the zone at the DNS server authorized to perform the updates for these RRs. |
The system failed to update and remove host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe system could not remove these host (A or AAAA) RRs because the DNS server failed the update request. A possible cause is that a zone transfer is in progress, causing a lock for the zone at the DNS server authorized to perform the updates for these RRs. |
0x1F63 | The system failed to update and remove host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason for this failure is because the DNS server sent the update either (a) does not support the DNS dynamic update protocol, or (b) the authoritative zone for the DNS domain name specified in these host (A or AAAA) RRs does not currently accept DNS dynamic updates. |
The system failed to update and remove host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason for this failure is because the DNS server sent the update either (a) does not support the DNS dynamic update protocol, or (b) the authoritative zone for the DNS domain name specified in these host (A or AAAA) RRs does not currently accept DNS dynamic updates. |
0x1F64 | The system failed to update and remove host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe request to remove these records failed because the DNS server refused the update request. The cause of this might be that either (a) this computer is not allowed to update the DNS domain name specified by these settings, or (b) because the DNS server authorized to perform updates for the zone that contains these RRs does not support the DNS dynamic update protocol. |
The system failed to update and remove host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe request to remove these records failed because the DNS server refused the update request. The cause of this might be that either (a) this computer is not allowed to update the DNS domain name specified by these settings, or (b) because the DNS server authorized to perform updates for the zone that contains these RRs does not support the DNS dynamic update protocol. |
0x1F65 | The system failed to update and remove host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason for this failure was because of a security related problem. The cause of this could be that (a) your computer does not have permissions to remove and update the specific DNS domain name or IP addresses configured for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request. See event details for specific error code information. |
The system failed to update and remove host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason for this failure was because of a security related problem. The cause of this could be that (a) your computer does not have permissions to remove and update the specific DNS domain name or IP addresses configured for this adapter, or (b) there might have been a problem negotiating valid credentials with the DNS server during the processing of the update request. See event details for specific error code information. |
0x1F66 | The system failed to update and remove host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason the update request failed was because of a system problem. See event details for specific error code information. |
The system failed to update and remove host (A or AAAA) resource records (RRs) for network adapter%nwith settings:%n%n Adapter Name : %1%n Host Name : %2%n Primary Domain Suffix : %3%n DNS server list :%n %4%n Sent update to server : %5%n IP Address(es) :%n %6%n%nThe reason the update request failed was because of a system problem. See event details for specific error code information. |
0x30000000 | Oplysninger |
Info |
0x300000B4 | Starttilstand |
Start State |
0x300000B5 | Sluttilstand |
End State |
0x300000B6 | Lukket tilstand |
Closed State |
0x300000B7 | Åben tilstand |
Open State |
0x300000B8 | Forbindelsestilstand |
Connect State |
0x300000B9 | Lyttetilstand |
Listen State |
0x300000BA | Tilknytningstilstand |
Association State |
0x300000BB | Godkendelsestilstand |
Authentication State |
0x300000BC | Oprettet tilstand |
Established State |
0x50000002 | Fejl |
Error |
0x50000003 | Advarsel |
Warning |
0x90000001 | Microsoft-Windows-DNS Client Events |
Microsoft-Windows-DNS Client Events |
0x90000002 | Microsoft-Windows-DNS Client Events/funktionel |
Microsoft-Windows-DNS Client Events/Operational |
0x90000003 | System |
System |
0xB00003E8 | Der er ikke konfigureret nogen IPv4 DNS-servere for nogen grænseflader på denne vært. Konfigurer DNS-serverindstillingerne, eller forny dine dynamiske IP-indstillinger. |
There are currently no IPv4 DNS servers configured for any interface on this host. Please configure DNS server settings, or renew your dynamic IP settings. |
0xB00003E9 | Grænseflade: %1 Totalt antal DNS-servere: %2 Indeks: %3 Adresse: %6 (%4) |
Interface: %1 Total DNS Server Count: %2 Index: %3 Address: %6 (%4) |
0xB00003EA | Den DNS-server, der sendes en forespørgsel til for grænsefladen %1, er ændret til %3 |
The DNS server being queried for interface %1 has changed to %3 |
0xB00003EB | Følgende DNS-servere blev valideret som aktive servere, der kan betjene klienten. %2 |
The following DNS server(s) were successfully validated as active servers that can service this client. %2 |
0xB00003ED | Klienten kunne ikke validere følgende som aktive DNS-servere, der kan betjene klienten. Serverne kan være midlertidigt utilgængelige, eller de kan være konfigureret forkert. %2 |
The client was unable to validate the following as active DNS server(s) that can service this client. The server(s) may be temporarily unavailable, or may be incorrectly configured. %2 |
0xB00003F7 | Der opstod en timeout for navnefortolkningen for navnet %1, da DNS-serveren %3 ikke svarede. |
Name resolution for the name %1 timed out after the DNS server %3 did not respond. |
0xB00003F8 | Der opstod en fejl, da navnet %1 ikke blev fundet. Kontrollér, at navnet er korrekt angivet. Svaret blev sendt af serveren på adresse %3. |
A name not found error was returned for the name %1. Check to ensure that the name is correct. The response was sent by the server at %3. |
0xB00003F9 | DNS-serverens svar på en forespørgsel for navnet %1 angiver, at der ikke er nogen tilgængelige poster af den anmodede type, men det kunne ikke angives, om der findes andre typer poster for det samme navn. |
The DNS server's response to a query for name %1 indicates that no records of the type queried are available, but could indicate that other records for the same name are present. |
0xB00003FA | Svaret på forespørgslen %1 var en lokal IP-linkadresse %3. Svaret blev sendt af serveren på adressen %5. |
The response for the query %1 was a Link Local IP address %3. The response was sent by the server at %5. |
0xB00003FC | Læs politiktabel for DNS-navnefortolkning: Nøglenavn %1: DNSSEC-indstillinger: DnsSecValidationRequired %2, DnsQueryOverIPSec %3, DnsEncryption %4 Direct Access-indstillinger: DirectAccessServerList %5, EnableRemoteIPSEC %6 RemoteEncryption %7 ProxyType %8 ProxyName %9 |
Read DNS Name Resolution Policy Table: Key Name %1: DNSSEC Settings: DnsSecValidationRequired %2, DnsQueryOverIPSec %3, DnsEncryption %4 Direct Access Settings: DirectAccessServerList %5, EnableRemoteIPSEC %6 RemoteEncryption %7 ProxyType %8 ProxyName %9 |
0xB00003FD | Overensstemmende effektiv politik for forespørgselsnavn %1: Nøglenavn %2: DnsSecValidationRequired %3, DnsQueryOverIPSec %4, DnsEncryption %5 DirectAccessServerList %6, ProxyType %7 ProxyName %8 |
Matched Effective policy for query name %1: Key Name %2: DnsSecValidationRequired %3, DnsQueryOverIPSec %4, DnsEncryption %5 DirectAccessServerList %6, ProxyType %7 ProxyName %8 |
0xB00003FE | Navnefortolkningen for navnet %1 foretager ikke fallback til LLMNR eller NetBIOS |
Name resolution for the name, %1, will not fall back to LLMNR or NetBIOS |
0xB0000400 | Transaktions-id'et for svar på forespørgslen %1 fra serveren %3 stemte ikke overens |
Transaction ID of the response for query %1 from server %3 did not match |
0xB0000401 | DNS-server-IP'en %3 for svar på forespørgslen %1 er ikke konfigureret på klienten |
The DNS server IP %3 of the response for query %1 is not configured on the client |
0xB0000402 | Spørgsmålet (%2) i svaret fra serveren %4 stemmer ikke overens med det oprindelige spørgsmål %1 |
The question (%2) in the response from server %4 does not match the original question %1 |
0xB0000403 | Det lykkedes ikke at udføre DNS-navneoversættelse for navnet, %1, da klienten ikke kunne oprette forbindelse til DNS-servere. Mindst en af brugergrænsefladerne er ikke et privat netværk, og navneoversættelse anvender ikke LLMNR eller NetBIOS igen |
DNS Name resolution for the name, %1, failed because the client was unable to contact DNS servers. At least one of the interfaces is not in a private network and name resolution will not fall back to LLMNR or NetBIOS |
0xB0000404 | Overensstemmende effektiv politik for forespørgselsnavn %1: Nøglenavn %2: DnsSecValidationRequired %3, DnsQueryOverIPSec %4, DnsEncryption %5 DirectAccessServerList %6, ProxyType %7 ProxyName %8 GenericServerList %9 IdnConfig %10 |
Matched effective policy for query name %1: Key Name %2: DnsSecValidationRequired %3, DnsQueryOverIPSec %4, DnsEncryption %5 DirectAccessServerList %6, ProxyType %7 ProxyName %8 GenericServerList %9 IdnConfig %10 |
0xB0000BB8 | DNS-forespørgsel er igangsat for navnet %1 og typen %2 med forespørgselsindstillingerne %3 |
DNS Query is initiated for the name %1 and for the type %2 with query options %3 |
0xB0000BB9 | DNS-forespørgslen er fuldført med resultatet %1 |
DNS Query operation is completed with result %1 |
0xB0000BBA | DNS-cacheopslag er igangsat for navnet %1 og typen %2 med forespørgselsindstillingerne %3 |
DNS Cache lookup is initiated for the name %1 and for the type %2 with query options %3 |
0xB0000BBB | DNS-cacheopslag for navnet %1 og typen %2 er fuldført med resultatet %3 |
DNS Cache lookup operation for the name %1 and for the type %2 is completed with result %3 |
0xB0000BBC | DNS-FQDN-forespørgsel er igangsat for navnet %1 og typen %2 med forespørgselsindstillingerne %3 |
DNS FQDN Query is initiated for the name %1 and for the type %2 with query options %3 |
0xB0000BBD | DNS-FQDN-forespørgsel for navnet %1 og typen %2 er fuldført med resultatet %3 |
DNS FQDN Query operation for the name %1 and for the type %2 is completed with result %3 |
0xB0000BBE | DNS-forespørgsel er kaldt for navnet %1, typen %2, forespørgselsvalgene %3, serverlisten %4, isNetwork-forespørgsel %5, netværksindeks %6, grænsefladeindeks %7, er asynkron forespørgsel %8 |
DNS query is called for the name %1, type %2, query options %3, Server List %4, isNetwork query %5, network index %6, interface index %7, is asynchronous query %8 |
0xB0000BBF | DnsQueryEx for navnet %1 venter |
DnsQueryEx for the name %1 is pending |
0xB0000BC0 | DNS-forespørgsel er fuldført for navnet %1, typen %2, forespørgselsvalgene %3 med status %4 resultaterne %5 |
DNS query is completed for the name %1, type %2, query options %3 with status %4 Results %5 |
0xB0000BC1 | Netværksforespørgsel er initieret for navnet %1 (er parallel forespørgsel %2) på netværksindeks %3 med grænsefladetæller %4 med første grænsefladenavn %5, lokale adresser %6 og DNS-servere %7 |
Network query initiated for the name %1 (is parallel query %2) on network index %3 with interface count %4 with first interface name %5, local addresses %6 and Dns Servers %7 |
0xB0000BC2 | DNS-forespørgsel er sendt til DNS-serveren %3 for navnet %1 og typen %2 |
DNS Query sent to DNS Server %3 for name %1 and type %2 |
0xB0000BC3 | Der er modtaget svar fra DNS-serveren %3 for navnet %1 og typen %2 med svarstatus %4 |
Received response from DNS Server %3 for name %1 and type %2 with response status %4 |
0xB0000BC4 | NETBIOS-forespørgsel er initieret for navnet %1 på netværksindeks %2 med grænsefladetæller %3 med første grænsefladenavn %4 og lokale adresser %5 |
NETBIOS query is initiated for name %1 on network index %2 with inteface count %3 with first interface name %4 and local addresses %5 |
0xB0000BC5 | NETBIOS-forespørgsel er fuldført for navnet %1 med status %2 og resultaterne %3 |
NETBIOS query is completed for name %1 with status %2 and results %3 |
0xB0000BC6 | NETBIOS-forespørgsel for navnet %1 venter |
NETBIOS query for the name %1 is pending |
0xB0000BC7 | DnsQueryEx er annulleret for navnet %1 |
DnsQueryEx is canceled for the name %1 |
0xB0000BC8 | Cacheopslag er kaldt for navnet %1, type %2, indstillinger %3 og grænsefladeindeks %4 |
Cache lookup called for name %1, type %2, options %3 and interface index %4 |
0xB0000BCA | Cacheopslag for navnet %1, typen %2 og indstillingen %3 har returneret %4 med resultaterne %5 |
Cache lookup for name %1, type %2 and option %3 returned %4 with results %5 |
0xB0000BCB | Forespørgselstråd er kaldt for navnet %1, type %2, grænsefladeindeks %3 og netværksindeks %4 |
Query wire called for name %1, type %2, interface index %3 and network index %4 |
0xB0000BCC | Forespørgselssvar for navnet %1, typen %2, grænsefladeindekset %3 og netværksindekset %4 har returneret %5 med resultaterne %6 |
Query response for name %1, type %2, interface index %3 and network index %4 returned %5 with results %6 |
0xB000EA64 | Fejl: %1. Placering: %2. Kontekst: %3 |
Error: %1 Location: %2 Context: %3 |
0xB000EA65 | Advarsel: %1. Placering: %2. Kontekst: %3 |
Warning: %1 Location: %2 Context: %3 |
0xB000EA66 | Overgået til tilstand: %1 Kontekst: %2 |
Transitioned to State: %1 Context: %2 |
0xB000EA67 | Opdateret kontekst: %1 Årsag til opdatering: %2 |
Updated Context: %1 Update Reason: %2 |
0xB000EAC5 | SourceAddress: %1 SourcePort: %2 DestinationAddress: %3 DestinationPort: %4 Protocol: %5 ReferenceContext: %6 |
SourceAddress: %1 SourcePort: %2 DestinationAddress: %3 DestinationPort: %4 Protocol: %5 ReferenceContext: %6 |
0xB000EAC7 | Grænseflade-GUID: %1 IfIndex: %2 Grænseflade-LUID: %3 ReferenceContext: %4 |
Interface Guid: %1 IfIndex: %2 Interface Luid: %3 ReferenceContext: %4 |
0xD0000001 | statisk |
static |
0xD0000002 | dynamisk |
dynamic |