| 211 | DHCP Users |
DHCP Users |
| 212 | 对 DHCP 服务拥有只读权限的成员 |
Members who have view-only access to the DHCP service |
| 213 | DHCP Administrators |
DHCP Administrators |
| 214 | 对 DHCP 服务拥有管理权限的成员 |
Members who have administrative access to the DHCP Service |
| 0x3E8 | DHCP 服务接收到长度为 %2 的未知选项 %1。原始选项数据如下。 |
The DHCP service received the unknown option %1, with a length of %2. The raw option data is given below. |
| 0x3E9 | DHCP 服务无法用服务控制器注册。发生了以下错误: %n%1。 |
The DHCP service failed to register with Service Controller. The following error occurred: %n%1. |
| 0x3EA | DHCP 服务无法初始化其全局参数。发生了以下错误: %n%1 |
The DHCP service failed to initialize its global parameters. The following error occurred: %n%1 |
| 0x3EB | DHCP 服务无法初始化其注册表参数。发生了以下错误: %n%1 |
The DHCP service failed to initialize its registry parameters. The following error occurred: %n%1 |
| 0x3EC | DHCP 服务无法初始化数据库。发生了以下错误: %n%1 |
The DHCP service failed to initialize the database. The following error occurred: %n%1 |
| 0x3ED | DHCP 服务无法初始化 Winsock 启动。发生了以下错误: %n%1 |
The DHCP service failed to initialize Winsock startup. The following error occurred: %n%1 |
| 0x3EE | 无法将 DHCP 服务器作为 RPC 服务器启动。发生了以下错误: %n%1 |
The DHCP service failed to start as a RPC server. The following error occurred : %n%1 |
| 0x3EF | DHCP 服务无法初始化 winsock 数据。发生了以下错误: %n%1 |
The DHCP service failed to initialize Winsock data. The following error occurred: %n%1 |
| 0x3F0 | DHCP 服务正在关闭，因为以下错误: %n%1 |
The DHCP service is shutting down due to the following error: %n%1 |
| 0x3F1 | DHCP 服务在清除挂起的客户端记录时遇到了以下错误: %n%1 |
The DHCP service encountered the following error while cleaning up the pending client records: %n%1 |
| 0x3F2 | DHCP 服务在清除用户数据库时遇到了以下错误: %n%1 |
The DHCP service encountered the following error while cleaning up the database: %n%1 |
| 0x3F3 | 客户端 %2 请求地址 %1 得到的 DHCP 服务的答复是 NACK(negative acknowledgement message)。 |
The DHCP service issued a NACK (negative acknowledgement message) to the client, %2, for the address, %1. |
| 0x3F4 | DHCP 客户端 %2 拒绝了地址 %1。 |
The DHCP client, %2, declined the address %1. |
| 0x3F5 | DHCP 客户端 %2 释放了地址 %1。 |
The DHCP Client, %2, released the address %1. |
| 0x3F8 | DHCP 服务在备份数据库时遇到了以下错误: %n%1 |
The DHCP service encountered the following error when backing up the database: %n%1 |
| 0x3F9 | DHCP 服务在备份注册表配置时遇到了以下错误: %n%1 |
The DHCP service encountered the following error when backing up the registry configuration: %n%1 |
| 0x3FA | DHCP 服务无法还原数据库。发生了以下错误: %n%1 |
The DHCP service failed to restore the database. The following error occurred: %n%1 |
| 0x3FB | DHCP 服务无法还原 DHCP 注册表配置。发生了以下错误: %n%1 |
The DHCP service failed to restore the DHCP registry configuration. The following error occurred: %n%1 |
| 0x3FC | 用了百分之 %2 的作用域 %1，只剩下 %3 个 IP 地址。 |
Scope, %1, is %2 percent full with only %3 IP addresses remaining. |
| 0x3FD | DHCP 服务无法成功加载 JET 数据库的库文件。 |
The DHCP service could not load the JET database library successfully. |
| 0x3FE | DHCP 服务无法使用数据库。如果该服务是从 NT3.51 或以前版本升级后的第一次启动，那么你需要在 DHCP 数据库上运行 upg351db.exe 实用程序将其转换成新的 JET 数据库格式。完成更新工作后请重新启动 DHCP 服务器。 |
The DHCP service could not use the database. If this service was started for the first time after the upgrade from NT 3.51 or earlier, you need to run the utility, upg351db.exe, on the DHCP database to convert it to the new JET database format. Restart the DHCP service after you have upgraded the database. |
| 0x3FF | 因为现存数据库需要转换到 Windows 2000 格式，所以 DHCP服务将终止。通过处理程序 jetconv 的转换程序已经开始。不要重新启动机器或终止 jetconv 程序。转换需要花十分钟的时间(根据数据库大小而定)。请单击“确定”，终止 DHCP。要使数据库转换成功，这是必需的。注意: 转换完成时，DHCP 服务将被自动重新启动。要检查转换的状态，请检查JETCONV 程序的应用程序事件日志。 |
The DHCP service will now terminate because the existing database needs conversion to Windows 2000 format. The conversion via the jetconv process, has initiated. Do not reboot or stop the jetconv process. The conversion may take up to 10 minutes depending on the size of the database. Terminate DHCP now by clicking OK. This is required for the database conversion to succeed. NOTE: The DHCP service will be restarted automatically when the conversion is completed. To check conversion status, look at the Application event log for the jetconv process. |
| 0x400 | DHCP 服务已初始化并就绪 |
The DHCP service has initialized and is ready |
| 0x401 | DHCP 服务无法从注册表中读取 BOOTP 文件表。DHCP 服务将无法对指定启动文件名的 BOOTP 请求作出反应。 |
The DHCP service was unable to read the BOOTP file table from the registry. The DHCP service will be unable to respond to BOOTP requests that specify the boot file name. |
| 0x402 | DHCP 服务无法从注册表中读取全局 BOOTP 文件名。 |
The DHCP service was unable to read the global BOOTP file name from the registry. |
| 0x403 | 无法向审核日志文件追加内容。 |
The audit log file cannot be appended. |
| 0x404 | DHCP 服务无法初始化审核日志。出现以下错误: %n%1 |
The DHCP service failed to initialize the audit log. The following error occurred: %n%1 |
| 0x405 | DHCP 服务无法 PING 新的 IP 地址。该地址已租给客户端。 |
The DHCP service was unable to ping for a new IP address. The address was leased to the client. |
| 0x406 | 无法备份审核日志文件。出现了以下错误: %n%1 |
The audit log file could not be backed up. The following error occurred: %n%1 |
| 0x407 | 安装的服务器 callout .dll 文件造成意外事件。意外事件为: %n%1。服务器忽略了这个意外事件。此后发生的其他意外事件也同样会被忽略。 |
The installed server callout .dll file has caused an exception. The exception was: %n%1. The server has ignored this exception. All further exceptions will be ignored. |
| 0x408 | 安装的服务器 callout .dll 文件造成意外事件。意外事件为: %n%1。服务器忽略了这个意外事件，并且未能加载 .dll 文件。 |
The installed server callout .dll file has caused an exception. The exception was: %n%1. The server has ignored this exception and the .dll file could not be loaded. |
| 0x409 | DHCP 服务已成功加载一个或多个 Callout DLL。 |
The DHCP service has successfully loaded one or more callout DLLs. |
| 0x40A | DHCP 服务未能加载一个或多个 Callout DLL。出现了以下错误: %n%1 |
The DHCP service has failed to load one or more callout DLLs. The following error occured: %n%1 |
| 0x40B | DHCP 服务无法在这台计算机上创建或搜索DHCP 用户本地组。错误代码在数据中。 |
The DHCP service was unable to create or lookup the DHCP Users local group on this computer. The error code is in the data. |
| 0x40C | DHCP 服务器无法在这台计算机上创建或搜索 DHCP 管理员 本地组。错误代码在数据中。 |
The DHCP server was unable to create or lookup the DHCP Administrators local group on this computer. The error code is in the data. |
| 0x40D | DHCP 服务开始清理数据库。 |
The DHCP service has started to clean up the database. |
| 0x40E | DHCP 服务已经为单播 IP 地址清理了数据库 -- 恢复了 %1 条租约并从数据库 中删除了 %2 条记录。 |
The DHCP service has cleaned up the database for unicast IP addresses -- %1 leases have been recovered and %2 records have been removed from the database. |
| 0x40F | DHCP 服务已经为多播 IP 地址清理了数据库 -- %1 条租约过期 (做了删除的记号)并且从数据库中删除了 %2 个记录。 |
The DHCP service has cleaned up the database for multicast IP addresses -- %1 leases have expired (been marked for deletion) and %2 records have been removed from the database. |
| 0x410 | DHCP 服务成功地还原了数据库。 |
The DHCP service successfully restored the database. |
| 0x411 | 由于没有任何活动的网络接口静态配置了 IPv4 地址或由于没有任何活动接口，DHCP 服务没有为任何 DHCPv4 客户端提供服务。 |
The DHCP service is not servicing any DHCPv4 clients because none of the active network interfaces have statically configured IPv4 addresses, or there are no active interfaces. |
| 0x412 | 在此计算机上运行的 DHCP/BINL 服务在网络上检查到了一台服务器。如果此服务器不属于任何域，域将列成空。此服务器的 IP 地址在括号中。%1 |
The DHCP/BINL service running on this machine has detected a server on the network. If the server does not belong to any domain, the domain is listed as empty. The IP address of the server is listed in parentheses. %1 |
| 0x413 | 本地计算机上的 DHCP/BINL 服务确定自身已被授权可以启动。它正在为客户端提供服务。 |
The DHCP/BINL service on the local machine has determined that it is authorized to start. It is servicing clients now. |
| 0x414 | 本地计算机上的 DHCP/BINL 服务属于 Windows 管理域 %2，已确定有权启动。它正在为客户端提供服务。 |
The DHCP/BINL service on the local machine, belonging to the Windows Administrative domain %2, has determined that it is authorized to start. It is servicing clients now. |
| 0x415 | 本地计算机上的 DHCP/BINL 服务确定尚未被授权启动。它已终止向客户端提供服务。下列时可能造成这个的可能原因: %n%t此计算机属于一个工作组并遇到另一台为同一网络提供服务的 DHCP 服务器(属于 Windows Administrative Domain)。%n%n%t出现了一个意外的网络错误。 |
The DHCP/BINL service on the local machine has determined that it is not authorized to start. It has stopped servicing clients. The following are some possible reasons for this: %n%tThis machine belongs to a workgroup and has encountered another DHCP Server (belonging to a Windows Administrative Domain) servicing the same network. %n%n%tAn unexpected network error occurred. |
| 0x416 | 本地计算机上属于 Windows Administrative 域 %2 的 DHCP/BINL 服务确定尚未被授权启动。它现在已终止向客户端提供服务。下面是可能造成此现象的一些可能原因: %n%t该计算机属于某个目录服务企业，并且在同一域中未被授权。(有关详细信息，请参阅 DHCP 服务管理工具帮助)。%n%n%t该计算机无法访问其目录服务企业，并且在属于某个目录服务企业的网络(未授权该本地计算机)上遇到另一个 DHCP 服务。%n%n%t遇到某个意外网络错误。 |
The DHCP/BINL service on the local machine, belonging to the Windows Administrative domain %2, has determined that it is not authorized to start. It has stopped servicing clients. The following are some possible reasons for this: %n%tThis machine is part of a directory service enterprise and is not authorized in the same domain. (See help on the DHCP Service Management Tool for additional information). %n%n%tThis machine cannot reach its directory service enterprise and it has encountered another DHCP service on the network belonging to a directory service enterprise on which the local machine is not authorized. %n%n%tSome unexpected network error occurred. |
| 0x417 | 本地计算机上的 DHCP/BINL 服务确定未被授权启动。它现在正在为客户端提供服务。%nDHCP/BINL 确定该计算机最近已升级。如果意欲使该计算机属于某个目录服务企业，则 DHCP 服务必须在该目录服务中得到授权，然后才可开始为客户端提供服务。(请参阅 DHCP 服务管理工具帮助了解授权服务器的信息。) |
The DHCP/BINL service on the local machine has determined that it is authorized to start. It is servicing clients now. %nThe DHCP/BINL service has determined that the machine was recently upgraded. If the machine is intended to belong to a directory service enterprise, the DHCP service must be authorized in the directory service for it to start servicing clients. (See help on DHCP Service Management Tool for authorizing the server). |
| 0x418 | 本地计算机上属于 Windows 域 %2 的 DHCP/BINL 服务确定已被授权启动。它现在正在为客户端提供服务。它已确定该计算机最近已升级。同时也确定该域没有目录服务企业，或是该计算机没有在目录服务中得到授权。所有属于目录服务企业的 DHCP 服务器都应该在目录服务中得到授权，以便为客户端提供服务。(请参阅 DHCP 服务管理工具帮助中有关在目录服务中授权 DHCP 服务器的信息。) |
The DHCP/BINL Service on the local machine, belonging to Windows Domain %2, has determined that it is authorized to start. It is servicing clients now. It has determined that the computer was recently upgraded. It has also determined that either there is no directory service enterprise for the domain or that the computer is not authorized in the directory service. All DHCP services that belong to a directory service enterprise should be authorized in the directory service to service clients. (See help on the DHCP Service Management Tool for authorizing a DHCP service in the directory service). |
| 0x419 | 尝试查找本地计算机的域时，本地计算机上的 DHCP/BINL 服务遇到错误。错误为: %3。 |
The DHCP/BINL service on the local machine encountered an error while trying to find the domain of the local machine. The error was: %3. |
| 0x41A | 本地计算机上的 DHCP/BINL 服务遇到网络错误。错误为: %3。 |
The DHCP/BINL service on the local machine encountered a network error. The error was: %3. |
| 0x41B | DHCP/BINL 服务确定没有授权为此 Windows 域网络上的客户端提供服务: %2。所有属于目录服务企业的 DHCP 服务必须在目录服务中得到授权才能为客户端提供服务。(请参阅 DHCP 服务管理工具帮助中有关在目录服务中授权 DHCP 服务器的信息)。 |
The DHCP/BINL service has determined that it is not authorized to service clients on this network for the Windows domain: %2. All DHCP services that belong to a directory service enterprise must be authorized in the directory service to service clients. (See help on the DHCP Service Management Tool for authorizing a DHCP server in the directory service). |
| 0x41C | 此工作组服务器上的 DHCP/BINL 服务遇到另一个属于域 %2，IP 地址为 %1 的服务器。 |
The DHCP/BINL service on this workgroup server has encountered another server with IP Address, %1, belonging to the domain %2. |
| 0x41D | DHCP/BINL 服务在 IP 地址为 %1 (属于域 %2)的网络上遇到另一个服务器。 |
The DHCP/BINL service has encountered another server on this network with IP Address, %1, belonging to the domain: %2. |
| 0x41E | 该计算机上的 DHCP/BINL 服务即将关闭。原因请参阅以前的事件日志消息。 |
The DHCP/BINL service on this computer is shutting down. See the previous event log messages for reasons. |
| 0x41F | DHCP 服务无法模拟 DNS 注册所需的凭据: %n%1。正在使用本地系统凭据。 |
The DHCP service was unable to impersonate the credentials necessary for DNS registrations: %n%1. The local system credentials is being used. |
| 0x420 | DHCP 服务检测到它在一个 DC 上运行，并且没有配置用于此 DHCP 服务启动的动态 DNS 注册的任何凭据。这不是推荐的安全配置。动态 DNS 注册的凭据可用命令行 \"netsh dhcp server set dnscredentials\" 或通过 DHCP 管理工具配置。 |
The DHCP service has detected that it is running on a DC and has no credentials configured for use with Dynamic DNS registrations initiated by the DHCP service. This is not a recommended security configuration. Credentials for Dynamic DNS registrations may be configured using the command line \"netsh dhcp server set dnscredentials\" or via the DHCP Administrative tool. |
| 0x421 | DHCP 服务无法将临时数据库转换成 ESE 格式: %n%1。 |
The DHCP service was unable to convert the temporary database to ESE format: %n%1. |
| 0x422 | DHCP 服务未能初始化其配置参数。发生了以下错误: %n%1 |
The DHCP service failed to initialize its configuration parameters. The following error occurred: %n%1 |
| 0x423 | DHCP 服务没看到授权目录服务器。 |
The DHCP service failed to see a directory server for authorization. |
| 0x424 | DHCP 服务不能访问审计日志的路径。 |
The DHCP service was unable to access path specified for the audit log. |
| 0x425 | DHCP 服务不能访问为数据库备份指定的路径。 |
The DHCP service was unable to access path specified for the database backups. |
| 0x426 | DHCP 服务不能访问为数据库指定的路径 |
The DHCP service was unable to access path specified for the database |
| 0x427 | 在作用域或超级作用域“%1”中没有可租赁的 IP 地址。 |
There are no IP addresses available for lease in the scope or superscope \"%1\". |
| 0x428 | 在作用域或超级作用域“%1”中没有 BOOTP 客户端可用的 IP 地址。 |
There are no IP addresses available for BOOTP clients in the scope or superscope \"%1\". |
| 0x429 | 由于删除了某个类或选项定义，有一些孤立的项目被删除。请重新检查服务器配置。 |
There were some orphaned entries deleted in the configuration due to the deletion of a class or an option definition. Please recheck the server configuration. |
| 0x42A | DHCP/BINL 服务没有在目录服务域“%2”中得到授权(服务器 IP 地址 %1) |
The DHCP/BINL service is not authorized in the directory service domain \"%2\" (Server IP Address %1) |
| 0x42B | DHCP/BINL 服务在目录服务域“%2”中得到授权(服务器 IP 地址 %1) |
The DHCP/BINL service is authorized in the directory service domain \"%2\" (Server IP Address %1) |
| 0x42C | DHCP/BINL 服务尚未确定它是否在目录域“%2”中得到授权(服务器 IP 地址 %1) |
The DHCP/BINL service has not determined if it is authorized in directory domain \"%2\" (Server IP Address %1) |
| 0x42D | Iashlpr 无法联系 NPS 服务器: %n%1，请检查 IAS 服务是否已启动。 |
Iashlpr could not contact the NPS server:%n%1, check if IAS service is started. |
| 0x42E | Iashlpr 初始化失败: %1，因此 DHCP 服务器无法与 NPS 服务器对话。可能是因为没有启动 IAS 服务。 |
Iashlpr initialization failed: %1, so DHCP server cannot talk to NPS server. It could be that IAS service is not started. |
| 0x42F | 动态 Bootp%0 |
Dynamic Bootp%0 |
| 0x430 | 更新%0 |
Renew%0 |
| 0x431 | 释放%0 |
Release%0 |
| 0x432 | 冲突%0 |
Conflict%0 |
| 0x433 | 作用域满%0 |
Scope Full%0 |
| 0x434 | 已启动%0 |
Started%0 |
| 0x435 | 已停止%0 |
Stopped%0 |
| 0x436 | 审计日志已暂停%0 |
Audit Log Paused%0 |
| 0x437 | dhcpsrv.log%0 |
dhcpsrv.log%0 |
| 0x438 | BAD_ADDRESS%0 |
BAD_ADDRESS%0 |
| 0x439 | 此地址已在使用中%0 |
This address is already in use%0 |
| 0x43A | NACK%0 |
NACK%0 |
| 0x43B | 已删除%0 |
Deleted%0 |
| 0x43C | 没有删除 DNS 记录%0 |
DNS record not deleted%0 |
| 0x43D | 过期%0 |
Expired%0 |
| 0x43E | %%d 个租约过期，%%d 个租约被删除%0 |
%%d leases expired and %%d leases deleted%0 |
| 0x43F | 开始数据库清理%0 |
Database Cleanup Begin%0 |
| 0x440 | %t%tMicrosoft DHCP 服务活动日志%n%n%n事件 ID 含义%n00%t已启动日志。%n01%t已停止日志。%n02%t由于磁盘空间不足，日志被暂停。%n10%t已将一个新的 IP 地址租赁给一个客户端。%n11%t一个客户端已续订了一个租赁。%n12%t一个客户端已释放了一个租赁。%n13%t一个 IP 地址已在网络上被占用。%n14%t不能满足一个租赁请求，因为作用域的地址池已用尽。%n15%t一个租赁已被拒绝。%n16%t一个租赁已被删除。%n17%t一个租赁已到期，并且已到期租赁的 DNS 记录未被删除。%n18%t一个租赁已到期，并且 DNS 记录已被删除。%n20%t已将一个 BOOTP 地址租赁给一个客户端。%n21%t已将一个动态 BOOTP 地址租赁给一个客户端。%n22%t无法满足一个 BOOTP 请求，因为作用域的 BOOTP 地址池已用尽。%n23%t删除了一个 BOOTP IP 地址，因为经检查了解到它不在使用中。%n24%tIP 地址清理操作已开始。%n25%tIP 地址清理统计信息。%n30%t命名 DNS 服务器的 DNS 更新请求。%n31%tDNS 更新失败。%n32%tDNS 更新成功。%n33%t由于 NAP 策略而丢弃数据包。%n34%tDNS 更新请求失败，因为超出了 DNS 更新请求队列限制。%n35%tDNS 更新请求失败。%n36%t数据包被丢弃，因为服务器具有故障转移备用角色或客户端 ID 的哈希值不匹配。%n50+%t超过 50 以上的代码用于 Rogue 服务器检测信息。%n%nQResult: 0: NoQuarantine、1:隔离、2:丢弃数据包、3:试用、6:无隔离信息试用时间:年-月-日 小时:分钟:秒:毫秒。%n%nID、日期、时间、描述、IP 地址、主机名、MAC 地址、用户名、TransactionID、QResult、Probationtime、CorrelationID、Dhcid、VendorClass(Hex)、VendorClass(ASCII)、UserClass(Hex)、UserClass(ASCII)、RelayAgentInformation、DnsRegError。 |
%t%tMicrosoft DHCP Service Activity Log%n%n%nEvent ID Meaning%n00%tThe log was started.%n01%tThe log was stopped.%n02%tThe log was temporarily paused due to low disk space.%n10%tA new IP address was leased to a client.%n11%tA lease was renewed by a client.%n12%tA lease was released by a client.%n13%tAn IP address was found to be in use on the network.%n14%tA lease request could not be satisfied because the scope's address pool was exhausted.%n15%tA lease was denied.%n16%tA lease was deleted.%n17%tA lease was expired and DNS records for an expired leases have not been deleted.%n18%tA lease was expired and DNS records were deleted.%n20%tA BOOTP address was leased to a client.%n21%tA dynamic BOOTP address was leased to a client.%n22%tA BOOTP request could not be satisfied because the scope's address pool for BOOTP was exhausted.%n23%tA BOOTP IP address was deleted after checking to see it was not in use.%n24%tIP address cleanup operation has began.%n25%tIP address cleanup statistics.%n30%tDNS update request to the named DNS server.%n31%tDNS update failed.%n32%tDNS update successful.%n33%tPacket dropped due to NAP policy.%n34%tDNS update request failed.as the DNS update request queue limit exceeded.%n35%tDNS update request failed.%n36%tPacket dropped because the server is in failover standby role or the hash of the client ID does not match.%n50+%tCodes above 50 are used for Rogue Server Detection information.%n%nQResult: 0: NoQuarantine, 1:Quarantine, 2:Drop Packet, 3:Probation,6:No Quarantine Information ProbationTime:Year-Month-Day Hour:Minute:Second:MilliSecond.%n%nID,Date,Time,Description,IP Address,Host Name,MAC Address,User Name, TransactionID, QResult,Probationtime, CorrelationID,Dhcid,VendorClass(Hex),VendorClass(ASCII),UserClass(Hex),UserClass(ASCII),RelayAgentInformation,DnsRegError. |
| 0x441 | BOOTP 范围满%0 |
BOOTP Range Full%0 |
| 0x442 | BOOTP 已删除%0 |
BOOTP deleted%0 |
| 0x443 | DhcpSrvLog-Sun.log%0 |
DhcpSrvLog-Sun.log%0 |
| 0x444 | DhcpSrvLog-Mon.log%0 |
DhcpSrvLog-Mon.log%0 |
| 0x445 | DhcpSrvLog-Tue.log%0 |
DhcpSrvLog-Tue.log%0 |
| 0x446 | DhcpSrvLog-Wed.log%0 |
DhcpSrvLog-Wed.log%0 |
| 0x447 | DhcpSrvLog-Thu.log%0 |
DhcpSrvLog-Thu.log%0 |
| 0x448 | DhcpSrvLog-Sat.log%0 |
DhcpSrvLog-Fri.log%0 |
| 0x44A | 无法连接的域%0 |
Unreachable Domain%0 |
| 0x44B | 授权成功%0 |
Authorization succeeded%0 |
| 0x44C | 服务器已升级%0 |
Server Upgraded%0 |
| 0x44D | 缓存的授权%0 |
Cached authorization%0 |
| 0x44E | 授权失败%0 |
Authorization failed%0 |
| 0x44F | 已授权(服务)%0 |
Authorized(servicing)%0 |
| 0x450 | 授权失败，服务停止%0 |
Authorization failure, stopped servicing%0 |
| 0x451 | 在我们的域中找到的服务器%0 |
Server found in our domain%0 |
| 0x452 | 无法找到域%0 |
Could not find domain%0 |
| 0x453 | 网络失败%0 |
Network failure%0 |
| 0x454 | 没有 DC 启动了 DS%0 |
No DC is DS Enabled%0 |
| 0x455 | 找到的属于 DS 域的服务器%0 |
Server found that belongs to DS domain%0 |
| 0x456 | 找到另一台服务器%0 |
Another server was found%0 |
| 0x457 | 重新启动 rogue 检测%0 |
Restarting rogue detection%0 |
| 0x458 | 没有绑定到 DHCP 服务器的 IP 地址%0 |
No static IP address bound to DHCP server%0 |
| 0x459 | Microsoft Windows 2000 选项%0 |
Microsoft Windows 2000 Options%0 |
| 0x45A | 针对 Windows 2000 及更高版本客户端的 Microsoft 供应商特定选项%0 |
Microsoft vendor-specific options for Windows 2000 and above Clients%0 |
| 0x45B | Microsoft Windows 98 选项%0 |
Microsoft Windows 98 Options%0 |
| 0x45C | Windows 98 客户端的 Microsoft 供应商特定选项%0 |
Microsoft vendor-specific options for Windows 98 Clients%0 |
| 0x45D | Microsoft 选项%0 |
Microsoft Options%0 |
| 0x45E | 适用于所有 Windows 客户端的 Microsoft 供应商特定选项%0 |
Microsoft vendor-specific options applicable to all Windows Clients%0 |
| 0x45F | Microsoft 禁用 Netbios 选项 %0 |
Microsoft Disable Netbios Option %0 |
| 0x460 | 为 Microsoft Windows 2000 客户端启用或禁用 Netbios 的选项%0 |
Option for enabling or disabling Netbios for Microsoft Windows 2000 Clients%0 |
| 0x461 | Microsoft 关机释放 DHCP 租约的选项%0 |
Microsoft Release DHCP Lease On Shutdown Option%0 |
| 0x462 | 为启用或禁用 Windows 2000 客户端在关闭时释放 DHCP 租约的选项%0 |
Option for enabling or disabling Windows 2000 Clients to release DHCP lease on shutdown%0 |
| 0x463 | Microsoft 默认路由器跃点数基%0 |
Microsoft Default Router Metric Base%0 |
| 0x464 | Microsoft Windows 2000 客户端的默认路由器跃点数基%0 |
Default Router Base Metrics for Microsoft Windows 2000 Clients%0 |
| 0x465 | 内部%0 |
Internal%0 |
| 0x466 | DHCP Users%0 |
DHCP Users%0 |
| 0x467 | 对 DHCP 服务只有查看访问权的成员%0 |
Members who have view-only access to the DHCP service%0 |
| 0x468 | DHCP Administrators%0 |
DHCP Administrators%0 |
| 0x469 | 对 DHCP 服务器有管理访问权的成员%0 |
Members who have administrative access to DHCP service%0 |
| 0x46A | 默认路由和远程访问类%0 |
Default Routing and Remote Access Class%0 |
| 0x46B | 远程访问客户端的用户类%0 |
User class for remote access clients%0 |
| 0x46C | 默认 BOOTP 类%0 |
Default BOOTP Class%0 |
| 0x46D | BOOTP 客户端的用户类%0 |
User class for BOOTP Clients%0 |
| 0x46E | 无类静态路由%0 |
Classless Static Routes%0 |
| 0x46F | 目标、掩码和路由器 IP 地址，按优先顺序排列%0 |
Destination, mask and router IP addresses in priority order%0 |
| 0x470 | DNS 更新请求%0 |
DNS Update Request%0 |
| 0x471 | DNS 更新失败%0 |
DNS Update Failed%0 |
| 0x472 | DNS 更新成功%0 |
DNS Update Successful%0 |
| 0x473 | 默认的网络访问保护级别%0 |
Default Network Access Protection Class%0 |
| 0x474 | 受限访问客户端的默认特殊用户类%0 |
Default special user class for Restricted Access clients%0 |
| 0x475 | 分配%0 |
Assign%0 |
| 0x476 | DHCP 服务器无法访问 NPS 服务器，以至于无法确定客户端的 NAP 访问状态 %0。 |
The DHCP server is unable to reach the NPS server for determining the client's NAP access state %0. |
| 0x477 | Bootp%0 |
Bootp%0 |
| 0x478 | 此计算机至少具有一个动态分配的 IP 地址。为了执行可靠的 DHCP 服务器操作，应该仅使用静态 IP 地址。 |
This computer has at least one dynamically assigned IP address. For reliable DHCP Server operation, you should use only static IP addresses. |
| 0x479 | Microsoft Windows 选项%0 |
Microsoft Windows Options%0 |
| 0x47A | 用于 Windows 客户端的 Microsoft 供应商特定的选项%0 |
Microsoft vendor-specific options for Windows Clients%0 |
| 0x47B | 已启用%0 |
Enabled%0 |
| 0x47C | 已禁用%0 |
Disabled%0 |
| 0x47D | EQ %0 |
EQ %0 |
| 0x47E | NEQ %0 |
NEQ %0 |
| 0x47F | AND%0 |
AND%0 |
| 0x480 | OR%0 |
OR%0 |
| 0x481 | 供应商类 %0 |
Vendor Class %0 |
| 0x482 | 用户类 %0 |
User Class %0 |
| 0x483 | MAC 地址 %0 |
MAC address %0 |
| 0x484 | 客户端 Id %0 |
Client Id %0 |
| 0x485 | 中继代理信息 %0 |
Relay Agent Info %0 |
| 0x486 | 中继代理信息 - 电路 Id %0 |
Relay Agent Info - Circuit Id %0 |
| 0x487 | 中继代理信息 - 远程 Id %0 |
Relay Agent Info - Remote Id %0 |
| 0x488 | 中继代理信息 - 订阅者 Id %0 |
Relay Agent Info - Subscriber Id %0 |
| 0x489 | , %0 |
, %0 |
| 0x48A | ; %0 |
; %0 |
| 0x48B | *%0 |
*%0 |
| 0x48C | 完全限定的域名 %0 |
Fully Qualified Domain Name %0 |
| 0x48D | 是单标签%0 |
Is Single Label%0 |
| 0x48E | 不是单标签%0 |
Is Not Single Label%0 |
| 0x48F | 已保留 |
Reserved |
| 0x498 | DhcpV6SrvLog-Sun.log%0 |
DhcpV6SrvLog-Sun.log%0 |
| 0x499 | DhcpV6SrvLog-Mon.log%0 |
DhcpV6SrvLog-Mon.log%0 |
| 0x49A | DhcpV6SrvLog-Tue.log%0 |
DhcpV6SrvLog-Tue.log%0 |
| 0x49B | DhcpV6SrvLog-Wed.log%0 |
DhcpV6SrvLog-Wed.log%0 |
| 0x49C | DhcpV6SrvLog-Thu.log%0 |
DhcpV6SrvLog-Thu.log%0 |
| 0x49D | DhcpV6SrvLog-Fri.log%0 |
DhcpV6SrvLog-Fri.log%0 |
| 0x49E | DhcpV6SrvLog-Sat.log%0 |
DhcpV6SrvLog-Sat.log%0 |
| 0x49F | SIP 服务器域名列表 %0 |
SIP Server Domain Name List %0 |
| 0x4A0 | 可用于客户端的 SIP 服务器域名 %0 |
Domain Name of SIP servers available to the client %0 |
| 0x4A1 | SIP 服务器 IPv6 地址列表 %0 |
SIP Servers IPv6 Address List %0 |
| 0x4A2 | 可用于客户端的 SIP 服务器的 IPv6 地址 %0 |
IPv6 addresses of SIP servers available to the client %0 |
| 0x4A3 | DNS 递归名称服务器 IPv6 地址列表 %0 |
DNS Recursive Name Server IPv6 Address List %0 |
| 0x4A4 | 可用于客户端的 DNS 递归名称服务器的 IPV6 地址 %0 |
IPv6 Addresses of DNS recursive name servers available to the client %0 |
| 0x4A5 | 域搜索列表 %0 |
Domain Search List %0 |
| 0x4A6 | 客户端使用域搜索列表按优先顺序解决带有 DNS 的主机名 %0 |
Domain search list used by clients to resolve hostnames with DNS, by preference %0 |
| 0x4A7 | NIS IPv6 地址列表 %0 |
NIS IPv6 Address List %0 |
| 0x4A8 | 可用于客户端 %0 的 NIS 服务器的 IPv6 地址 |
IPv6 Addresses of NIS servers available to the client %0 |
| 0x4A9 | NIS+ IPv6 地址列表 %0 |
NIS+ IPv6 Address List %0 |
| 0x4AA | 可用于客户端 %0 的 NIS+ 服务器的 IPv6 地址 |
IPv6 Addresses of NIS+ servers available to the client %0 |
| 0x4AB | NIS 域列表 %0 |
NIS Domain List %0 |
| 0x4AC | 可用于客户端的 NIS 服务器的域名称 %0 |
Domain names of NIS servers available to the client %0 |
| 0x4AD | NIS+ 域名称列表 %0 |
NIS+ Domain Name List %0 |
| 0x4AE | 可用于客户端的 NIS+ 服务器的域名称 %0 |
Domain names of NIS+ servers available to the client %0 |
| 0x4AF | SNTP 服务器 IPv6 地址列表 %0 |
SNTP Servers IPv6 Address List %0 |
| 0x4B0 | 可用于客户端 %0 的 SNTP 服务器的 IPv6 地址 |
IPv6 Addresses of SNTP servers available to the client %0 |
| 0x4B1 | 信息刷新时间 %0 |
Information Refresh Time %0 |
| 0x4B2 | 此选项指定了在刷新从 DHCPv6 服务器检索到的信息之前，客户端应等待的最长时间 %0 |
This option specifies an upper bound for how long a client should wait before refreshing information retrieved from DHCPv6 Server %0 |
| 0x4B3 | %t%tMicrosoft DHCPv6 服务活动日志%n%n%n事件 ID 含义%n11000%tDHCPv6 要求。%n11001%tDHCPv6 播发。%n11002%tDHCPv6 请求。%n11003%tDHCPv6 确认。%n11004%tDHCPv6 续订。%n11005%tDHCPv6 重新绑定。%n11006%tDHCPv6 拒绝。%n11007%tDHCPv6 发布。%n11008%tDHCPv6 信息请求。%n11009%tDHCPv6 作用域已满。%n11010%tDHCPv6 已启动。%n11011%tDHCPv6 已停止。%n11012%tDHCPv6 审核日志已暂停。%n11013%tDHCPv6 日志文件。%n11014%tDHCPv6 错误地址。%n11015%tDHCPv6 地址已在使用。%n11016%tDHCPv6 客户端已删除。%n11017%tDHCPv6 DNS 记录未删除。%n11018%tDHCPv6 已过期。%n11019%tDHCPv6 租约已过期且租约已被删除。%n11020%tDHCPv6 数据库清除开始。%n11021%tDHCPv6 数据库清除结束。%n11022%tDNS IPv6 更新请求。%n11023%tDNS IPv6 更新失败。%n11024%tDNS IPv6 更新成功。%n11028%tDNS IPv6 更新请求失败，因为超出了 DNS 更新请求队列限制。%n11029%tDNS IPv6 更新请求失败。%n11030%tDHCPv6 无状态客户端记录已清除。%n11031%tDHCPv6 无状态客户端记录已清除，因为此客户端记录的清除间隔已过期。%n11032%t来自 IPV6 无状态客户端的 DHCPV6 信息请求。%n%nID、日期、时间、描述、IPv6 地址、主机名、错误代码、Duid 长度、Duid 字节(十六进制)、用户名、Dhcid、子网前缀。 |
%t%tMicrosoft DHCPv6 Service Activity Log%n%n%nEvent ID Meaning%n11000%tDHCPv6 Solicit.%n11001%tDHCPv6 Advertise.%n11002%tDHCPv6 Request.%n11003%tDHCPv6 Confirm.%n11004%tDHCPv6 Renew.%n11005%tDHCPv6 Rebind.%n11006%tDHCPv6 Decline.%n11007%tDHCPv6 Release.%n11008%tDHCPv6 Information Request.%n11009%tDHCPv6 Scope Full.%n11010%tDHCPv6 Started.%n11011%tDHCPv6 Stopped.%n11012%tDHCPv6 Audit log paused.%n11013%tDHCPv6 Log File.%n11014%tDHCPv6 Bad Address.%n11015%tDHCPv6 Address is already in use.%n11016%tDHCPv6 Client deleted.%n11017%tDHCPv6 DNS record not deleted.%n11018%tDHCPv6 Expired.%n11019%tDHCPv6 Leases Expired and Leases Deleted .%n11020%tDHCPv6 Database cleanup begin.%n11021%tDHCPv6 Database cleanup end.%n11022%tDNS IPv6 Update Request.%n11023%tDNS IPv6 Update Failed.%n11024%tDNS IPv6 Update Successful.%n11028%tDNS IPv6 update request failed as the DNS update request queue limit exceeded.%n11029%tDNS IPv6 update request failed.%n11030%tDHCPv6 stateless client records purged.%n11031%tDHCPv6 stateless client record is purged as the purge interval has expired for this client record.%n11032%tDHCPV6 Information Request from IPV6 Stateless Client.%n%nID,Date,Time,Description,IPv6 Address,Host Name,Error Code, Duid Length, Duid Bytes(Hex),User Name,Dhcid,Subnet Prefix. |
| 0x4B4 | 丢弃的数据包%0 |
Packet dropped%0 |
| 0x4B5 | DHCP 标准选项%0 |
DHCP Standard Options%0 |
| 0x4B6 | 默认用户类%0 |
Default User Class%0 |
| 0x4B7 | %0 |
%0 |
| 0x4B8 | UTC 偏移(秒)%0 |
UTC offset in seconds%0 |
| 0x4B9 | 路由器%0 |
Router%0 |
| 0x4BA | 按优先顺序排列的路由器地址阵列%0 |
Array of router addresses ordered by preference%0 |
| 0x4BB | 时间服务器%0 |
Time Server%0 |
| 0x4BC | 按优先顺序排列的时间服务器地址阵列%0 |
Array of time server addresses, by preference%0 |
| 0x4BD | 名称服务器%0 |
Name Servers%0 |
| 0x4BE | 按优先顺序排列的名称服务器 [IEN 116] 阵列%0 |
Array of name servers [IEN 116], by preference%0 |
| 0x4BF | DNS 服务器%0 |
DNS Servers%0 |
| 0x4C0 | DNS 服务器的阵列，按首选项排列%0 |
Array of DNS servers, by preference%0 |
| 0x4C1 | 日志服务器%0 |
Log Servers%0 |
| 0x4C2 | 子网上的 MIT_LCS UDP 日志服务器阵列%0 |
Array of MIT_LCS UDP log servers on subnet%0 |
| 0x4C3 | Cookie 服务器%0 |
Cookie Servers%0 |
| 0x4C4 | Cookie 服务器阵列，RFC 865%0 |
Array of cookie servers, RFC 865%0 |
| 0x4C5 | LPR 服务器%0 |
LPR Servers%0 |
| 0x4C6 | 按优先顺序排列的 RFC 1179 服务器阵列%0 |
Array of RFC 1179 servers, by preference%0 |
| 0x4C7 | Impress 服务器%0 |
Impress Servers%0 |
| 0x4C8 | Imagen Impress 服务器阵列%0 |
Array of Imagen Impress Servers%0 |
| 0x4C9 | 资源位置服务器%0 |
Resource Location Servers%0 |
| 0x4CA | 按优先顺序排列的子网上的 RFC 887 ResLoc 服务器阵列%0 |
Array of RFC 887 ResLoc Servers on subnet, by preference%0 |
| 0x4CB | 主机名称%0 |
Host Name%0 |
| 0x4CC | 客户端的主机名称，RFC 1035 字符集%0 |
Host name for client, RFC 1035 character set%0 |
| 0x4CD | 引导文件大小%0 |
Boot File Size%0 |
| 0x4CE | 启动映像文件的大小，以 512 八进制块为单位%0 |
Size of boot image file in 512-octet blocks%0 |
| 0x4CF | 现场转储文件%0 |
Merit Dump File%0 |
| 0x4D0 | 故障转储文件的路径名称%0 |
Path name for crash dump file%0 |
| 0x4D1 | DNS 域名%0 |
DNS Domain Name%0 |
| 0x4D2 | 客户端解析的 DNS 域名称%0 |
DNS Domain name for client resolutions%0 |
| 0x4D3 | 交换服务器%0 |
Swap Server%0 |
| 0x4D4 | 客户端的交换服务器地址%0 |
Address of client's swap server%0 |
| 0x4D5 | 根路径%0 |
Root Path%0 |
| 0x4D6 | 客户端的根磁盘路径名称，字符集为 NVT ASCII%0 |
Path name for client's root disk, char set NVT ASCII%0 |
| 0x4D7 | 扩展路径%0 |
Extensions Path%0 |
| 0x4D8 | 用于选项扩展的 tftp 文件%0 |
tftp file for option extensions%0 |
| 0x4D9 | IP 层转发%0 |
IP Layer Forwarding%0 |
| 0x4DA | 禁用/启用此客户端上的 IP 数据包转发%0 |
Disable/enable IP packet forwarding on this client%0 |
| 0x4DB | 非本地源路由%0 |
Nonlocal Source Routing%0 |
| 0x4DC | 禁用/启用非本地数据报%0 |
Disable/enable nonlocal datagrams%0 |
| 0x4DD | 策略筛选器掩码%0 |
Policy Filter Masks%0 |
| 0x4DE | 用于筛选源路由的目标/掩码 IP 地址对%0 |
Destination/mask IP address pairs to filter source routes%0 |
| 0x4DF | 最大 DG 重组大小%0 |
Max DG Reassembly Size%0 |
| 0x4E0 | 客户端重组的数据报大小上限，最大 576%0 |
Maximum size datagram for reassembly by client; max 576%0 |
| 0x4E1 | 默认 IP 生存时间%0 |
Default IP Time-to-live%0 |
| 0x4E2 | 供客户端在传出的 DG 上使用的默认 TTL%0 |
Default TTL for client's use on outgoing DGs%0 |
| 0x4E3 | 路径 MTU 老化超时%0 |
Path MTU Aging Timeout%0 |
| 0x4E4 | 在数秒内老化路径 MTU 值将超时，RFC 1191%0 |
Timeout in seconds for aging Path MTU values; RFC 1191%0 |
| 0x4E5 | 路径 MTU 停滞表%0 |
Path MTU Plateau Table%0 |
| 0x4E6 | MTU 发现大小，按大小排序，所有 = 68%0 |
MTU discovery sizes, sorted by size, all = 68%0 |
| 0x4E7 | MTU 选项%0 |
MTU Option%0 |
| 0x4E8 | MTU 发现大小，= 68%0 |
MTU discovery size, = 68%0 |
| 0x4E9 | 所有子网均为本地%0 |
All subnets are local%0 |
| 0x4EA | 客户端假设所有子网均为本地%0 |
The client assumes that all subnets are local%0 |
| 0x4EB | 广播地址%0 |
Broadcast Address%0 |
| 0x4ED | 执行掩码发现%0 |
Perform Mask Discovery%0 |
| 0x4EE | 客户端应使用 ICMP 来发现子网掩码。%0 |
The client should use ICMP for subnet mask discovery.%0 |
| 0x4EF | 掩码提供者选项%0 |
Mask Supplier Option%0 |
| 0x4F0 | 客户端应通过 ICMP 响应子网掩码请求。%0 |
The client should respond to subnet mask requests via ICMP.%0 |
| 0x4F1 | 执行路由器发现%0 |
Perform Router Discovery%0 |
| 0x4F2 | 客户端应使用 RFC 1256 请求路由器。%0 |
The client should solicit routers using RFC 1256.%0 |
| 0x4F3 | 路由器请求地址%0 |
Router Solicitation Address%0 |
| 0x4F4 | 供路由器请求使用的地址%0 |
Address to use for router solicitation%0 |
| 0x4F5 | 静态路由选项%0 |
Static Route Option%0 |
| 0x4F6 | 按照优先级排列目标/路由器地址对%0 |
Destination/router address pairs, in priority order%0 |
| 0x4F7 | 尾端封装%0 |
Trailer Encapsulation%0 |
| 0x4F8 | 客户端应协商使用尾端(RFC 983)。%0 |
The client should negotiate use of trailers (RFC 983).%0 |
| 0x4F9 | ARP 缓存超时%0 |
ARP Cache Timeout%0 |
| 0x4FA | 以秒为单位的 ARP 缓存项超时时间%0 |
Timeout in seconds for ARP cache entries%0 |
| 0x4FB | 以太网封装%0 |
Ethernet Encapsulation%0 |
| 0x4FC | 0= 客户端应该使用 ENet 版本 V2; 1= IEEE 802.3%0 |
0=client should use ENet V2; 1= IEEE 802.3%0 |
| 0x4FD | 默认 TCP 生存时间%0 |
TCP Default Time-to-live%0 |
| 0x4FE | 发送 TCP 段时客户端使用的 TTL%0 |
TTL that client uses when sending TCP segments%0 |
| 0x4FF | “保持连接”间隔%0 |
Keepalive Interval%0 |
| 0x500 | 以秒为单位的保持连接超时时间%0 |
Keepalive timeout in seconds%0 |
| 0x501 | “保持连接”垃圾%0 |
Keepalive Garbage%0 |
| 0x502 | 发送垃圾八进制数%0 |
Send garbage octet%0 |
| 0x503 | NIS 域名%0 |
NIS Domain Name%0 |
| 0x504 | 网络信息服务域名%0 |
Name of Network Information Service domain%0 |
| 0x505 | NIS 服务器%0 |
NIS Servers%0 |
| 0x506 | 客户端子网上的 NIS 服务器地址%0 |
Addresses of NIS servers on client's subnet%0 |
| 0x507 | NTP 服务器%0 |
NTP Servers%0 |
| 0x508 | Network 时间协议服务器的地址%0 |
Addresses of Network Time Protocol servers%0 |
| 0x509 | 供应商特定信息%0 |
Vendor Specific Info%0 |
| 0x50A | 内嵌的特定于供应商的选项%0 |
Embedded vendor-specific options%0 |
| 0x50B | WINS/NBNS 服务器%0 |
WINS/NBNS Servers%0 |
| 0x50C | 按照优先级排列的 NBNS 地址%0 |
NBNS Address(es) in priority order%0 |
| 0x50D | TCP/IP NBDD 上的 NetBIOS%0 |
NetBIOS over TCP/IP NBDD%0 |
| 0x50E | 按照优先级排列的 TCP/IP NBDD 上的 NetBIOS 地址%0 |
NetBIOS over TCP/IP NBDD address(es) in priority order%0 |
| 0x50F | WINS/NBT 节点类型%0 |
WINS/NBT Node Type%0 |
| 0x510 | 0x1 = B 节点，0x2 = P 节点，0x4 = M 节点，0x8 = H 节点%0 |
0x1 = B-node, 0x2 = P-node, 0x4 = M-node, 0x8 = H-node%0 |
| 0x511 | NetBIOS 作用域 ID%0 |
NetBIOS Scope ID%0 |
| 0x512 | TCP/IP 上的 NetBIOS 作用域 ID%0 |
NetBIOS over TCP/IP Scope ID%0 |
| 0x513 | X Window 系统字体%0 |
X Window System Font%0 |
| 0x514 | X Window 的字体服务器阵列%0 |
Array of X Windows font servers%0 |
| 0x515 | X Window 系统显示%0 |
X Window System Display%0 |
| 0x516 | X Window 的显示管理服务器阵列%0 |
Array of X Windows Display Mgr servers%0 |
| 0x517 | 租约%0 |
Lease%0 |
| 0x518 | 客户端 IP 地址租约时间(以秒计)%0 |
Client IP address lease time in seconds%0 |
| 0x519 | 续订(T1)时间值%0 |
Renewal (T1) Time Value%0 |
| 0x51A | 介于地址分配到 RENEWING 状态之间的时间%0 |
Time between addr assignment to RENEWING state%0 |
| 0x51B | 重新绑定(T2)时间值%0 |
Rebinding (T2) Time Value%0 |
| 0x51C | 从地址分配到 REBINDING 状态的时间%0 |
Time from addr assignment to REBINDING state%0 |
| 0x51D | NIS+ 域名%0 |
NIS+ Domain Name%0 |
| 0x51E | 客户端的 NIS+ 域名。%0 |
The name of the client's NIS+ domain.%0 |
| 0x51F | NIS+ 服务器%0 |
NIS+ Servers%0 |
| 0x520 | 指示 NIS+ 服务器的 IP 地址列表%0 |
A list of IP addresses indicating NIS+ servers%0 |
| 0x521 | 启动服务器主机名%0 |
Boot Server Host Name%0 |
| 0x522 | TFTP 启动服务器主机名%0 |
TFTP boot server host name%0 |
| 0x523 | 启动文件名%0 |
Bootfile Name%0 |
| 0x525 | 移动 IP 主代理%0 |
Mobile IP Home Agents%0 |
| 0x526 | 按照优先级排列的移动 IP 主代理%0 |
Mobile IP home agents in priority order%0 |
| 0x527 | 简单邮件传输协议(SMTP)服务器%0 |
Simple Mail Transport Protocol (SMTP) Servers%0 |
| 0x528 | 可供客户端使用的 SMTP 服务器列表%0 |
List of SMTP servers available to the client%0 |
| 0x529 | 邮局协议(POP3)服务器%0 |
Post Office Protocol (POP3) Servers%0 |
| 0x52A | 可供客户端使用的 POP3 服务器列表%0 |
List of POP3 servers available to the client%0 |
| 0x52B | 网络新闻传输协议(NNTP)服务器%0 |
Network News Transport Protocol (NNTP) Servers%0 |
| 0x52C | 可供客户端使用的 NNTP 服务器列表%0 |
List of NNTP servers available to the client%0 |
| 0x52D | 万维网(WWW)服务器%0 |
World Wide Web (WWW) Servers%0 |
| 0x52E | 可供客户端使用的 WWW 服务器列表%0 |
List of WWW servers available to the client%0 |
| 0x52F | 指状服务器%0 |
Finger Servers%0 |
| 0x530 | 可供客户端使用的指状服务器列表%0 |
List of Finger servers available to the client%0 |
| 0x531 | Internet 中继聊天(IRC)服务器%0 |
Internet Relay Chat (IRC) Servers%0 |
| 0x532 | 可供客户端使用的 IRC 服务器列表%0 |
List of IRC servers available to the client%0 |
| 0x533 | StreetTalk 服务器%0 |
StreetTalk Servers%0 |
| 0x534 | 可供客户端使用的 StreetTalk 服务器列表%0 |
List of StreetTalk servers available to the client%0 |
| 0x535 | 子网掩码%0 |
Subnet Mask%0 |
| 0x536 | StreetTalk 目录帮助(STDA)服务器%0 |
StreetTalk Directory Assistance (STDA) Servers%0 |
| 0x537 | 可供客户端使用的 STDA 服务器列表%0 |
List of STDA servers available to the client%0 |
| 0x538 | 按网络字节顺序排列的子网掩码%0 |
Subnet mask in network byte order%0 |
| 0x539 | 时间偏差%0 |
Time Offset%0 |
| 0x53A | 延迟传输到客户端的挂起的 DHCPOFFER 消息的数量已经超过服务器的容量即 1000 个挂起的消息。DHCP 服务器将丢弃需要根据服务器配置延迟的 DHCPOFFER 消息响应的所有后续的 DHCPDISCOVER 消息。DHCP 服务器将继续处理不需要延迟的 DHCPOFFER 消息响应的 DHCPDISCOVER 消息。一旦延迟传输到客户端的挂起的 DHCPOFFE 消息的数量低于服务器容量，DHCP 服务器将继续处理所有 DHCPDISCOVER 消息。 |
The number of pending DHCPOFFER messages for delayed transmission to the client has exceeded the server's capacity of 1000 pending messages. The DHCP server will drop all subsequent DHCPDISCOVER messages for which the DHCPOFFER message response needs to be delayed as per the server configuration. The DHCP server will continue to process DHCPDISCOVER messages for which the DHCPOFFER message responses do not need to be delayed. The DHCP server will resume processing all DHCPDISCOVER messages once the number of pending DHCPOFFER messages for delayed transmission to the client is below the server's capacity. |
| 0x53B | 因延迟传输到客户端而挂起的 DHCPOFFER 消息数现在低于服务器的 1000 的容量。DHCP 服务器现在将继续处理所有的 DHCPDISCOVER 消息。 |
The number pending DHCPOFFER messages for delayed transmission to the client is now below the server's capacity of 1000. The DHCP server will now resume processing all DHCPDISCOVER messages. |
| 0x53C | DHCPv4 客户端 IP 地址 %1，FQDN %2 和 DHCID %3 的 DNS 注册已经被拒绝，因为可能有一个具有相同 FQDN 的现有客户端已经注册 DNS。 |
The DNS registration for DHCPv4 Client IP address %1 , FQDN %2 and DHCID %3 has been denied as there is probably an existing client with same FQDN already registered with DNS. |
| 0x53D | 在作用域 %2 策略 %1 的 IP 地址范围中没有可租赁的 IP 地址。 |
There are no IP addresses available for lease in IP address range(s) of the policy %1 in scope %2. |
| 0x53E | 作用域 %1 的 IP 地址超出 IP 地址范围。 |
IP address range of scope %1 is out of IP addresses. |
| 0x53F | 作用域 %1 策略 %2 的 IP 地址范围已占用的百分比为 %3，只有 %4 个 IP 地址可用。 |
Ip address range(s) for the scope %1 policy %2 is %3 percent full with only %4 IP addresses available . |
| 0x540 | DNS IP 地址 %1 是无效的 DNS 服务器地址。 |
The DNS IP Address %1 is not a valid DNS Server Address. |
| 0x541 | DNS 更新请求失败，因为超过了 DNS 更新请求队列限制%0 |
DNS update request failed as the DNS update requests queue limit exceeded%0 |
| 0x542 | DNS 更新请求失败%0 |
DNS update request failed%0 |
| 0x543 | DNS IPv6 更新请求失败，因为超过了 DNS 更新请求队列限制%0 |
DNS IPv6 update request failed as the DNS update requests queue limit exceeded%0 |
| 0x544 | DNS IPv6 更新请求失败%0 |
DNS IPv6 update request failed%0 |
| 0x545 | 已保留%0 |
Reserved%0 |
| 0x546 | 非法 IP 地址(不属于任何地址池)%0 |
Illegal IP address (not part of any address pool)%0 |
| 0x547 | 存在致命冲突: 地址正在被其他客户端使用%0 |
Fatal conflict exists: address in use by other client%0 |
| 0x548 | 缺少绑定信息%0 |
Missing binding information%0 |
| 0x549 | 连接被拒绝，不匹配的时间太多%0 |
Connection rejected, time mismatch too great%0 |
| 0x54A | 连接被拒绝，MCLT 无效%0 |
Connection rejected, invalid MCLT%0 |
| 0x54B | 连接被拒绝，原因未知%0 |
Connection rejected, unknown reason%0 |
| 0x54C | 连接被拒绝，连接重复%0 |
Connection rejected, duplicate connection%0 |
| 0x54D | 连接被拒绝，故障转移伙伴无效%0 |
Connection rejected, invalid failover partner%0 |
| 0x54E | 不支持 TLS%0 |
TLS not supported%0 |
| 0x54F | 支持 TLS，但未配置%0 |
TLS supported but not configured%0 |
| 0x550 | 需要 TLS，但伙伴不支持%0 |
TLS required but not supported by partner%0 |
| 0x551 | 不支持消息摘要%0 |
Message digest not supported%0 |
| 0x552 | 未配置消息摘要%0 |
Message digest not configured%0 |
| 0x553 | 协议版本不匹配%0 |
Protocol version mismatch%0 |
| 0x554 | 绑定信息已过期%0 |
Outdated binding information%0 |
| 0x555 | 关键绑定信息较少%0 |
Less critical binding information%0 |
| 0x556 | 在足够的时间内没有通信%0 |
No traffic within sufficient time%0 |
| 0x557 | 哈希桶分配冲突%0 |
Hash bucket assignment conflict%0 |
| 0x558 | 此服务器上未保留 IP%0 |
IP not reserved on this server%0 |
| 0x559 | 无法比较消息摘要%0 |
Message digest failed to compare%0 |
| 0x55A | 缺少消息摘要%0 |
Missing message digest%0 |
| 0x55B | 已向此服务器分配地址%0 |
Address is allocated to this server%0 |
| 0x55C | 已向伙伴服务器分配地址%0 |
Address is allocated to the partner server%0 |
| 0x55D | 拒绝原因未知%0 |
Reject Reason Unknown%0 |
| 0x55E | 数据包已被丢弃，这是由于客户端 ID 哈希不匹配，或者服务器处于待机状态。%0 |
Packet dropped because of Client ID hash mismatch or standby server.%0 |
| 0x560 | 作用域 %1 的 IP 地址范围占用百分比为 %2，只有 %3 个 IP 地址可用。 |
IP address range of scope %1 is %2 percent full with only %3 IP addresses available. |
| 0x561 | 超级作用域 %1 占到总数的 %2，而且只剩下 %3 个 IP 地址。此超级作用域具有以下作用域 %4 |
SuperScope, %1, is %2 percent full with only %3 IP addresses remaining. This superscope has the following scopes %4 |
| 0x00002710 | DHCPv6 确认已被拒绝，因为链接的地址不正确或者客户端地址 %1 的 DHCPv6 续订请求有一个生存时间为零。 |
DHCPv6 confirmation has been declined because the address was not appropriate to the link or DHCPv6 renew request has a Zero lifetime for Client Address %1. |
| 0x00002711 | 已收到没有活动租约可用的 IPv6 地址 %1 的续订、重新绑定或确认 |
Renew, rebind or confirm received for IPv6 addresses %1 for which there are no active lease available |
| 0x00002712 | DHCPv6 服务收到长度为 %2 的未知选项 %1。原始选项数据如下。 |
DHCPv6 service received the unknown option %1, with a length of %2. The raw option data is given below. |
| 0x00002713 | 在前缀为 %1 的网络的作用域中，没有 IPv6 地址可租用。 |
There are no IPv6 addresses available to lease in the scope serving the network with Prefix %1. |
| 0x00002714 | DHCPv6 客户端 %2 已拒绝地址 %1。 |
The DHCPv6 client, %2, declined the address %1. |
| 0x00002715 | 仅用了百分之 %2 的为前缀为 %1 的网络提供服务的 DHCPv6 作用域，只剩下 %3 的 IP 地址。 |
DHCPv6 Scope serving the network with prefix %1, is %2 percent full with only %3 IP addresses remaining. |
| 0x00002716 | DHCPV6 客户端 %1 已从 DHCPV6 数据库中删除。 |
A DHCPV6 client %1 has been deleted from DHCPV6 database. |
| 0x00002717 | 在队列中停留超过 30 秒的 DHCPV6 消息已被删除，因为该消息太旧，无法进行处理。 |
A DHCPV6 message that was in the queue for more than 30 seconds has been dropped because it is too old to process. |
| 0x00002718 | 无效的 DHCPV6 消息已被删除。 |
An invalid DHCPV6 message has been dropped. |
| 0x00002719 | 与该服务器无关的 DHCPV6 消息已被删除。 |
A DHCPV6 message that was not meant for this server has been dropped. |
| 0x0000271A | DHCV6 消息已被删除，因为该消息是在单播地址上接收的，而且在该服务器上已禁用单播支持。 |
DHCV6 message has been dropped because it was received on a Uni-cast address and unicast support is disabled on the server. |
| 0x0000271B | 无法附加 DHCPV6 审核日志文件，返回的错误代码为 %1。 |
DHCPV6 audit log file cannot be appended, Error Code returned %1. |
| 0x0000271C | DHCPV6 消息已被删除，因为未授权服务器处理该消息。 |
A DHCPV6 message has been dropped because the server is not authorized to process the message. |
| 0x0000271D | DHCPv6 服务未能初始化审核日志。发生以下错误: %n%1 |
The DHCPv6 service failed to initialize the audit log. The following error occurred: %n%1 |
| 0x0000271E | 无法备份 DHCPv6 审核日志文件。错误代码 %1 |
DHCPv6 audit log file could not be backed up. Error code %1 |
| 0x0000271F | DHCPv6 服务无法访问为审核日志指定的路径。 |
AThe DHCPv6 service was unable to access path specified for the audit log. |
| 0x00002720 | DHCPv6 服务未能初始化 Winsock 启动。发生以下错误: %1。 |
The DHCPv6 service failed to initialize Winsock startup. The following error occurred %1. |
| 0x00002721 | DHCPv6 服务已检测到它正在某个 DC 上运行并且没有配置用于 DHCPv6 服务所启动的动态 DNS 注册的凭据。建议不要使用此安全配置。 |
The DHCPv6 service has detected that it is running on a DC and has no credentials configured for use with Dynamic DNS registrations initiated by the DHCPv6 service. This is not a recommended security configuration. |
| 0x00002722 | DHCPv6 服务器未能接收接口列表更改的通知。在 DHCPv6 服务中将不启用某些接口。 |
The DHCPv6 Server failed to receive a notification of interface list changes. Some of the interfaces will not be enabled in the DHCPv6 service. |
| 0x00002723 | DHCPv6 服务未能初始化其配置参数。发生以下错误: %n%1。 |
The DHCPv6 service failed to initialize its configuration parameters. The following error occurred: %n%1. |
| 0x00002724 | 该计算机至少动态指定了一个 IPv6 地址。若要使 DHCPv6 服务器操作更可靠，应该只使用静态的 IPv6 地址。 |
This computer has at least one dynamically assigned IPv6 address.For reliable DHCPv6 server operation, you should use only static IPv6 addresses. |
| 0x00002725 | DHCPv6 服务未能初始化数据库。发生了以下错误: %n%1。 |
DHCPv6 service failed to initialize the database. The following error occurred: %n%1. |
| 0x00002726 | DHCPv6 服务已初始化并且已准备就绪，可以使用。 |
The DHCPv6 service has initialized and is ready to serve. |
| 0x00002727 | DHCPv6 服务器无法绑定到 UDP 端口号 %1，因为该端口正被另一应用程序使用。必须使该端口处于可用状态，DHCPv6 服务器才能开始为客户端提供服务。 |
DHCPv6 Server is unable to bind to UDP port number %1 as it is used by another application. This port must be made available to DHCPv6 Server to start servicing the clients. |
| 0x00002728 | ERROR_LAST_DHCPV6_SERVER_ERROR |
ERROR_LAST_DHCPV6_SERVER_ERROR |
| 0x00002729 | DHCPv6 客户端 IPv6 地址 %1，FQDN %2 和 DHCID %3 的 DNS 注册已经被拒绝，因为可能有一个具有相同 FQDN 的现有客户端已经注册 DNS。 |
The DNS registration for DHCPv6 Client IPv6 address %1 , FQDN %2 and DHCID %3 has been denied as there is probably an existing client with same FQDN already registered with DNS. |
| 0x00002AF8 | DHCPV6 请求%0 |
DHCPV6 Solicit%0 |
| 0x00002AF9 | DHCPV6 播发%0 |
DHCPV6 Advertise%0 |
| 0x00002AFB | DHCPV6 确认%0 |
DHCPV6 Confirm%0 |
| 0x00002AFC | DHCPV6 续订%0 |
DHCPV6 Renew%0 |
| 0x00002AFD | DHCPV6 重新绑定%0 |
DHCPV6 Rebind%0 |
| 0x00002AFE | DHCPV6 拒绝%0 |
DHCPV6 Decline%0 |
| 0x00002AFF | DHCPV6 发布%0 |
DHCPV6 Release%0 |
| 0x00002B00 | DHCPV6 信息请求%0 |
DHCPV6 Information Request%0 |
| 0x00002B01 | DHCPV6 作用域满%0 |
DHCPV6 Scope Full%0 |
| 0x00002B02 | DHCPV6 已启动%0 |
DHCPV6 Started%0 |
| 0x00002B03 | DHCPV6 已停止%0 |
DHCPV6 Stopped%0 |
| 0x00002B04 | DHCPV6 审核日志暂停%0 |
DHCPV6 Audit Log Paused%0 |
| 0x00002B05 | DHCPV6 dhcpsrv.log%0 |
DHCPV6 dhcpsrv.log%0 |
| 0x00002B06 | DHCPV6 地址错误%0 |
DHCPV6 Bad Address%0 |
| 0x00002B07 | DHCPV6 地址正在使用%0 |
DHCPV6 address is already in use%0 |
| 0x00002B08 | DHCPV6 客户端已删除%0 |
DHCPV6 client Deleted%0 |
| 0x00002B09 | DHCPV6 DNS 记录未删除%0 |
DHCPV6 DNS record not deleted%0 |
| 0x00002B0A | DHCPV6 已过期%0 |
DHCPV6 Expired%0 |
| 0x00002B0B | DHCPV6 %%I64d 租约已过期并且 %%I64d 租约已被删除%0 |
DHCPV6 %%I64d leases expired and %%I64d leases deleted%0 |
| 0x00002B0C | DHCPV6 数据库清理开始%0 |
DHCPV6 Database Cleanup Begin%0 |
| 0x00002B0D | DHCPV6 数据库清理结束%0 |
DHCPV6 Database Cleanup End%0 |
| 0x00002B0E | DNS IPv6 更新请求%0 |
DNS IPv6 Update Request%0 |
| 0x00002B0F | DNS IPv6 更新失败%0 |
DNS IPv6 Update Failed%0 |
| 0x00002B10 | DNS IPv6 更新成功%0 |
DNS IPv6 Update Successful%0 |
| 0x00002B11 | %%I64d DHCPV6 无状态客户端记录已清除%0 |
%%I64d DHCPV6 Stateless client records purged%0 |
| 0x00002B12 | DHCPv6 无状态客户端记录已清除，因为此客户端记录的清除间隔已过期%0 |
DHCPv6 stateless client record is purged as the purge interval has expired for this client record%0 |
| 0x00002B13 | 来自 IPV6 无状态客户端的 DHCPV6 信息请求%0 |
DHCPV6 Information Request from IPV6 Stateless Client%0 |
| 0x00002B15 | DHCPV6 服务在目录服务域“%2”中未得到授权(服务器 IP 地址 %1) |
The DHCPV6 service is not authorized in the directory service domain \"%2\" (Server IP Address %1) |
| 0x00002B16 | DHCPV6 服务在目录服务域“%2”中得到授权(服务器 IP 地址 %1) |
The DHCPV6 service is authorized in the directory service domain \"%2\" (Server IP Address %1) |
| 0x00002B17 | DHCPV6 服务尚未确定其是否在目录域“%2”中得到授权(服务器 IP 地址 %1) |
The DHCPV6 service has not determined if it is authorized in directory domain \"%2\" (Server IP Address %1) |
| 0x00004E20 | DHCP 服务器初始化参数不对。 |
The DHCP server initialization parameters are incorrect. |
| 0x00004E21 | DHCP 服务器无法打开 DHCP 客户端数据库。 |
The DHCP server was unable to open the DHCP client database. |
| 0x00004E22 | DHCP 服务器无法作为 RPC 服务器启动。 |
The DHCP server was unable to start as an RPC server. |
| 0x00004E23 | DHCP 服务器无法建立套接字连接。 |
The DHCP server was unable to establish a socket connection. |
| 0x00004E24 | 指定的子网已存在。 |
The specified subnet already exists. |
| 0x00004E25 | 指定的子网不存在。 |
The specified subnet does not exist. |
| 0x00004E26 | 找不到指定子网的初级主机信息。 |
The primary host information for the specified subnet was not found. |
| 0x00004E27 | 无法删除指定的 DHCP 元素，因为它已被使用。 |
The specified DHCP element cannot be removed because it has been used. |
| 0x00004E29 | 指定的选项已存在。 |
The specified option already exists. |
| 0x00004E2A | 指定的选项不存在。 |
The specified option does not exist. |
| 0x00004E2B | 没有指定的地址。 |
The specified address is not available. |
| 0x00004E2C | 指定的 IP 地址范围已满。 |
The specified IP address range is full. |
| 0x00004E2D | 在访问 DHCP 数据库时，出现了一个错误；有关这个错误请查看DHCP 服务器事件日志以获得详细信息。 |
An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error. |
| 0x00004E2E | 指定的客户端已存在数据库中。 |
The specified client already exists in the database. |
| 0x00004E2F | DHCP 服务器接收到无效的消息。 |
The DHCP server received a message that is not valid. |
| 0x00004E30 | DHCP 服务器接收到来自无效客户端的消息。 |
The DHCP server received a message from a client that is not valid. |
| 0x00004E31 | DHCP 服务器服务已暂停。 |
The DHCP server service is paused. |
| 0x00004E32 | 指定的 DHCP 客户端不是保留客户端。 |
The specified DHCP client is not a reserved client. |
| 0x00004E33 | 指定的 DHCP 客户端是保留客户端。 |
The specified DHCP client is a reserved client. |
| 0x00004E34 | 指定的 IP 地址范围太小。 |
The specified IP address range is too small. |
| 0x00004E35 | 指定的 IP 地址范围已存在。 |
The specified IP address range already exists. |
| 0x00004E36 | 指定的 IP 地址或硬件地址正被其他客户端使用。 |
The specified IP address or hardware address is being used by another client. |
| 0x00004E37 | 指定的范围无效，或与其他已存在的范围重叠。 |
The specified range either overlaps an existing range or is not valid. |
| 0x00004E38 | 指定的范围是一个现存范围的扩展。 |
The specified range is an extension of an existing range. |
| 0x00004E39 | 指定的扩展太小，请将范围以32 个地址的倍数成倍扩展。 |
The range extension specified is too small. The range must be extended by multiples of 32 addresses. |
| 0x00004E3A | 扩展范围小于指定的向后扩展。请将范围以32 个地址的整数成倍扩展。 |
The range was extended less than the specified backward extension. Extend the range by multiples of 32 addresses. |
| 0x00004E3B | DHCP 数据库需要升级到更新的格式。请查看DHCP 服务器事件日志以获得更详细信息。 |
DHCP database needs to be upgraded to a newer format. Look at the DHCP server event log for more information. |
| 0x00004E3C | bootstrap 协议文件表格式不正确。正确的格式为:,,,,... |
The format of the bootstrap protocol file table is incorrect. The correct format is: ,, ,, etc... |
| 0x00004E3D | ERROR_SERVER_UNKNOWN_BOOT_FILE_NAME |
ERROR_SERVER_UNKNOWN_BOOT_FILE_NAME |
| 0x00004E3E | 指定的超级作用域名太长。 |
The specified superscope name is too long. |
| 0x00004E40 | 此 IP 地址已在使用。 |
This IP address is already in use. |
| 0x00004E41 | DHCP 审核日志文件路径太长。 |
The DHCP audit-log file path is too long. |
| 0x00004E42 | DHCP 服务收到对有效 IP 地址的请求，此 IP 地址不在该服务器的管理之下。 |
The DHCP service received a request for a valid IP address that is not administered by this server. |
| 0x00004E43 | DHCP 服务器未能接收接口列表更改的通知。有些接口将不会为 DHCP 服务而启用。 |
The DHCP Server failed to receive a notification of interface list changes. Some of the interfaces will not be enabled in the DHCP service. |
| 0x00004E44 | 需要将 DHCP 数据库升级到新的 Jet 格式。请看DHCP 服务事件日志以获得更详细信息。 |
The DHCP database needs to be upgraded to the current Jet format. Look at the DHCP service event log for more information. |
| 0x00004E45 | 由于无法确定是否已被授权运行，可能是由于网络问 题或资源不足，DHCP 服务器没有服务于网络上的 任何客户端。 |
The DHCP Server is not servicing any clients on the network because it could not determine if it is authorized to run. This might be due to network problems or insufficient resources. |
| 0x00004E46 | DHCP 服务正在关机，因为另一个 IP 地址为 %1 的 DHCP 服务器正在网络上运行。 |
The DHCP service is shutting down because another DHCP server with the IP address %1 is active on the network. |
| 0x00004E47 | 因为已经确定未被授权运行，DHCP 服务没有服务 于网络上的任何客户端。 |
The DHCP service is not servicing any clients on the network because it has determined that it is not authorized to run. |
| 0x00004E48 | DHCP 服务无法跟域 %1 的目录服务联系。它会继续试图跟目录服务联系。这段期间内，将不能为网络上的客户端提供服务。 |
The DHCP service is unable to contact the directory service for domain %1. The DHCP service will continue to attempt to contact the directory service. During this time, no clients on the network will be serviced. |
| 0x00004E49 | 由于其授权信息与另一个 DHCP 服务相冲突，DHCP 服务器没有服务于网络上的任何客户端。另一个服务器的 IP 地址是 %1，活动在域 %2 上。 |
The DHCP service is not servicing any clients on the network because its authorization information conflicts with another DHCP server whose IP address is %1 and is active on domain %2. |
| 0x00004E4A | DHCP 服务忽略来自另一个 DHCP 服务的请求，因为它在不同的目录服务企业(客户端的目录服务企业根 = %1) |
The DHCP service is ignoring a request from another DHCP service because it is on a different directory service enterprise (Directory Service Enterprise root = %1) |
| 0x00004E4B | DHCP 服务在网络上检测到目录服务环境。如果网络上有目录服务，DHCP 服务只能在作为目录服务的一部分的服务器上运行。因为该服务器属于一个工作组，DHCP 服务正在终止。 |
The DHCP service has detected a directory service environment on the network. If there is directory service on the network, DHCP service can only run on a server which is part of the directory service. Since this server belongs to a workgroup, the DHCP service is terminating. |
| 0x00004E4C | 正使用的类名未知或不正确。 |
The class name being used is unknown or incorrect. |
| 0x00004E4D | 类名称或类信息已在使用中。 |
The class name is already in use or the class information is already in use. |
| 0x00004E4E | 指定的作用域名太长。名称限制在 256 个字符之内。 |
The specified scope name is too long. The name is limited to a maximum of 256 characters. |
| 0x00004E4F | 服务器上已配置有默认作用域。 |
There is already a default scope configured on the server. |
| 0x00004E50 | 不能启用或关闭动态 BOOTP 属性。 |
The Dynamic BOOTP attribute cannot be turned on or off. |
| 0x00004E51 | 当 DHCP 和 BOOTP 客户端同时在作用域中存在，不允许将一个作用域转换为仅是 DHCP 作用域或仅是 BOOTP 作用域。根据创建的作用域的类型，手动从作用域中删除 DHCP 或 BOOTP 客户端。 |
Conversion of a scope to a DHCP Only scope or to a BOOTP Only scope is not allowed when DHCP and BOOTP clients both exist in the scope. Manually delete either the DHCP or the BOOTP clients from the scope, as appropriate for the type of scope being created. |
| 0x00004E52 | 网络已经更改。在检查网络更改后重试这个操作。网络更改可能由新的、不再有效的或由不在生效的 IP 地址的接口引起的。 |
The network has changed. Retry this operation after checking for the network changes. Network changes may be caused by interfaces that are new or no longer valid, or by IP addresses that are new or no longer valid. |
| 0x00004E53 | 不能更改到内部 IP 地址的绑定。 |
The bindings to internal IP addresses cannot be modified. |
| 0x00004E54 | 作用域参数不正确。不是作用域已存在就是其子网地址和掩码与现存作用域子网地址和掩码不一致。 |
The scope parameters are incorrect. Either the scope already exists or its subnet address and mask is inconsistent with the subnet address and mask of an existing scope. |
| 0x00004E55 | 多播作用域参数无效。作用域可能已存在或其属性域其他存在的作用域属性不一致。 |
The multicast scope parameters are incorrect. Either the scope already exists or its properties are inconsistent with the properties of another existing scope. |
| 0x00004E56 | 多播作用于范围必须至少为 256 IP 地址。 |
The multicast scope range must have atleast 256 IP addresses. |
| 0x00004E57 | 免除参数不正确。免除已存在。 |
The exemption parameters are incorrect. The exemption already exists. |
| 0x00004E58 | 免除参数不正确。指定的免除不存在。 |
The exemption parameters are incorrect. The specified exemption does not exist. |
| 0x00004E59 | 参数不正确。可接受的值介于 600 与 4294967295 之间。 |
Incorrect Parameter. Acceptable values are between 600 and 4294967295. |
| 0x00004E5A | %1 %3 |
%1 %3 |
| 0x00004E64 | Scavenger 已启动。 |
Scavenger started. |
| 0x00004E65 | Scavenger 已结束。 |
Scavenger ended. |
| 0x00004E66 | DHCP 服务无法访问 Windows Active Directory。 |
The DHCP service could not contact Active Directory. |
| 0x00004E67 | 在 Active Directory 里找不到 DHCP 服务根对象。 |
The DHCP service root could not be found in the Active Directory. |
| 0x00004E68 | 当访问 Active Directory 时出现了一个异常错误。 |
An unexpected error occurred while accessing the Active Directory. |
| 0x00004E69 | 错误太多，无法继续。 |
There were too many errors to proceed. |
| 0x00004E6A | 找不到 DHCP 服务。 |
A DHCP service could not be found. |
| 0x00004E6B | 指定的选项已在目录服务中。 |
The specified options are already present in the directory service. |
| 0x00004E6C | 指定的选项不在目录服务中。 |
The specified options are not present in the directory service. |
| 0x00004E6D | 指定的类已在目录服务中。 |
The specified classes already exist in the directory service. |
| 0x00004E6E | 指定的类不在目录服务中。 |
The specified classes do not exist in the directory service. |
| 0x00004E6F | 指定的服务器已在目录服务中。 |
The specified servers are already present in the directory service. |
| 0x00004E70 | 指定的服务器不在目录服务中。 |
The specified servers are not present in the directory service. |
| 0x00004E71 | 指定的服务器地址不属于带有识别服务器名称。 |
The specified server address does not belong to the identified server name. |
| 0x00004E72 | 指定的子网已在目录服务中。 |
The specified subnets already exist in the directory service. |
| 0x00004E73 | 指定的子网属于不同的超级作用域。 |
The specified subnet belongs to a different superscope. |
| 0x00004E74 | 指定的子网不在目录服务中。 |
The specified subnet is not present in the directory service. |
| 0x00004E75 | 指定的保留区不在目录服务中。 |
The specified reservation is not present in the directory service. |
| 0x00004E76 | 指定的保留区与目录服务中的一个现存保留区有冲突。 |
The reservation specified conflicts with an existing reservation in the directory service. |
| 0x00004E77 | 指定的 IP 范围与目录服务中的一些现存 IP 范围有冲突。 |
The specified IP range conflicts with some existing IP range in the directory service. |
| 0x00004E78 | 指定的 IP 范围不在目录服务中。 |
The specified IP range is not present in the directory service. |
| 0x00004E79 | 无法删除此类。 |
This class cannot be deleted. |
| 0x00004E7A | DHCP 服务器无法绑定到 UDP 端口号 %1，因为该端口正被另一应用程序使用。必须使该端口处于可用状态，DHCP 服务器才能开始为客户端提供服务。 |
DHCP Server is unable to bind to UDP port number %1 as it is used by another application. This port must be made available to DHCP Server to start servicing the clients. |
| 0x00004E7B | 给定的子网前缀无效。它表示一个非单播或链接本地地址范围。 |
The given subnet prefix is invalid. It represents either a non-unicast or link local address range. |
| 0x00004E7C | 给定的延迟值无效。有效值从 0 到 1000。 |
The given delay value is invalid. The valid value is from 0 to 1000. |
| 0x00004E7D | 地址或地址模式已包含在某个列表中。 |
Address or Address pattern is already contained in one of the list. |
| 0x00004E7E | 要添加到拒绝列表中的地址或要从允许列表中删除的地址具有关联的保留。 |
Address to be added to Deny list or to be deleted from allow list, has an associated reservation. |
| 0x00004E7F | 地址或地址模式不包含在任何列表中。 |
Address or Address pattern is not contained in either list. |
| 0x00004E82 | 没有为任何 DHCP 客户端提供服务，因为允许列表为空且已将服务器配置为向允许列表中存在相应硬件地址的客户端提供 DHCP 服务。 |
No DHCP clients are being served, as the Allow list is empty and the server was configured to provide DHCP services, to clients whose hardware addresses are present in the Allow List. |
| 0x00004E85 | 此硬件类型已经免除。 |
This Hardware Type is already exempt. |
| 0x00004E86 | 你在尝试删除未定义的硬件类型。若要定义/添加硬件类型，请使用 \"add filterexemption\"。 |
You are trying to delete an undefined Hardware Type. To define/add a Hardware Type, use 'add filterexemption'. |
| 0x00004E87 | 主机和已添加的 DHCP 服务器上的同一选项发生类型冲突。 |
Conflict in types for the same option on Host and Added DHCP Servers. |
| 0x00004E88 | 指定的父级表达式不存在。 |
The parent expression specified does not exist. |
| 0x00004E89 | DHCP 服务器策略已存在 |
The DHCP server policy already exists |
| 0x00004E8A | 给定作用域中已存在指定的 DHCP 服务器策略范围。 |
The DHCP server policy range specified already exists in the given scope. |
| 0x00004E8B | 指定的 DHCP 服务器策略范围无效或者与给定子网不匹配。 |
The DHCP server policy range specified is invalid or does not match the given subnet. |
| 0x00004E8C | 只能将 DHCP 服务器策略范围添加到作用域级别策略。 |
DHCP server policy ranges can only be added to scope level policies. |
| 0x00004E8D | DHCP 服务器策略包含无效的表达式。 |
The DHCP server policy contains an invalid expression. |
| 0x00004E8E | 为 DHCP 服务器策略指定的处理顺序无效。 |
The processing order specified for the DHCP server policy is invalid. |
| 0x00004E8F | 找不到 DHCP 服务器策略。 |
The DHCP server policy was not found. |
| 0x00004E90 | 存在为此作用域中的策略配置的 IP 地址范围。对此策略 IP 地址范围进行适当修改之后，才能对此作用域 IP 地址范围执行该操作。执行该操作之前，请更改此策略的 IP 地址范围。 |
There is an IP address range configured for a policy in this scope. This operation on the scope IP address range cannot be performed till the policy IP address range is suitably modified. Please change the IP address range of the policy before performing this operation. |
| 0x00004E91 | DHCP 作用域已位于故障转移关系中。 |
The DHCP scope is already in a failover relationship. |
| 0x00004E92 | DHCP 故障转移关系已存在。 |
The DHCP failover relationship already exists. |
| 0x00004E93 | DHCP 故障转移关系不存在。 |
The DHCP failover relationship does not exist. |
| 0x00004E94 | DHCP 作用域不是故障转移关系的一部分 |
The DHCP scope is not part of failover relationship |
| 0x00004E95 | DHCP 故障转移关系为次要关系。 |
The DHCP failover relationship is a secondary. |
| 0x00004E96 | 不支持 DHCP 故障转移 |
The DHCP failover is not supported |
| 0x00004E97 | 同步故障转移关系中的 DHCP 服务器时间不同步。 |
The DHCP servers in the failover relationship has time out of synchronization. |
| 0x00004E98 | DHCP 故障转移关系状态不是“正常”。 |
The DHCP failover relationship state is not NORMAL. |
| 0x00004E99 | 此用户对 DHCP 服务器没有管理权限 |
The user does not have administrative permissions for the DHCP server |
| 0x00004E9A | 指定的 DHCP 服务器无法访问。请提供一个可以访问的 DHCP 服务器。 |
The specified DHCP server is not reachable. Please provide a DHCP server that is reachable. |
| 0x00004E9B | DHCP 服务器服务未在指定的服务器上运行。请确保 DHCP 服务器服务在指定计算机上运行 |
The DHCP Server Service is not running on the specified server. Please ensure that the DHCP Server service is running on the specified computer |
| 0x00004E9C | 无法解析 DNS 名称 |
Unable to resolve DNS name |
| 0x00004E9D | 指定的 DHCP 故障转移关系名称过长。名称限制为最多 126 个字符 |
The specified DHCP failover relationship name is too long. The name is limited to a maximum of 126 characters |
| 0x00004E9E | 查找免费 IP 地址时，指定的 DHCP 服务器已达到所选范围的结尾 |
The specified DHCP Server has reached the end of the selected range while finding the free IP address |
| 0x00004E9F | 向故障转移关系添加的作用域中的租用同步失败。 |
The synchronization of leases in the scopes being added to the failover relationship failed. |
| 0x00004EA0 | 无法在 DHCP 服务器上创建关系，因为已超过允许的最大关系数量。 |
The relationship cannot be created on the DHCP server as the maximum number of allowed relationship has exceeded. |
| 0x00004EA1 | 如果故障转移关系中的某一服务器为 Windows Server 2012，则无法将已为故障转移配置的作用域更改为 BOOTP 或 BOTH 类型。 |
A Scope configured for failover cannot be changed to type BOOTP or BOTH if one of the servers in the failover relationship is Windows Server 2012. |
| 0x00004EA2 | 要添加到故障转移关系的作用域数量超过一次可以添加到故障转移关系的最大作用域数量。 |
Number of scopes being added to the failover relationship exceeds the max number of scopes which can be added to a failover relationship at one time. |
| 0x00004EA3 | 无法将支持 BOOTP 客户端的作用域添加到故障转移关系中。 |
A scope supporting BOOTP clients cannot be added to a failover relationship. |
| 0x00004EA4 | 无法删除属于故障转移关系的作用域的 IP 地址范围。删除该范围之前，需要将该作用域从故障转移关系中移除。 |
An IP address range of a scope which is part of a failover relationship cannot be deleted. The scope will need to be removed from the failover relationship before deleting the range. |
| 0x00004EA5 | 服务器正在与其故障转移伙伴服务器重新集成。在重新集成期间，不允许对故障转移关系添加或删除作用域。请过一段时间再尝试此操作。 |
The server is reintegrating with it's failover partner server. During reintegration, addition or deletion of scopes to the failover relationship is not permitted. Please try this operation after sometime. |
| 0x00004EA6 | 如果故障转移关系中的服务器之一正运行 Windows Server 2012，则为故障转移配置的作用域具有不受支持的设置。 |
A scope configured for failover has settings that are not supported if one of the servers in the failover relationship is running Windows Server 2012. |
| 0x00004EA7 | 无法为 DHCP 服务器策略定义 IP 地址范围，因为它具有基于完全限定的域名的条件。 |
IP Address range cannot be defined for the DHCP server policy because it has fully qualified domain name based conditions. |
| 0x00004EA8 | 无法为 DHCP 服务器策略定义选项值，因为它具有基于完全限定的域名的条件。 |
Option values cannot be defined for the DHCP server policy because it has fully qualified domain name based conditions. |
| 0x00004EA9 | 不能在策略中将基于完全限定域名的条件与已配置的选项或 IP 地址范围一起使用。 |
Fully qualified domain name based conditions cannot be used in a policy with configured options or IP address ranges. |
| 0x00004EAA | 服务器不支持网络访问保护。 |
Network Access Protection is not supported by the server. |
| 0x00004EAB | ERROR_LAST_DHCP_SERVER_ERROR |
ERROR_LAST_DHCP_SERVER_ERROR |
| 0x00004EC1 | 为故障转移关系 %1 触发了地址分配。 |
Address allocation triggered for the failover relationship %1. |
| 0x00004EC2 | Scavenger 已开始清除无状态条目。 |
Scavenger started purging stateless entries. |
| 0x00004EC3 | Scavenger 已完成清除无状态条目。 |
Scavenger finished purging stateless entries. |
| 0x00004EC4 | Scavenger 中删除的租用总数为 %1 |
The total leases deleted in scavenger are %1 |
| 0x00004EC5 | 在 DHCP 服务器数据库中找不到属于故障转移关系 %2 的作用域 %1。请还原 DHCP 服务器数据库。 |
Scope %1 which was part of failover relationship %2 was not found in DHCP server database. Please restore the DHCP server database. |
| 0x10000038 | 经典 |
Classic |
| 0x30000065 | CreateFailover |
CreateFailover |
| 0x30000066 | DeleteFailover |
DeleteFailover |
| 0x30000067 | AddFailoverScope |
AddFailoverScope |
| 0x30000068 | RemoveFailoverScope |
RemoveFailoverScope |
| 0x30000069 | ChangeFailoverConfig |
ChangeFailoverConfig |
| 0x3000006A | FailoverStateChange |
FailoverStateChange |
| 0x3000006B | TimeOutOfSync |
TimeOutOfSync |
| 0x3000006C | CommUp |
CommUp |
| 0x3000006D | CommDown |
CommDown |
| 0x3000006E | BINDING-UPDATE |
BINDING-UPDATE |
| 0x3000006F | BINDING-ACK |
BINDING-ACK |
| 0x30000070 | CONNECT |
CONNECT |
| 0x30000071 | CONNECT-ACK |
CONNECT-ACK |
| 0x30000072 | UPDATE-REQUEST-ALL |
UPDATE-REQUEST-ALL |
| 0x30000073 | UPDATE-REQUEST |
UPDATE-REQUEST |
| 0x30000074 | UPDATE-DONE |
UPDATE-DONE |
| 0x30000075 | STATE |
STATE |
| 0x30000076 | CONTACT |
CONTACT |
| 0x30000077 | MessageAuthentication |
MessageAuthentication |
| 0x30000078 | InitializeFailover |
InitializeFailover |
| 0x30000079 | FailoverIPPoolTakeover |
FailoverIPPoolTakeover |
| 0x50000002 | 错误 |
Error |
| 0x50000003 | 警告 |
Warning |
| 0x50000004 | 信息 |
Information |
| 0x7000007A | DHCP 故障转移 |
DHCP Failover |
| 0x7000007B | 策略 |
Policy |
| 0x7000007C | 名称注册。 |
Name Registration. |
| 0x90000001 | Microsoft-Windows-DHCP Server Events/Operational |
Microsoft-Windows-DHCP Server Events/Operational |
| 0x90000002 | Microsoft-Windows-DHCP Server Events/FilterNotifications |
Microsoft-Windows-DHCP Server Events/FilterNotifications |
| 0x90000003 | Microsoft-Windows-DHCP Server Events/Admin |
Microsoft-Windows-DHCP Server Events/Admin |
| 0x90000004 | Microsoft-Windows-DHCP Server Events/AuditLogs |
Microsoft-Windows-DHCP Server Events/AuditLogs |
| 0x90000005 | Microsoft-Windows-DHCP Server Events/DebugLogs |
Microsoft-Windows-DHCP Server Events/DebugLogs |
| 0x90000006 | 系统 |
System |
| 0xB0000046 | IPv4 的作用域: %1 由 %2 配置。 |
Scope: %1 for IPv4 is Configured by %2. |
| 0xB0000047 | IPv4 的作用域: %1 由 %2 修改。 |
Scope: %1 for IPv4 is Modified by %2. |
| 0xB0000048 | IPv4 的作用域: %1 由 %2 删除。 |
Scope: %1 for IPv4 is Deleted by %2. |
| 0xB0000049 | IPv4 的作用域: %1 由 %2 激活。 |
Scope: %1 for IPv4 is Activated by %2. |
| 0xB000004A | IPv4 的作用域: %1 由 %2 停用。 |
Scope: %1 for IPv4 is DeActivated by %2. |
| 0xB000004B | 由 %3 更新了 IPv4 的作用域 %1 的租约持续时间 %2 秒。以前配置的租约持续时间为 %4 秒。 |
Scope: %1 for IPv4 is Updated with Lease Duration: %2 seconds by %3. The previous configured Lease Duration was: %4 seconds. |
| 0xB000004C | %3 更新了 IPv4 的作用域 %1 的选项设置 %2 |
Scope: %1 for IPv4 is Updated with Option Settings: %2 by %3 |
| 0xB000004D | IPv4 的作用域: %1 由 %2 启用了 DNS 动态更新。 |
Scope: %1 for IPv4 is Enabled for DNS Dynamic updates by %2. |
| 0xB000004E | IPv4 的作用域: %1 由 %2 禁用了 DNS 动态更新。 |
Scope: %1 for IPv4 is Disabled for DNS Dynamic updates by %2. |
| 0xB000004F | %2 更新了 IPv4 的作用域 %1 的 DNS 设置: 根据 DHCP 客户端的请求动态更新 DNS A 和 PTR 记录。 |
Scope: %1 for IPv4 is Updated with DNS Settings by %2: to dynamically update DNS A and PTR records on request by the DHCP Clients . |
| 0xB0000050 | IPv4 的作用域: %1 由 %2 更新为 DNS 设置: 始终更新 DNS A 和 PTR 记录。 |
Scope: %1 for IPv4 is Updated with DNS Settings by %2: to always dynamically update DNS A and PTR records. |
| 0xB0000051 | IPv4 的作用域: %1 由 %2 启用了 DNS 设置: 删除租约时丢弃 DNS A 和 PTR 记录。 |
Scope: %1 for IPv4 is Enabled for DNS Settings by %2: to discard DNS A and PTR records when lease is deleted. |
| 0xB0000052 | IPv4 的作用域: %1 由 %2 禁用了 DNS 设置: 删除租约时丢弃 DNS A 和 PTR 记录。 |
Scope: %1 for IPv4 is Disabled for DNS Settings by %2: to discard DNS A and PTR records when lease is deleted. |
| 0xB0000053 | IPv4 的作用域: %1 由 %2 启用了 DNS 设置: 对未请求更新的 DHCP 客户端动态更新 DNS A 和 PTR 记录。 |
Scope: %1 for IPv4 is Enabled for DNS Settings by %2: to dynamically update DNS A and PTR records for DHCP Clients that do not request updates. |
| 0xB0000054 | IPv4 的作用域: %1 由 %2 禁用了 DNS 设置: 对未请求更新的 DHCP 客户端动态更新 DNS A 和 PTR 记录。 |
Scope: %1 for IPv4 is Disabled for DNS Settings by %2: to dynamically update DNS A and PTR records for DHCP Clients that do not request updates. |
| 0xB0000055 | 已为作用域 %1 禁用基于策略的分配。 |
Policy based assignment has been disabled for scope %1. |
| 0xB0000056 | 已为作用域 %1 启用基于策略的分配。 |
Policy based assignment has been enabled for scope %1. |
| 0xB0000057 | %2 在 IPv4 的作用域 %1 上启用了名称保护设置。 |
Name Protection setting is Enabled on Scope: %1 for IPv4 by %2. |
| 0xB0000058 | %2 在 IPv4 的作用域 %1 上禁用了名称保护设置。 |
Name Protection setting is Disabled on Scope: %1 for IPv4 by %2. |
| 0xB0000059 | IPv4 的作用域: %1 由 %3 更新为支持类型: %2。以前配置的状态为: %4。 |
Scope: %1 for IPv4 is Updated with support type: %2 by %3. The previous configured state was: %4. |
| 0xB000005A | %2 在 IPv4 的作用域: %1 上启用了 NAP 强制。 |
NAP Enforcement is Enabled on Scope: %1 for IPv4 by %2. |
| 0xB000005B | %2 在 IPv4 的作用域: %1 上禁用了 NAP 强制。 |
NAP Enforcement is Disabled on Scope: %1 for IPv4 by %2. |
| 0xB000005C | %3 使用以下 NAP 配置文件: %2 在 IPv4 的作用域: %1 上配置了 NAP 配置文件。 |
NAP Profile is configured on Scope: %1 for IPv4 with the following NAP Profile: %2 by %3. |
| 0xB000005D | %3 使用以下 NAP 配置文件: %2 在 IPv4 的作用域: %1 上更新了 NAP 配置文件。以前配置的 NAP 配置文件为: %4。 |
NAP Profile is Updated on Scope: %1 for IPv4 with the following NAP Profile: %2 by %3. The previous configured NAP Profile was: %4. |
| 0xB000005E | %3 在作用域: %2 上删除了以下 NAP 配置文件: %1。 |
The following NAP Profile: %1 is deleted on Scope: %2 by %3. |
| 0xB000005F | 多播 IPv4 的作用域: %1 由 %2 配置。 |
Scope: %1 for Multicast IPv4 is Configured by %2. |
| 0xB0000060 | 多播 IPv4 的作用域: %1 由 %2 删除。 |
Scope: %1 for Multicast IPv4 is Deleted by %2. |
| 0xB0000061 | %3 将 IPv4 的作用域 %1 添加到了超级作用域 %2 中。 |
Scope: %1 for IPv4 is Added in Superscope: %2 by %3. |
| 0xB0000062 | IPv4 的超级作用域: %1 由 %2 配置。 |
SuperScope: %1 for IPv4 is Configured by %2. |
| 0xB0000063 | IPv4 的超级作用域: %1 由 %2 删除。 |
SuperScope: %1 for IPv4 is Deleted by %2. |
| 0xB0000064 | %3 激活了 IPv4 的超级作用域 %2 内的作用域 %1。 |
Scope: %1 within SuperScope: %2 for IPv4 is Activated by %3. |
| 0xB0000065 | %3 停用了 IPv4 的超级作用域 %2 中的作用域: %1。 |
Scope: %1 within SuperScope: %2 for IPv4 is DeActivated by %3. |
| 0xB0000066 | IPv4 的作用域: %1 在超级作用域: %2 中被 %3 删除。不过，该作用域存在于超级作用域外部。 |
Scope: %1 for IPv4 is Removed in Superscope: %2 by %3. However, the Scope exists outside the Superscope. |
| 0xB0000067 | IPv4 的作用域: %1 在超级作用域: %2 中被删除，同时被 %3 永久删除。 |
Scope: %1 for IPv4 is Deleted in Superscope: %2 as well as Deleted permanently by %3. |
| 0xB0000068 | %4 在 IPv4 的作用域 %2 上更新了辅助服务器发送的 OFFER 消息的延迟时间 %1 毫秒。以前配置的延迟时间为: %3 毫秒。 |
Delay Time: %1 milliseconds for the OFFER message sent by Secondary Servers is Updated on Scope: %2 for IPv4 by %4. The previous configured Delay Time was: %3 milliseconds. |
| 0xB0000069 | IPv4 的服务器级别选项 %1 已由 %2 更新。 |
Server level option %1 for IPv4 has been updated by %2. |
| 0xB000006A | %3 在作用域 %2 下配置了 IPv4 的保留 %1。 |
Reservation: %1 for IPv4 is Configured under Scope %2 by %3. |
| 0xB000006B | %3 在作用域 %2 下删除了 IPv4 的保留: %1。 |
Reservation: %1 for IPv4 is Deleted under Scope %2 by %3. |
| 0xB000006C | %3 在作用域 %2 下启用了 IPv4 保留 %1 的 DNS 动态更新。 |
Reservation: %1 for IPv4 under Scope: %2 is Enabled for DNS Dynamic updates by %3. |
| 0xB000006D | %3 在作用域 %2 下禁用了 IPv4 保留 %1 的 DNS 动态更新。 |
Reservation: %1 for IPv4 under Scope: %2 is Disabled for DNS Dynamic updates by %3. |
| 0xB000006E | %3 更新了作用域 %2 下 IPv4 保留 %1 的 DNS 设置: 根据 DHCP 客户端的请求动态更新 DNS A 和 PTR 记录。 |
Reservation: %1 for IPv4 under Scope: %2 is Updated with DNS Settings by %3: to dynamically update DNS A and PTR records on request by the DHCP Clients. |
| 0xB000006F | %3 更新了作用域 %2 下 IPv4 保留 %1 的 DNS 设置: 始终动态更新 DNS A 和 PTR 记录。 |
Reservation: %1 for IPv4 under Scope: %2 is Updated with DNS Settings by %3: to always dynamically update DNS A and PTR records. |
| 0xB0000070 | %3 在作用域 %2 下启用了 IPv4 的保留 %1 的 DNS 设置: 删除租约时丢弃 DNS A 和 PTR 记录。 |
Reservation: %1 for IPv4 under Scope: %2 is Enabled for DNS Settings by %3: to discard DNS A and PTR records when lease is deleted. |
| 0xB0000071 | %3 在作用域 %2 下禁用了 IPv4 的保留 %1 的 DNS 设置: 删除租约时丢弃 DNS A 和 PTR 记录。 |
Reservation: %1 for IPv4 under Scope: %2 is Disabled for DNS Settings by %3: to discard DNS A and PTR records when lease is deleted. |
| 0xB0000072 | %3 启用了作用域 %2 下 IPv4 保留 %1 的 DNS 设置: 对未请求更新的 DHCP 客户端动态更新 DNS A 和 PTR 记录。 |
Reservation: %1 for IPv4 under Scope: %2 is Enabled for DNS Settings by %3: to dynamically update DNS A and PTR records for DHCP Clients that do not request updates. |
| 0xB0000073 | %3 禁用了作用域 %2 下 IPv4 保留 %1 的 DNS 设置: 对未请求更新的 DHCP 客户端动态更新 DNS A 和 PTR 记录。 |
Reservation: %1 for IPv4 under Scope: %2 is Disabled for DNS Settings by %3: to dynamically update DNS A and PTR records for DHCP Clients that do not request updates. |
| 0xB0000074 | %4 在作用域 %2 下更新了 IPv4 的保留 %1 的选项设置 %3。 |
Reservation: %1 for IPv4 under Scope: %2 is Updated with Option Setting: %3 by %4. |
| 0xB0000075 | 已在服务器级别禁用基于策略的分配。 |
Policy based assignment has been disabled at server level. |
| 0xB0000076 | 已在服务器级别启用基于策略的分配。 |
Policy based assignment has been enabled at server level. |
| 0xB0000077 | %3 在作用域 %2 下的 IPv4 地址池中添加了排除 IP 地址范围 %1。 |
Added exclusion IP Address range %1 in the Address Pool for IPv4 under Scope: %2 by %3. |
| 0xB0000078 | %3 在作用域 %2 下的 IPv4 地址池中删除了排除 IP 地址范围 %1。 |
Deleted exclusion IP Address range %1 in the Address Pool for IPv4 under Scope: %2 by %3. |
| 0xB0000079 | %1 在 IPv4 的允许列表中启用了基于链路层的筛选 |
Link Layer based filtering is Enabled in the Allow List of the IPv4 by %1 |
| 0xB000007A | %1 在 IPv4 的允许列表中禁用了基于链路层的筛选 |
Link Layer based filtering is Disabled in the Allow List of the IPv4 by %1 |
| 0xB000007B | %2 将物理地址为 %1、硬件类型为 %3 的筛选器添加到了 IPv4 的允许列表中。 |
Filter for physical address: %1, hardware type: %3 added to the IPv4 Allow List by %2. |
| 0xB000007C | %2 从 IPv4 的允许列表中删除了物理地址为: %1、硬件类型为: %3 的筛选器。 |
Filter for physical address: %1, hardware type: %3 removed from the IPv4 Allow List by %2. |
| 0xB000007D | %1 在 IPv4 的拒绝列表中启用了基于链路层的筛选 |
Link Layer based filtering is Enabled in the Deny List of the IPv4 by %1 |
| 0xB000007E | %1 在 IPv4 的拒绝列表中禁用了基于链路层的筛选 |
Link Layer based filtering is Disabled in the Deny List of the IPv4 by %1 |
| 0xB000007F | %2 在 IPv4 的拒绝列表中添加了物理地址为: %1、硬件类型为: %3 的筛选器。 |
Filter for physical address: %1, hardware type: %3 added to the IPv4 Deny List by %2. |
| 0xB0000080 | %2 在 IPv4 的拒绝列表中为物理地址 %1、硬件类型 %3 删除了筛选器。 |
Filter for physical address: %1, hardware type: %3 removed from the IPv4 Deny List by %2. |
| 0xB0000081 | IPv6 的作用域: %1 由 %2 配置。 |
Scope: %1 for IPv6 is Configured by %2. |
| 0xB0000082 | IPv6 的作用域: %1 由 %2 删除。 |
Scope: %1 for IPv6 is Deleted by %2. |
| 0xB0000083 | IPv6 的作用域: %1 由 %2 激活。 |
Scope: %1 for IPv6 is Activated by %2. |
| 0xB0000084 | IPv6 的作用域: %1 由 %2 停用。 |
Scope: %1 for IPv6 is DeActivated by %2. |
| 0xB0000085 | %3 更新了 IPv6 的作用域 %1 的租约首选寿命 %2。以前配置的租约首选寿命为 %4。 |
Scope: %1 for IPv6 is Updated with Lease Preferred Lifetime: %2 by %3. The previous configured Lease Preferred Lifetime was: %4. |
| 0xB0000086 | %3 更新了 IPv6 的作用域 %1 的租约有效寿命 %2。以前配置的租约有效寿命为 %4。 |
Scope: %1 for IPv6 is Updated with Lease Valid Lifetime: %2 by %3. The previous configured Lease Valid Lifetime was: %4. |
| 0xB0000087 | %3 更新了 IPv6 的作用域 %1 的选项设置 %2。 |
Scope: %1 for IPv6 is Updated with Option Setting: %2 by %3. |
| 0xB0000088 | IPv6 的作用域: %1 由 %2 启用了 DNS 动态更新。 |
Scope: %1 for IPv6 is Enabled for DNS Dynamic updates by %2. |
| 0xB0000089 | IPv6 的作用域: %1 由 %2 禁用了 DNS 动态更新。 |
Scope: %1 for IPv6 is Disabled for DNS Dynamic updates by %2. |
| 0xB000008A | %2 更新了 IPv6 的作用域 %1 的 DNS 设置: 根据 DHCP 客户端的请求动态更新 DNS AAAA 和 PTR 记录。 |
Scope: %1 for IPv6 is Updated with DNS Settings by %2: to dynamically update DNS AAAA and PTR records on request by the DHCP Clients. |
| 0xB000008B | %2 更新了 IPv6 的作用域 %1 的 DNS 设置: 始终动态更新 DNS AAAA 和 PTR 记录。 |
Scope: %1 for IPv6 is Updated with DNS Settings by %2: to always dynamically update DNS AAAA and PTR records. |
| 0xB000008C | %2 启用了 IPv6 的作用域: %1 的 DNS 设置: 删除租约时丢弃 DNS AAAA 和 PTR 记录。 |
Scope: %1 for IPv6 is Enabled for DNS Settings by %2: to discard DNS AAAA and PTR records when lease is deleted. |
| 0xB000008D | %2 禁用了 IPv6 的作用域 %1 的 DNS 设置: 删除租约时丢弃 DNS AAAA 和 PTR 记录。 |
Scope: %1 for IPv6 is Disabled for DNS Settings by %2: to discard DNS AAAA and PTR records when lease is deleted. |
| 0xB000008E | %2 在 IPv6 的作用域 %1 上启用了名称保护设置。 |
Name Protection setting is Enabled on Scope: %1 for IPv6 by %2. |
| 0xB000008F | %2 在 IPv6 的作用域 %1 上禁用了名称保护设置。 |
Name Protection setting is Disabled on Scope: %1 for IPv6 by %2. |
| 0xB0000091 | %3 在作用域 %2 下配置了 IPv6 的保留: %1。 |
Reservation: %1 for IPv6 is Configured under Scope %2 by %3. |
| 0xB0000093 | %3 在作用域 %2 下删除了 IPv6 的保留: %1。 |
Reservation: %1 for IPv6 is Deleted under Scope %2 by %3. |
| 0xB0000094 | %3 在作用域 %2 下启用了 IPv6 保留 %1 的 DNS 动态更新。 |
Reservation: %1 for IPv6 under Scope: %2 is Enabled for DNS Dynamic updates by %3. |
| 0xB0000095 | %3 在作用域 %2 下禁用了 IPv6 保留 %1 的 DNS 动态更新。 |
Reservation: %1 for IPv6 under Scope: %2 is Disabled for DNS Dynamic updates by %3. |
| 0xB0000096 | %3 在作用域 %2 下更新了 IPv6 保留 %1 的 DNS 设置: 根据 DHCP 客户端的请求动态更新 DNS AAAA 和 PTR 记录。 |
Reservation: %1 for IPv6 under Scope: %2 is Updated with DNS Settings by %3: to dynamically update DNS AAAA and PTR records on request by the DHCP Clients. |
| 0xB0000097 | %3 在作用域 %2 下更新了 IPv6 保留 %1 的 DNS 设置: 始终动态更新 DNS AAAA 和 PTR 记录。 |
Reservation: %1 for IPv6 under Scope: %2 is Updated with DNS Settings by %3: to always dynamically update DNS AAAA and PTR records. |
| 0xB0000098 | %3 在作用域 %2 下启用了 IPv6 保留 %1 的 DNS 设置: 删除租约时丢弃 DNS AAAA 和 PTR 记录。 |
Reservation: %1 for IPv6 under Scope: %2 is Enabled for DNS Settings by %3: to discard DNS AAAA and PTR records when lease is deleted. |
| 0xB0000099 | %3 在作用域 %2 下禁用了 IPv6 保留 %1 的 DNS 设置: 删除租约时丢弃 DNS AAAA 和 PTR 记录。 |
Reservation: %1 for IPv6 under Scope: %2 is Disabled for DNS Settings by %3: to discard DNS AAAA and PTR records when lease is deleted. |
| 0xB000009A | %4 在作用域 %2 下更新了 IPv6 保留 %1 的选项设置 %3。 |
Reservation: %1 for IPv6 under Scope: %2 is Updated with Option Setting: %3 by %4. |
| 0xB000009B | %3 在作用域 %2 下的 IPv6 地址池中添加了排除 IP 地址范围 %1。 |
Added exclusion IP Address range %1 in the Address Pool for IPv6 under Scope: %2 by %3. |
| 0xB000009C | %3 删除了作用域 %2 下 IPv6 地址池中的排除 IP 地址范围 %1。 |
Deleted exclusion IP Address range %1 in the Address Pool for IPv6 under Scope: %2 by %3. |
| 0xB000009D | IPv6 的作用域: %1 由 %2 修改。 |
Scope: %1 for IPv6 is Modified by %2. |
| 0xB000009E | 已为作用域 %1 启用 DHCPv6 无状态客户端清单。 |
DHCPv6 Stateless client inventory has been enabled for the scope %1. |
| 0xB000009F | 已为作用域 %1 禁用 DHCPv6 无状态客户端清单。 |
DHCPv6 Stateless client inventory has been disabled for the scope %1. |
| 0xB00000A0 | 已为服务器启用 DHCPv6 无状态客户端清单。 |
DHCPv6 Stateless client inventory has been enabled for the server. |
| 0xB00000A1 | 已为服务器禁用 DHCPv6 无状态客户端清单。 |
DHCPv6 Stateless client inventory has been disabled for the server. |
| 0xB00000A2 | 已将作用域 %1 的 DHCPv6 无状态客户端清单的清除时间间隔设置为 %2 小时。 |
Purge time interval for DHCPv6 stateless client inventory for scope %1 has been set to %2 hours. |
| 0xB00000A3 | 已将服务器的 DHCPv6 无状态客户端清单的清除时间间隔设置为 %1 小时。 |
Purge time interval for DHCPv6 stateless client inventory for server has been set to %1 hours. |
| 0xB00000A4 | %2 启用了 IPv4 的作用域: %1 的 DNS 设置: 禁用 DNS PTR 记录的动态更新。 |
Scope: %1 for IPv4 is Enabled for DNS Settings by %2: to disable dynamic updates for DNS PTR records. |
| 0xB00000A5 | %2 禁用了 IPv4 的作用域 %1 的 DNS 设置: 禁用 DNS PTR 记录的动态更新。 |
Scope: %1 for IPv4 is Disabled for DNS Settings by %2: to disable dynamic updates for DNS PTR records. |
| 0xB00000A6 | IPv6 的服务器级别选项 %1 已由 %2 更新。 |
Server level option %1 for IPv6 has been updated by %2. |
| 0xB00000A7 | %2 删除了 IPv4 的服务器级别选项 %1。 |
Server level option %1 for IPv4 has been removed by %2. |
| 0xB00000A8 | 选项设置: %3 从 IPv4 作用域 %1 中删除了 %2。 |
Option setting: %2 has been removed from IPv4 scope: %1 by %3. |
| 0xB00000A9 | 选项设置: %4 从 IPv4 作用域 %2 中的保留 %1 内删除了 %3。 |
Option setting: %3 has been removed from the reservation: %1 in IPv4 scope: %2 by %4. |
| 0xB00000AA | %2 删除了 IPv6 的服务器级别选项 %1。 |
Server level option %1 for IPv6 has been removed by %2. |
| 0xB00000AB | 选项设置: %3 从 IPv6 作用域 %1 中删除了 %2。 |
Option setting: %2 has been removed from IPv6 scope: %1 by %3. |
| 0xB00000AC | 选项设置: %4 从 Ipv6 作用域 %2 中的保留 %1 内删除了 %3。 |
Option setting: %3 has been removed from the reservation: %1 in IPv6 scope: %2 by %4. |
| 0xB0004E80 | 拒绝为硬件地址为 %1、硬件类型为 %4 且 FQDN/主机名为 %2 的计算机提供 DHCP 服务，因为该计算机与拒绝列表中的项目 %3 匹配。 |
DHCP Services were denied to machine with hardware address %1, hardware type %4 and FQDN/Hostname %2 because it matched entry %3 in the Deny List. |
| 0xB0004E81 | 拒绝为硬件地址为 %1、硬件类型为 %3 且 FQDN/主机名为 %2 的计算机提供 DHCP 服务，因为该计算机与允许列表中的所有项目都不匹配。 |
DHCP Services were denied to machine with hardware address %1, hardware type %3 and FQDN/Hostname %2 because it did not match any entry in the Allow List. |
| 0xB0004E83 | 拒绝为硬件地址为 %1、硬件类型为 %4 且未指定的 FQDN/主机名 %2 的计算机提供 DHCP 服务，因为该计算机与拒绝列表中的项目 %3 匹配。 |
DHCP Services were denied to machine with hardware address %1, hardware type %4 and unspecified FQDN/Hostname%2 because it matched entry %3 in the Deny List. |
| 0xB0004E84 | 拒绝为硬件地址为 %1、硬件类型为 %3 且未指定的 FQDN/主机名 %2 的计算机提供 DHCP 服务，因为该计算机与允许列表中的所有项目都不匹配。 |
DHCP Services were denied to machine with hardware address %1, hardware type %3 and unspecified FQDN/Hostname%2 because it did not match any entry in the Allow List. |
| 0xB0004EFC | 服务器的策略 %2 为 %1。 |
Policy %2 for server is %1. |
| 0xB0004EFD | 作用域 %3 的策略 %2 为 %1。 |
Policy %2 for scope %3 is %1. |
| 0xB0004EFE | 服务器策略 %3 的条件已设置为 %1。这些条件已按逻辑运算符 %2 进行分组。 |
The conditions for server policy %3 have been set to %1. The conditions are grouped by logical operator %2. |
| 0xB0004EFF | 作用域 %4 策略 %3 的条件已设置为 %1。这些条件已按逻辑运算符 %2 进行分组。 |
The conditions for scope %4 policy %3 have been set to %1. The conditions are grouped by logical operator %2. |
| 0xB0004F00 | 已创建新的服务器范围 IPv4 策略 %1。此策略的处理顺序为 %2。 |
A new server wide IPv4 policy %1 was created. The processing order of the policy is %2. |
| 0xB0004F01 | 已在作用域 %3 中创建新的作用域策略 %1。此策略的处理顺序为 %2。 |
A new scope policy %1 was created in scope %3. The processing order of the policy is %2. |
| 0xB0004F02 | 策略 %1 已从服务器中删除。 |
Policy %1 was deleted from server. |
| 0xB0004F03 | 已从作用域 %2 中删除策略 %1。 |
Policy %1 was deleted from scope %2. |
| 0xB0004F04 | 已为作用域 %3 策略 %2 设置从 %1 开始的 IP 地址范围。 |
The IP address range from %1 was set for the scope %3 policy %2. |
| 0xB0004F05 | 已从作用域 %3 策略 %2 中删除从 %1 开始的 IP 地址范围。 |
The IP address range from %1 was removed from the scope %3 policy %2. |
| 0xB0004F06 | 已为服务器策略 %3 的选项 %1 设置值 %2。 |
The value %2 was set for the option %1 for the server policy %3. |
| 0xB0004F07 | 已为作用域 %4 策略 %3 的选项 %1 设置值 %2。 |
The value %2 was set for the option %1 for the scope %4 policy %3. |
| 0xB0004F08 | 已从服务器策略 %3 的选项 %1 中删除值 %2。 |
The value %2 was removed from the option %1 for the server policy %3. |
| 0xB0004F09 | 已从作用域 %4 策略 %3 的选项 %1 中删除值 %2。 |
The value %2 was removed from the option %1 for the scope %4 policy %3. |
| 0xB0004F0A | 服务器策略 %2 已重命名为 %1。 |
Server policy %2 has been renamed to %1. |
| 0xB0004F0B | 作用域 %3 策略 %2 已重命名为 %1。 |
Scope %3 policy %2 has been renamed to %1. |
| 0xB0004F0C | 服务器策略 %2 的描述已设置为 %1。 |
Description of server policy %2 was set to %1. |
| 0xB0004F0D | 作用域 %3 策略 %2 的描述已设置为 %1。 |
Description of scope %3 policy %2 was set to %1. |
| 0xB0004F0E | 服务器策略 %3 的处理顺序已从 %2 更改为 %1。 |
Processing order of server policy %3 was changed to %1 from %2. |
| 0xB0004F0F | 作用域 %4 策略 %3 的处理顺序已从 %2 更改为 %1。 |
Processing order of scope %4 policy %3 was changed to %1 from %2. |
| 0xB0004F10 | 已使用以下配置参数创建服务器 %1 和 %2 之间的故障转移关系: 名称: %3，模式: 负载平衡，最长客户端提前期: %4 秒，此服务器上的负载平衡百分比: %5，自动状态切换间隔: %6 秒。 |
A failover relationship has been created between servers %1 and %2 with the following configuration parameters: name: %3, mode: load balance, maximum client lead time: %4 seconds, load balance percentage on this server: %5, auto state switchover interval: %6 seconds. |
| 0xB0004F11 | 已使用以下配置参数创建服务器 %1 和 %2 之间的故障转移关系: 名称: %3，模式: 热备用，最长客户端提前期: %4 秒，备用服务器上的保留地址百分比: %5，自动状态切换间隔: %6 秒，备用服务器: %7。 |
A failover relationship has been created between servers %1 and %2 with the following configuration parameters: name: %3, mode: hot standby, maximum client lead time: %4 seconds, reserve address percentage on standby server: %5, auto state switchover interval: %6 seconds, standby server: %7. |
| 0xB0004F12 | 已删除 %2 和 %3 之间的故障转移关系 %1。 |
Failover relationship %1 between %2 and %3 has been deleted. |
| 0xB0004F13 | 已将作用域 %1 添加到与服务器 %3 的故障转移关系 %2。 |
Scope %1 has been added to the failover relationship %2 with server %3. |
| 0xB0004F14 | 已将作用域 %1 从与服务器 %3 的故障转移关系 %2 中删除。 |
Scope %1 has been removed from the failover relationship %2 with server %3. |
| 0xB0004F15 | 与服务器 %2 的故障转移关系 %1 的故障转移配置参数 MCLT 已从 %3 秒更改为 %4 秒。 |
The failover configuration parameter MCLT for failover relationship %1 with server %2 has been changed from %3 seconds to %4 seconds. |
| 0xB0004F16 | 与服务器 %2 的故障转移关系 %1 的故障转移配置参数“自动切换间隔”已从 %3 秒更改为 %4 秒。 |
The failover configuration parameter auto switch over interval for failover relationship %1 with server %2 has been changed from %3 seconds to %4 seconds. |
| 0xB0004F17 | 与服务器 %2 的故障转移关系 %1 的故障转移配置参数“保留地址百分比”已从 %3 更改为 %4。 |
The failover configuration parameter reserve address percentage for failover relationship %1 with server %2 has been changed from %3 to %4. |
| 0xB0004F18 | 在此服务器上，与服务器 %2 的故障转移关系 %1 的故障转移配置参数“负载平衡百分比”已从 %3 更改为 %4。 |
The failover configuration parameter load balance percentage for failover relationship %1 with server %2 has been changed from %3 to %4 on this server. |
| 0xB0004F19 | 与服务器 %2 的故障转移关系 %1 的故障转移配置参数“模式”已从“热备用”更改为“负载平衡”。 |
The failover configuration parameter mode for failover relationship %1 with server %2 has been changed from hot standby to load balance. |
| 0xB0004F1A | 与服务器 %2 的故障转移关系 %1 的故障转移配置参数模式已从“负载平衡”更改为“热备用”。 |
The failover configuration parameter mode for failover relationship %1 with server %2 has been changed from load balance to hot standby. |
| 0xB0004F1B | 故障转移关系 %2 的服务器 %1 的故障转移状态已从 %3 更改为 %4。 |
The failover state of server: %1 for failover relationship: %2 changed from: %3 to %4. |
| 0xB0004F1D | 服务器检测到与故障转移关系 %2 的伙伴服务器 %1 的同步超时。同步超时 %3 秒。 |
The server detected that it is out of time synchronization with partner server: %1 for failover relationship: %2. The time is out of sync by: %3 seconds . |
| 0xB0004F1E | 服务器已与关系 %2 的故障转移伙伴服务器 %1 建立联系。 |
Server has established contact with failover partner server %1 for relationship %2 . |
| 0xB0004F1F | 服务器已失去与关系 %2 的故障转移伙伴服务器 %1 的联系。 |
Server has lost contact with failover partner server %1 for relationship %2 . |
| 0xB0004F20 | 来自故障转移关系 %2 的服务器 %1 的故障转移协议消息 BINDING-UPDATE 被拒绝，因为无法比较消息摘要。 |
Failover protocol message BINDING-UPDATE from server %1 for failover relationship %2 was rejected because message digest failed to compare. |
| 0xB0004F21 | 来自故障转移关系 %2 的服务器 %1 的故障转移协议消息 BINDING-UPDATE 被拒绝，因为未配置消息摘要。 |
Failover protocol message BINDING-UPDATE from server %1 for failover relationship %2 was rejected because message digest was not configured. |
| 0xB0004F22 | 来自故障转移关系 %2 的服务器 %1 的故障转移协议消息 BINDING-UPDATE 被拒绝，因为消息摘要不存在。 |
Failover protocol message BINDING-UPDATE from server %1 for failover relationship %2 is rejected because message digest was not present. |
| 0xB0004F23 | 故障转移关系 %2 的服务器 %1 的故障转移状态已更改为 %3。 |
The failover state of server: %1 for failover relationship: %2 changed to : %3. |
| 0xB0004F25 | 来自故障转移关系 %2 的服务器 %1 的故障转移协议消息 BINDING-ACK 被拒绝，因为消息摘要无法比较。 |
Failover protocol message BINDING-ACK from server %1 for failover relationship %2 was rejected because message digest failed to compare. |
| 0xB0004F26 | 来自故障转移关系 %2 的服务器 %1 的故障转移协议消息 BINDING-ACK 被拒绝，因为未配置消息摘要。 |
Failover protocol message BINDING-ACK from server %1 for failover relationship %2 was rejected because message digest was not configured. |
| 0xB0004F27 | 来自故障转移关系 %2 的服务器 %1 的故障转移协议消息 BINDING-ACK 被拒绝，因为消息摘要不存在。 |
Failover protocol message BINDING-ACK from server %1 for failover relationship %2 is rejected because message digest was not present. |
| 0xB0004F28 | 来自故障转移关系 %2 的服务器 %1 的故障转移协议消息 CONNECT 被拒绝，因为无法比较消息摘要。 |
Failover protocol message CONNECT from server %1 for failover relationship %2 was rejected because message digest failed to compare. |
| 0xB0004F29 | 来自故障转移关系 %2 的服务器 %1 的故障转移协议消息 CONNECT 被拒绝，因为未配置消息摘要。 |
Failover protocol message CONNECT from server %1 for failover relationship %2 was rejected because message digest was not configured. |
| 0xB0004F2A | 来自故障转移关系 %2 的服务器 %1 的故障转移协议消息 CONNECT 被拒绝，因为消息摘要不存在。 |
Failover protocol message CONNECT from server %1 for failover relationship %2 is rejected because message digest was not present. |
| 0xB0004F2B | 来自故障转移关系 %2 的服务器 %1 的故障转移协议消息 CONNECTACK 被拒绝，因为无法比较消息摘要。 |
Failover protocol message CONNECTACK from server %1 for failover relationship %2 was rejected because message digest failed to compare. |
| 0xB0004F2C | 来自故障转移关系 %2 的服务器 %1 的故障转移协议消息 CONNECTACK 被拒绝，因为未配置消息摘要。 |
Failover protocol message CONNECTACK from server %1 for failover relationship %2 was rejected because message digest was not configured. |
| 0xB0004F2D | 来自故障转移关系 %2 的服务器 %1 的故障转移协议消息 CONNECTACK 被拒绝，因为消息摘要不存在。 |
Failover protocol message CONNECTACK from server %1 for failover relationship %2 is rejected because message digest was not present. |
| 0xB0004F2E | 来自故障转移关系 %2 的服务器 %1 的故障转移协议消息 UPDREQALL 被拒绝，因为无法比较消息摘要。 |
Failover protocol message UPDREQALL from server %1 for failover relationship %2 was rejected because message digest failed to compare. |
| 0xB0004F2F | 来自故障转移关系 %2 的服务器 %1 的故障转移协议消息 UPDREQALL 被拒绝，因为未配置消息摘要。 |
Failover protocol message UPDREQALL from server %1 for failover relationship %2 was rejected because message digest was not configured. |
| 0xB0004F30 | 来自故障转移关系 %2 的服务器 %1 的故障转移协议消息 UPDREQALL 被拒绝，因为消息摘要不存在。 |
Failover protocol message UPDREQALL from server %1 for failover relationship %2 is rejected because message digest was not present. |
| 0xB0004F31 | 来自故障转移关系 %2 的服务器 %1 的故障转移协议消息 UPDDONE 被拒绝，因为无法比较消息摘要。 |
Failover protocol message UPDDONE from server %1 for failover relationship %2 was rejected because message digest failed to compare. |
| 0xB0004F32 | 来自故障转移关系 %2 的服务器 %1 的故障转移协议消息 UPDDONE 被拒绝，因为未配置消息摘要。 |
Failover protocol message UPDDONE from server %1 for failover relationship %2 was rejected because message digest was not configured. |
| 0xB0004F33 | 来自故障转移关系 %2 的服务器 %1 的故障转移协议消息 UPDDONE 被拒绝，因为消息摘要不存在。 |
Failover protocol message UPDDONE from server %1 for failover relationship %2 is rejected because message digest was not present. |
| 0xB0004F34 | 来自故障转移关系 %2 的服务器 %1 的故障转移协议消息 UPDREQ 被拒绝，因为无法比较消息摘要。 |
Failover protocol message UPDREQ from server %1 for failover relationship %2 was rejected because message digest failed to compare. |
| 0xB0004F35 | 来自故障转移关系 %2 的服务器 %1 的故障转移协议消息 UPDREQ 被拒绝，因为未配置消息摘要。 |
Failover protocol message UPDREQ from server %1 for failover relationship %2 was rejected because message digest was not configured. |
| 0xB0004F36 | 来自故障转移关系 %2 的服务器 %1 的故障转移协议消息 UPDREQ 被拒绝，因为消息摘要不存在。 |
Failover protocol message UPDREQ from server %1 for failover relationship %2 is rejected because message digest was not present. |
| 0xB0004F37 | 来自故障转移关系 %2 的服务器 %1 的故障转移协议消息 STATE 被拒绝，因为无法比较消息摘要。 |
Failover protocol message STATE from server %1 for failover relationship %2 was rejected because message digest failed to compare. |
| 0xB0004F38 | 来自故障转移关系 %2 的服务器 %1 的故障转移协议消息 STATE 被拒绝，因为未配置消息摘要。 |
Failover protocol message STATE from server %1 for failover relationship %2 was rejected because message digest was not configured. |
| 0xB0004F39 | 来自故障转移关系 %2 的服务器 %1 的故障转移协议消息 STATE 被拒绝，因为消息摘要不存在。 |
Failover protocol message STATE from server %1 for failover relationship %2 is rejected because message digest was not present. |
| 0xB0004F3A | 来自故障转移关系 %2 的服务器 %1 的故障转移协议消息 CONTACT 被拒绝，因为无法比较消息摘要。 |
Failover protocol message CONTACT from server %1 for failover relationship %2 was rejected because message digest failed to compare. |
| 0xB0004F3B | 来自故障转移关系 %2 的服务器 %1 的故障转移协议消息 CONTACT 被拒绝，因为未配置消息摘要。 |
Failover protocol message CONTACT from server %1 for failover relationship %2 was rejected because message digest was not configured. |
| 0xB0004F3C | 来自故障转移关系 %2 的服务器 %1 的故障转移协议消息 CONTACT 被拒绝，因为消息摘要不存在。 |
Failover protocol message CONTACT from server %1 for failover relationship %2 is rejected because message digest was not present. |
| 0xB0004F3D | 在注册表项 HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\DHCPServer\\Parameters\\Failover 下，为 FailoverCryptoAlgorithm 中的故障转移消息身份验证指定了无效的加密算法 %1。该操作已中止。 |
An invalid cryptographic algorithm %1 was specified for failover message authentication in FailoverCryptoAlgorithm under registry key HKEY_LOCAL_MACHINE\\SYSTEM\\CurrentControlSet\\Services\\DHCPServer\\Parameters\\Failover. The operation is halted. |
| 0xB0004F3E | 由于内部 BINDING UPDATE 队列已满，因此 IP 地址 %1 的 BINDING UPDATE 消息无法复制到故障转移关联 %3 的伙伴服务器 %2。 |
BINDING UPDATE message for IP address %1 could not be replicated to the partner server %2 of failover relation %3 as the internal BINDING UPDATE queue is full. |
| 0xB0004F3F | 已丢弃来自 %1 的 DHCP 客户端请求，因为作用域/超级作用域 %2 中的适用 IP 地址范围不在可用的 IP 地址范围内。这可能是因为某个策略的 IP 地址范围不在可用的 IP 地址范围内。 |
DHCP client request from %1 was dropped since the applicable IP address ranges in scope/superscope %2 are out of available IP addresses. This could be because of IP address ranges of a policy being out of available IP addresses. |
| 0xB0004F40 | 对于故障转移关系 %2，此 DHCP 服务器 %1 已转换为“合作伙伴已关闭”状态，并且 %3 秒的 MCLT 期限已过。对于属于故障转移关系的所有作用域，该服务器已接管合作伙伴服务器 %4 的可用 IP 地址池。 |
This DHCP server %1 has transitioned to a PARTNER DOWN state for the failover relationship %2 and the MCLT period of %3 seconds has expired. The server has taken over the free IP address pool of the partner server %4 for all scopes which are part of the failover relationship. |
| 0xB0004F41 | 对于绑定状态为 %3 的 IP 地址 %2，已向故障转移关系 %5 的伙伴服务器 %4 发送事务 ID 为 %1 的 BINDING-UPDATE 消息。 |
A BINDING-UPDATE message with transaction id: %1 was sent for IP address: %2 with binding status: %3 to partner server: %4 for failover relationship: %5. |
| 0xB0004F42 | 对于绑定状态为 %3 的 IP 地址 %2，已从故障转移关系 %5 的伙伴服务器 %4 接收到事务 ID 为 %1 的 BINDING-UPDATE 消息。 |
A BINDING-UPDATE message with transaction id: %1 was received for IP address: %2 with binding status: %3 from partner server: %4 for failover relationship: %5. |
| 0xB0004F43 | 对于拒绝原因为(%3)的 IP 地址 %2，已向故障转移关系 %5 的伙伴服务器 %4 发送事务 ID 为 %1 的 BINDING-ACK 消息。 |
A BINDING-ACK message with transaction id: %1 was sent for IP address: %2 with reject reason: (%3) to partner server: %4 for failover relationship: %5. |
| 0xB0004F44 | 对于拒绝原因为(%3)的 IP 地址 %2，已从故障转移关系 %5 的伙伴服务器 %4 接收到事务 ID 为 %1 的 BINDING-ACK 消息。 |
A BINDING-ACK message with transaction id: %1 was received for IP address: %2 with reject reason: (%3 ) from partner server: %4 for failover relationship: %5. |
| 0xB0004F45 | 已向故障转移关系 %3 的伙伴服务器 %2 发送事务 ID 为 %1 的 UPDREQ 消息。 |
A UPDREQ message with transaction id: %1 was sent to partner server: %2 for failover relationship: %3. |
| 0xB0004F46 | 已从故障转移关系 %3 的伙伴服务器 %2 接收到事务 ID 为 %1 的 UPDREQ 消息 |
A UPDREQ message with transaction id: %1 was received from partner server: %2 for failover relationship: %3 |
| 0xB0004F47 | 已向故障转移关系 %3 的伙伴服务器 %2 发送事务 ID 为 %1 的 UPDDONE 消息。 |
A UPDDONE message with transaction id: %1 was sent to partner server: %2 for failover relationship: %3. |
| 0xB0004F48 | 已从故障转移关系 %3 的伙伴服务器 %2 接收到事务 ID 为 %1 的 UPDDONE 消息。 |
A UPDDONE message with transaction id: %1 was received from partner server: %2 for failover relationship: %3. |
| 0xB0004F49 | 已向故障转移关系 %3 的伙伴服务器 %2 发送事务 ID 为 %1 的 UPDREQALL 消息 |
A UPDREQALL message with transaction id: %1 was sent to partner server: %2 for failover relationship: %3 |
| 0xB0004F4A | 已从故障转移关系 %3 的伙伴服务器 %2 接收到事务 ID 为 %1 的 UPDREQALL 消息 |
A UPDREQALL message with transaction id: %1 was received from partner server: %2 for failover relationship: %3 |
| 0xB0004F4B | 已向故障转移关系 %3 的伙伴服务器 %2 发送事务 ID 为 %1 的 CONTACT 消息。 |
A CONTACT message with transaction id: %1 was sent to partner server: %2 for failover relationship: %3. |
| 0xB0004F4C | 已从故障转移关系 %3 的伙伴服务器 %2 接收到事务 ID 为 %1 的 CONTACT 消息。 |
A CONTACT message with transaction id: %1 was received from partner server: %2 for failover relationship: %3. |
| 0xB0004F4D | 已向故障转移关系 %3 的伙伴服务器 %2 发送事务 ID 为 %1 的 CONNECT 消息。 |
A CONNECT message with transaction id: %1 was sent to partner server: %2 for failover relationship: %3. |
| 0xB0004F4E | 已从故障转移关系 %3 的伙伴服务器 %2 接收到事务 ID 为 %1 的 CONNECT 消息。 |
A CONNECT message with transaction id: %1 was received from partner server: %2 for failover relationship: %3. |
| 0xB0004F4F | 已向故障转移关系 %3 的伙伴服务器 %2 发送事务 ID 为 %1 的 STATE 消息，状态为: %4，状态的开始时间为: %5。 |
A STATE message with transaction id: %1 was sent to partner server : %2 for failover relationship %3 with state: %4 and start time of state: %5. |
| 0xB0004F50 | 已从故障转移关系 %3 的伙伴服务器 %2 接收到事务 ID 为 %1 的 STATE 消息，状态为 %4 且状态的开始时间为 %5。 |
A STATE message with transaction id: %1 was received from partner server : %2 for failover relationship %3 with state: %4 and start time of state %5. |
| 0xB0004F51 | 已向故障转移关系 %3 的伙伴服务器 %2 发送事务 ID 为 %1 的 CONNECTACK 消息。 |
A CONNECTACK message with transaction id %1 was sent to partner server : %2 for failover relationship: %3. |
| 0xB0004F52 | 已从故障转移关系 %3 的伙伴服务器 %2 接收到事务 ID 为 %1 的 CONNECTACK 消息。 |
A CONNECTACK message with transaction id %1 was received from partner server : %2 for failover relationship: %3. |
| 0xB0004F53 | 对于 IP 地址 %2，已向故障转移关系 %4 的伙伴服务器 %3 发送事务 ID 为 %1 的 BINDING-ACK 消息。 |
A BINDING-ACK message with transaction id: %1 was sent for IP address: %2 to partner server: %3 for failover relationship: %4. |
| 0xB0004F54 | 对于 IP 地址 %2，已从故障转移关系 %4 的伙伴服务器 %3 接收到事务 ID 为 %1 的 BINDING-ACK 消息。 |
A BINDING-ACK message with transaction id: %1 was received for IP address: %2 from partner server: %3 for failover relationship: %4. |
| 0xB0004F55 | 已向故障转移关系 %3 的伙伴服务器 %2 发送事务 ID 为 %1 的 CONNECTACK 消息，拒绝原因为: %4。 |
A CONNECTACK message with transaction id %1 was sent to partner server : %2 for failover relationship: %3 with reject reason: %4. |
| 0xB0004F56 | 已从故障转移关系 %3 的伙伴服务器 %2 接收到事务 ID 为 %1 的 CONNECTACK 消息，拒绝原因为: %4。 |
A CONNECTACK message with transaction id %1 was received from partner server : %2 for failover relationship: %3 with reject reason: %4. |
| 0xB0004F57 | 已更改与服务器 %1 的故障转移关系 %2 的共享机密。 |
The shared secret for failover relationship %2 with server %1 has been changed. |
| 0xB0004F58 | 已为与服务器 %1 的故障转移关系 %2 启用消息身份验证。 |
Message authentication for failover relationship %2 with server %1 has been enabled. |
| 0xB0004F59 | 已为与服务器 %1 的故障转移关系 %2 禁用消息身份验证。 |
Message authentication for failover relationship %2 with server %1 has been disabled. |
| 0xB0004F5A | %1 |
%1 |
| 0xB0004F5B | 作用域为 %3 且策略为 %2 的 DNSSuffix 设置为 %1。 |
DNSSuffix of scope %3 policy %2 was set to %1. |
| 0xB0004F5C | 服务器策略为 %2 的 DNSSuffix 设置为 %1。 |
DNSSuffix of server policy %2 was set to %1. |
| 0xB0004F5D | IPv4 地址 %1 和 FQDN %2 的转发记录注册失败，错误为 %3。这很可能是因为 DNS 服务器上不存在该记录的正向查找区域。 |
Forward record registration for IPv4 address %1 and FQDN %2 failed with error %3. This is likely to be because the forward lookup zone for this record does not exist on the DNS server. |
| 0xB0004F5E | IPv4 地址 %1 和 FQDN %2 的转发记录注册失败，错误为 %3。 |
Forward record registration for IPv4 address %1 and FQDN %2 failed with error %3. |
| 0xB0004F5F | IPv4 地址 %1 和 FQDN %2 的转发记录注册失败，错误为 %3 (%4)。 |
Forward record registration for IPv4 address %1 and FQDN %2 failed with error %3 (%4). |
| 0xB0004F60 | IPv4 地址 %1 和 FQDN %2 的 PTR 记录注册失败，错误为 %3。这很可能是因为 DNS 服务器上不存在该记录的反向查找区域。 |
PTR record registration for IPv4 address %1 and FQDN %2 failed with error %3. This is likely to be because the reverse lookup zone for this record does not exist on the DNS server. |
| 0xB0004F61 | IPv4 地址 %1 和 FQDN %2 的 PTR 记录注册失败，错误为 %3。 |
PTR record registration for IPv4 address %1 and FQDN %2 failed with error %3. |
| 0xB0004F62 | IPv4 地址 %1 和 FQDN %2 的 PTR 记录注册失败，错误为 %3 (%4)。 |
PTR record registration for IPv4 address %1 and FQDN %2 failed with error %3 (%4). |
| 0xB0004F63 | IPv6 地址 %1 和 FQDN %2 的转发记录注册失败，错误为 %3。这很可能是因为 DNS 服务器上不存在该记录的正向查找区域。 |
Forward record registration for IPv6 address %1 and FQDN %2 failed with error %3. This is likely to be because the forward lookup zone for this record does not exist on the DNS server. |
| 0xB0004F64 | IPv6 地址 %1 和 FQDN %2 的转发记录注册失败，错误为 %3。 |
Forward record registration for IPv6 address %1 and FQDN %2 failed with error %3. |
| 0xB0004F65 | IPv6 地址 %1 和 FQDN %2 的转发记录注册失败，错误为 %3 (%4)。 |
Forward record registration for IPv6 address %1 and FQDN %2 failed with error %3 (%4). |
| 0xB0004F66 | IPv6 地址 %1 和 FQDN %2 的 PTR 记录注册失败，错误为 %3。这很可能是因为 DNS 服务器上不存在该记录的反向查找区域。 |
PTR record registration for IPv6 address %1 and FQDN %2 failed with error %3. This is likely to be because the reverse lookup zone for this record does not exist on the DNS server. |
| 0xB0004F67 | IPv6 地址 %1 和 FQDN %2 的 PTR 记录注册失败，错误为 %3。 |
PTR record registration for IPv6 address %1 and FQDN %2 failed with error %3. |
| 0xB0004F68 | IPv6 地址 %1 和 FQDN %2 的 PTR 记录注册失败，错误为 %3 (%4)。 |
PTR record registration for IPv6 address %1 and FQDN %2 failed with error %3 (%4). |