403Webshell
Server IP : 209.209.40.120  /  Your IP : 216.73.217.112
Web Server : Microsoft-IIS/10.0
System : Windows NT NEWWWW 10.0 build 17763 (Windows Server 2019) i586
User : NEWWWW$ ( 0)
PHP Version : 8.3.30
Disable Function : NONE
MySQL : OFF  |  cURL : ON  |  WGET : OFF  |  Perl : OFF  |  Python : OFF  |  Sudo : OFF  |  Pkexec : OFF
Directory :  C:/Windows/System32/en-US/

Upload File :
current_dir [ Writeable ] document_root [ Writeable ]

 

Command :

[ Back ]     

Current File : C:/Windows/System32/en-US/dhcpsapi.dll.mui
MZ����@���	�!�L�!This program cannot be run in DOS mode.

$�<ߵ�R���R���R�Ы����R�ЫP���R�Rich��R�PEL�!


0�@ �8.rdata�@@.rsrc @@/B�
T88/B�$��8.rdata8x.rdata$zzzdbg @.rsrc$01@!�.rsrc$02 �<E9����]l;��&��x/�C
B=�7/B�0�0�H�`�x���������	�			 8!���!8�(#����MUI�������!��_<-��T��a���|�e�_�3����MUIen-US
DHCP Users5Members who have view-only access to the DHCP serviceDHCP Administrators:Members who have administrative access to the DHCP Service���a�
')'���*+� N'N��)N>N��@NN8��N�N0#�N�N�$�N�NXA88De0y04DPP\Gzp}p�G��DHF���tJ����<}�����}�N��N���N��N�p��N�hO���The DHCP service received the unknown option %1, with a length of %2. The raw option data is given below.

�The DHCP service failed to register with Service Controller. The following error occurred: %n%1.

�The DHCP service failed to initialize its global parameters. The following error occurred: %n%1

�The DHCP service failed to initialize its registry parameters. The following error occurred: %n%1

�The DHCP service failed to initialize the database. The following error occurred: %n%1

�The DHCP service failed to initialize Winsock startup. The following error occurred: %n%1

�The DHCP service failed to start as a RPC server. The following error occurred : %n%1

�The DHCP service failed to initialize Winsock data. The following error occurred: %n%1

�The DHCP service is shutting down due to the following error: %n%1

�The DHCP service encountered the following error while cleaning up the pending client records: %n%1

�The DHCP service encountered the following error while cleaning up the database: %n%1

�The DHCP service issued a NACK (negative acknowledgement message) to the client, %2, for the address, %1.

dThe DHCP client, %2, declined the address %1.

dThe DHCP Client, %2, released the address %1.

�The DHCP service encountered the following error when backing up the database: %n%1

�The DHCP service encountered the following error when backing up the registry configuration: %n%1

�The DHCP service failed to restore the database. The following error occurred: %n%1

�The DHCP service failed to restore the DHCP registry configuration. The following error occurred: %n%1

�Scope, %1, is %2 percent full with only %3 IP addresses remaining.

�The DHCP service could not load the JET database library successfully.

pThe 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.

hThe 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.

dThe DHCP service has initialized and is ready

`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.

�The DHCP service was unable to read the global BOOTP file name from the registry.

XThe audit log file cannot be appended.

�The DHCP service failed to initialize the audit log. The following error occurred: %n%1

�The DHCP service was unable to ping for a new IP address. The address was leased to the client.

�The audit log file could not be backed up.  The following error occurred: %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.

XThe 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.

�The DHCP service has successfully loaded one or more callout DLLs.

�The DHCP service has failed to load one or more callout DLLs. The following error occured: %n%1

The DHCP service was unable to create or lookup the DHCP Users local group on this computer.  The error code is in the data.

The DHCP server was unable to create or lookup the DHCP Administrators local group on this computer.  The error code is in the data.

xThe DHCP service has started to clean up the database.

@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.

lThe 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.

tThe DHCP service successfully restored the database.

lThe 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.

�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

�The DHCP/BINL service on the local machine has determined that it is authorized to start.  It is servicing clients now.

`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.

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.

DThe 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.

xThe 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).

�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).

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.

�The DHCP/BINL service on the local machine encountered a network error. The error was: %3.

�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).

The DHCP/BINL service on this workgroup server has encountered another server with IP Address, %1, belonging to the domain %2.

�The DHCP/BINL service has encountered another server on this network with IP Address, %1, belonging to the domain: %2.

�The DHCP/BINL service on this computer is shutting down. See the previous event log messages for reasons.

(The DHCP service was unable to impersonate the credentials necessary for DNS registrations: %n%1.  The local system credentials is being used.

�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.

�The DHCP service was unable to convert the temporary database to ESE format: %n%1.

�The DHCP service failed to initialize its configuration parameters. The following error occurred: %n%1

�The DHCP service failed to see a directory server for authorization.

�The DHCP service was unable to access path specified for the audit log.

�The DHCP service was unable to access path specified for the database backups.

�The DHCP service was unable to access path specified for the database

�There are no IP addresses available for lease in the scope or superscope "%1".

�There are no IP addresses available for BOOTP clients in the scope or superscope "%1".

HThere were some orphaned entries deleted in the configuration due to the deletion of a class or an option definition. Please recheck the server configuration.

�The DHCP/BINL service is not authorized in the directory service domain "%2" (Server IP Address %1)

�The DHCP/BINL service is authorized in the directory service domain "%2" (Server IP Address %1)

�The DHCP/BINL service has not determined if it is authorized in directory domain "%2" (Server IP Address %1)

�Iashlpr could not contact the NPS server:%n%1, check if IAS service is started.

�Iashlpr initialization failed: %1, so DHCP server cannot talk to NPS server. It could be that IAS service is not started.

(Dynamic Bootp%0

Renew%0

Release%0

 Conflict%0

$Scope Full%0

Started%0

Stopped%0

0Audit Log Paused%0

$dhcpsrv.log%0

$BAD_ADDRESS%0

LThis address is already in use%0

NACK%0

Deleted%0

<DNS record not deleted%0

Expired%0

`%%d leases expired and %%d leases deleted%0

<Database Cleanup Begin%0

D%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.

0BOOTP Range Full%0

(BOOTP deleted%0

4DhcpSrvLog-Sun.log%0

4DhcpSrvLog-Mon.log%0

4DhcpSrvLog-Tue.log%0

4DhcpSrvLog-Wed.log%0

4DhcpSrvLog-Thu.log%0

4DhcpSrvLog-Fri.log%0

4DhcpSrvLog-Sat.log%0

4Unreachable Domain%0

<Authorization succeeded%0

,Server Upgraded%0

8Cached authorization%0

8Authorization failed%0

8Authorized(servicing)%0

`Authorization failure, stopped servicing%0

DServer found in our domain%0

8Could not find domain%0

,Network failure%0

4No DC is DS Enabled%0

\Server found that belongs to DS domain%0

@Another server was found%0

DRestarting rogue detection%0

`No static IP address bound to DHCP server%0

LMicrosoft Windows 2000 Options%0

�Microsoft vendor-specific options for Windows 2000 and above Clients%0

HMicrosoft Windows 98 Options%0

�Microsoft vendor-specific options for Windows 98 Clients%0

0Microsoft Options%0

�Microsoft vendor-specific options applicable to all Windows Clients%0

PMicrosoft Disable Netbios Option %0

�Option for enabling or disabling Netbios for Microsoft Windows 2000 Clients%0

lMicrosoft Release DHCP Lease On Shutdown Option%0

�Option for enabling or disabling Windows 2000 Clients to release DHCP lease on shutdown%0

XMicrosoft Default Router Metric Base%0

�Default Router Base Metrics for Microsoft Windows 2000 Clients%0

 Internal%0

$DHCP Users%0

xMembers who have view-only access to the DHCP service%0

4DHCP Administrators%0

|Members who have administrative access to DHCP service%0

\Default Routing and Remote Access Class%0

XUser class for remote access clients%0

4Default BOOTP Class%0

HUser class for BOOTP Clients%0

<Classless Static Routes%0

�Destination, mask and router IP addresses in priority order%0

4DNS Update Request%0

0DNS Update Failed%0

8DNS Update Successful%0

\Default Network Access Protection Class%0

�Default special user class for Restricted Access clients%0

Assign%0

�The DHCP server is unable to reach the NPS server for determining the client's NAP access state %0.

Bootp%0

$This computer has at least one dynamically assigned IP address. For reliable DHCP Server operation, you should use only static IP addresses.

@Microsoft Windows Options%0

xMicrosoft vendor-specific options for Windows Clients%0

Enabled%0

 Disabled%0

EQ %0

NEQ %0

AND%0

OR%0

(Vendor Class %0

$User Class %0

(MAC address %0

$Client Id %0

0Relay Agent Info %0

LRelay Agent Info - Circuit Id %0

HRelay Agent Info - Remote Id %0

PRelay Agent Info - Subscriber Id %0

, %0

; %0

*%0

HFully Qualified Domain Name %0

,Is Single Label%0

4Is Not Single Label%0

Reserved

Reserved

Reserved

Reserved

Reserved

Reserved

Reserved

Reserved

Reserved

8DhcpV6SrvLog-Sun.log%0

8DhcpV6SrvLog-Mon.log%0

8DhcpV6SrvLog-Tue.log%0

8DhcpV6SrvLog-Wed.log%0

8DhcpV6SrvLog-Thu.log%0

8DhcpV6SrvLog-Fri.log%0

8DhcpV6SrvLog-Sat.log%0

HSIP Server Domain Name List %0

tDomain Name of SIP servers available to the client %0

LSIP Servers IPv6 Address List %0

|IPv6 addresses of SIP servers available to the client %0

hDNS Recursive Name Server IPv6 Address List %0

�IPv6 Addresses of DNS recursive name servers available to the client %0

4Domain Search List %0

�Domain search list used by clients to resolve hostnames with DNS, by preference %0

<NIS IPv6 Address List %0

|IPv6 Addresses of NIS servers available to the client %0

<NIS+ IPv6 Address List %0

|IPv6 Addresses of NIS+ servers available to the client %0

0NIS Domain List %0

xDomain names of NIS servers available to the client %0

<NIS+ Domain Name List %0

xDomain names of NIS+ servers available to the client %0

LSNTP Servers IPv6 Address List %0

|IPv6 Addresses of SNTP servers available to the client %0

@Information Refresh Time %0

This option specifies an upper bound for how long a client should wait before refreshing information retrieved from DHCPv6 Server %0


%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.

,Packet dropped%0

8DHCP Standard Options%0

4Default User Class%0

%0

8UTC offset in seconds%0

Router%0

lArray of router addresses ordered by preference%0

$Time Server%0

hArray of time server addresses, by preference%0

(Name Servers%0

lArray of name servers [IEN 116], by preference%0

$DNS Servers%0

TArray of DNS servers, by preference%0

$Log Servers%0

dArray of MIT_LCS UDP log servers on subnet%0

,Cookie Servers%0

PArray of cookie servers, RFC 865%0

$LPR Servers%0

`Array of RFC 1179 servers, by preference%0

,Impress Servers%0

LArray of Imagen Impress Servers%0

@Resource Location Servers%0

�Array of RFC 887 ResLoc Servers on subnet, by preference%0

 Host Name%0

hHost name for client, RFC 1035 character set%0

,Boot File Size%0

dSize of boot image file in 512-octet blocks%0

,Merit Dump File%0

HPath name for crash dump file%0

,DNS Domain Name%0

\DNS Domain name for client resolutions%0

$Swap Server%0

LAddress of client's swap server%0

 Root Path%0

xPath name for client's root disk, char set NVT ASCII%0

,Extensions Path%0

Ltftp file for option extensions%0

4IP Layer Forwarding%0

tDisable/enable IP packet forwarding on this client%0

<Nonlocal Source Routing%0

PDisable/enable nonlocal datagrams%0

4Policy Filter Masks%0

�Destination/mask IP address pairs to filter source routes%0

<Max DG Reassembly Size%0

|Maximum size datagram for reassembly by client; max 576%0

<Default IP Time-to-live%0

hDefault TTL for client's use on outgoing DGs%0

<Path MTU Aging Timeout%0

|Timeout in seconds for aging Path MTU values; RFC 1191%0

<Path MTU Plateau Table%0

lMTU discovery sizes, sorted by size, all >= 68%0

$MTU Option%0

@MTU discovery size, >= 68%0

8All subnets are local%0

hThe client assumes that all subnets are local%0

0Broadcast Address%0

0Broadcast address%0

<Perform Mask Discovery%0

xThe client should use ICMP for subnet mask discovery.%0

8Mask Supplier Option%0

�The client should respond to subnet mask requests via ICMP.%0

@Perform Router Discovery%0

pThe client should solicit routers using RFC 1256.%0

DRouter Solicitation Address%0

\Address to use for router solicitation%0

4Static Route Option%0

tDestination/router address pairs, in priority order%0

8Trailer Encapsulation%0

|The client should negotiate use of trailers (RFC 983).%0

0ARP Cache Timeout%0

`Timeout in seconds for ARP cache entries%0

<Ethernet Encapsulation%0

h0=>client should use ENet V2; 1=> IEEE 802.3%0

@TCP Default Time-to-live%0

lTTL that client uses when sending TCP segments%0

4Keepalive Interval%0

HKeepalive timeout in seconds%0

0Keepalive Garbage%0

4Send garbage octet%0

,NIS Domain Name%0

dName of Network Information Service domain%0

$NIS Servers%0

dAddresses of NIS servers on client's subnet%0

$NTP Servers%0

dAddresses of Network Time Protocol servers%0

8Vendor Specific Info%0

PEmbedded vendor-specific options%0

0WINS/NBNS Servers%0

TNBNS Address(es) in priority order%0

@NetBIOS over TCP/IP NBDD%0

|NetBIOS over TCP/IP NBDD address(es) in priority order%0

4WINS/NBT Node Type%0

|0x1 = B-node, 0x2 = P-node, 0x4 = M-node, 0x8 = H-node%0

0NetBIOS Scope ID%0

HNetBIOS over TCP/IP Scope ID%0

8X Window System Font%0

LArray of X Windows font servers%0

<X Window System Display%0

\Array of X Windows Display Mgr servers%0

Lease%0

\Client IP address lease time in seconds%0

<Renewal (T1) Time Value%0

lTime between addr assignment to RENEWING state%0

@Rebinding (T2) Time Value%0

hTime from addr assignment to REBINDING state%0

0NIS+ Domain Name%0

XThe name of the client's NIS+ domain.%0

(NIS+ Servers%0

lA list of IP addresses indicating NIS+ servers%0

8Boot Server Host Name%0

DTFTP boot server host name%0

(Bootfile Name%0

(Bootfile Name%0

8Mobile IP Home Agents%0

\Mobile IP home agents in priority order%0

hSimple Mail Transport Protocol (SMTP) Servers%0

hList of SMTP servers available to the client%0

TPost Office Protocol (POP3) Servers%0

hList of POP3 servers available to the client%0

lNetwork News Transport Protocol (NNTP) Servers%0

hList of NNTP servers available to the client%0

HWorld Wide Web (WWW) Servers%0

dList of WWW servers available to the client%0

,Finger Servers%0

lList of Finger servers available to the client%0

PInternet Relay Chat (IRC) Servers%0

dList of IRC servers available to the client%0

4StreetTalk Servers%0

tList of StreetTalk servers available to the client%0

$Subnet Mask%0

lStreetTalk Directory Assistance (STDA) Servers%0

hList of STDA servers available to the client%0

PSubnet mask in network byte order%0

$Time Offset%0

�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.

�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.

hThe 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.

�There are no IP addresses available for lease in IP address range(s) of the policy %1 in scope %2.

tIP address range of scope %1 is out of IP addresses.

�Ip address range(s) for the scope %1 policy %2 is %3 percent full with only %4 IP addresses available .

|The DNS IP Address %1 is not a valid DNS Server Address.

�DNS update request failed as the DNS update requests queue limit exceeded%0

@DNS update request failed%0

�DNS IPv6 update request failed as the DNS update requests queue limit exceeded%0

LDNS IPv6 update request failed%0

 Reserved%0

pIllegal IP address (not part of any address pool)%0

xFatal conflict exists: address in use by other client%0

DMissing binding information%0

hConnection rejected, time mismatch too great%0

PConnection rejected, invalid MCLT%0

TConnection rejected, unknown reason%0

`Connection rejected, duplicate connection%0

hConnection rejected, invalid failover partner%0

0TLS not supported%0

PTLS supported but not configured%0

`TLS required but not supported by partner%0

HMessage digest not supported%0

HMessage digest not configured%0

@Protocol version mismatch%0

HOutdated binding information%0

PLess critical binding information%0

PNo traffic within sufficient time%0

LHash bucket assignment conflict%0

LIP not reserved on this server%0

PMessage digest failed to compare%0

<Missing message digest%0

TAddress is allocated to this server%0

dAddress is allocated to the partner server%0

8Reject Reason Unknown%0

�Packet dropped because of Client ID hash mismatch or standby server.%0

%0

�IP address range of scope %1 is %2 percent full with only %3 IP addresses available.

�SuperScope, %1, is %2 percent full with only %3 IP addresses remaining. This superscope has the following scopes %4 

DDHCPv6 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.

�Renew, rebind or confirm received for IPv6 addresses %1 for which there are no active lease available

�DHCPv6 service received the unknown option %1, with a length of %2. The raw option data is given below.

�There are no IPv6 addresses available to lease in the scope serving the network with Prefix %1.

hThe DHCPv6 client, %2, declined the address %1.

�DHCPv6 Scope serving the network with prefix %1, is %2 percent full with only %3 IP addresses remaining.

|A DHCPV6 client %1 has been deleted from DHCPV6 database.

�A DHCPV6 message that was in the queue for more than 30 seconds has been dropped because it is too old to process.

`An invalid DHCPV6 message has been dropped.

�A DHCPV6 message that was not meant for this server has been dropped.

DHCV6 message has been dropped because it was received on a Uni-cast address and unicast support is disabled on the server.

�DHCPV6 audit log file cannot be appended, Error Code returned %1.

�A DHCPV6 message has been dropped because the server is not authorized to process the message.

�The DHCPv6 service failed to initialize the audit log. The following error occurred: %n%1

�DHCPv6 audit log file could not be backed up.  Error code %1

�AThe DHCPv6 service was unable to access path specified for the audit log.

�The DHCPv6 service failed to initialize Winsock startup. The following error occurred %1.

�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.

,The DHCPv6 Server failed to receive a notification of interface list changes.  Some of the interfaces will not be enabled in the DHCPv6 service.

�The DHCPv6 service failed to initialize its configuration parameters. The following error occurred: %n%1.

,This computer has at least one dynamically assigned IPv6 address.For reliable DHCPv6 server operation, you should use only static IPv6 addresses.

�DHCPv6 service failed to initialize the database. The following error occurred: %n%1.

|The DHCPv6 service has initialized and is ready to serve.

dDHCPv6 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.

HERROR_LAST_DHCPV6_SERVER_ERROR

lThe 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.

,DHCPV6 Solicit%0

0DHCPV6 Advertise%0

,DHCPV6 Request%0

,DHCPV6 Confirm%0

(DHCPV6 Renew%0

(DHCPV6 Rebind%0

,DHCPV6 Decline%0

,DHCPV6 Release%0

DDHCPV6 Information Request%0

0DHCPV6 Scope Full%0

,DHCPV6 Started%0

,DHCPV6 Stopped%0

<DHCPV6 Audit Log Paused%0

4DHCPV6 dhcpsrv.log%0

4DHCPV6 Bad Address%0

PDHCPV6 address is already in use%0

8DHCPV6 client Deleted%0

HDHCPV6 DNS record not deleted%0

,DHCPV6 Expired%0

|DHCPV6 %%I64d leases expired and %%I64d leases deleted%0

HDHCPV6 Database Cleanup Begin%0

DDHCPV6 Database Cleanup End%0

<DNS IPv6 Update Request%0

<DNS IPv6 Update Failed%0

DDNS IPv6 Update Successful%0

h%%I64d DHCPV6 Stateless client records purged%0

�DHCPv6 stateless client record is purged as the purge interval has expired for this client record%0

xDHCPV6 Information Request from IPV6 Stateless Client%0

%0

�The DHCPV6 service is not authorized in the directory service domain "%2" (Server IP Address %1)

�The DHCPV6 service is authorized in the directory service domain "%2" (Server IP Address %1)

�The DHCPV6 service has not determined if it is authorized in directory domain "%2" (Server IP Address %1)

|The DHCP server initialization parameters are incorrect.

�The DHCP server was unable to open the DHCP client database.

tThe DHCP server was unable to start as an RPC server.

�The DHCP server was unable to establish a socket connection.

TThe specified subnet already exists.

TThe specified subnet does not exist.

�The primary host information for the specified subnet was not found.

�The specified DHCP element cannot be removed because it has been used.

TThe specified option already exists.

TThe specified option does not exist.

XThe specified address is not available.

XThe specified IP address range is full.

An error occurred while accessing the DHCP database. Look at the DHCP server event log for more information on this error.

tThe specified client already exists in the database.

tThe DHCP server received a message that is not valid.

�The DHCP server received a message from a client that is not valid.

PThe DHCP server service is paused.

pThe specified DHCP client is not a reserved client.

hThe specified DHCP client is a reserved client.

dThe specified IP address range is too small.

hThe specified IP address range already exists.

�The specified IP address or hardware address is being used by another client.

�The specified range either overlaps an existing range or is not valid.

|The specified range is an extension of an existing range.

�The range extension specified is too small.  The range must be extended by multiples of 32 addresses.

�The range was extended less than the specified backward extension. Extend the range by multiples of 32 addresses.

�DHCP database needs to be upgraded to a newer format.  Look at the DHCP server event log for more information.

�The format of the bootstrap protocol file table is incorrect. The correct format is: <requested boot file name1>,<boot file server name1>,<boot file name1> <requested boot file name2>,<boot file server name2>,<boot file name2> etc...

PERROR_SERVER_UNKNOWN_BOOT_FILE_NAME

`The specified superscope name is too long.

PThis IP address is already in use.

\The DHCP audit-log file path is too long.

�The DHCP service received a request for a valid IP address that is not administered by this server.

$The DHCP Server failed to receive a notification of interface list changes.  Some of the interfaces will not be enabled in the DHCP service.

The DHCP database needs to be upgraded to the current Jet format. Look at the DHCP service event log for more information.

xThe 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.

�The DHCP service is shutting down because another DHCP server with the IP address %1 is active on the network.

�The DHCP service is not servicing any clients on the network because it has determined that it is not authorized to run.

�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.

|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.

PThe DHCP service is ignoring a request from another DHCP service because it is on a different directory service enterprise (Directory Service Enterprise root = %1)

8The 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.

pThe class name being used is unknown or incorrect.

�The class name is already in use or the class information is already in use.

�The specified scope name is too long.  The name is limited to a maximum of 256 characters.

�There is already a default scope configured on the server.

xThe Dynamic BOOTP attribute cannot be turned on or off.

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.

�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.

|The bindings to internal IP addresses cannot be modified.

`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.

LThe multicast scope parameters are incorrect.  Either the scope  already exists or its properties are inconsistent with the properties of another existing scope.

�The multicast scope range must have atleast 256 IP addresses.

�The exemption parameters are incorrect.  The exemption already exists.

�The exemption parameters are incorrect.  The specified exemption does not exist.

�Incorrect Parameter. Acceptable values are between 600 and 4294967295.

%1 %3

%1 %3

%1 %3

%1 %3

%1 %3

%1 %3

%1 %3

%1 %3

%1 %3

%1 %3

0Scavenger started.

,Scavenger ended.

tThe DHCP service could not contact Active Directory.

�The DHCP service root could not be found in the Active Directory.

�An unexpected error occurred while accessing the Active Directory.

XThere were too many errors to proceed.

PA DHCP service could not be found.

�The specified options are already present in the directory service.

�The specified options are not present in the directory service.

�The specified classes already exist in the directory service.

�The specified classes do not exist in the directory service.

�The specified servers are already present in the directory service.

�The specified servers are not present in the directory service.

�The specified server address does not belong to the identified server name.

�The specified subnets already exist in the directory service.

xThe specified subnet belongs to a different superscope.

�The specified subnet is not present in the directory service.

�The specified reservation is not present in the directory service.

�The reservation specified conflicts with an existing reservation in the directory service.

�The specified IP range conflicts with some existing IP range in the directory service.

�The specified IP range is not present in the directory service.

DThis class cannot be deleted.

\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.

�The given subnet prefix is invalid. It represents either a non-unicast or link local address range.

�The given delay value is invalid. The valid value is from 0 to 1000.

�Address or Address pattern is already contained in one of the list.

�Address to be added to Deny list or to be deleted from allow list, has an associated reservation.

�Address or Address pattern is not contained in either list.

|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.

TThis Hardware Type is already exempt.

�You are trying to delete an undefined Hardware Type. To define/add a Hardware Type, use 'add filterexemption'.

�Conflict in types for the same option on Host and Added DHCP Servers.

hThe parent expression specified does not exist.

TThe DHCP server policy already exists

�The DHCP server policy range specified already exists in the given scope.

�The DHCP server policy range specified is invalid or does not match the given subnet.

�DHCP server policy ranges can only be added to scope level policies.

xThe DHCP server policy contains an invalid expression.

�The processing order specified for the DHCP server policy is invalid.

TThe DHCP server policy was not found.

(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.

tThe DHCP scope is already in a failover relationship.

hThe DHCP failover relationship already exists.

hThe DHCP failover relationship does not exist.

pThe DHCP scope is not part of failover relationship

hThe DHCP failover relationship is a secondary.

PThe DHCP failover is not supported

�The DHCP servers in the failover relationship has time out of synchronization.

pThe DHCP failover relationship state is not NORMAL.

�The user does not have administrative permissions for the DHCP server

�The specified DHCP server is not reachable. Please provide a DHCP server that is reachable.

(The DHCP Server Service is not running on the specified server. Please ensure that the DHCP Server service is running on the specified computer

@Unable to resolve DNS name 

�The specified DHCP failover relationship name is too long. The name is limited to a maximum of 126 characters

�The specified DHCP Server has reached the end of the selected range while finding the free IP address

�The synchronization of leases in the scopes being added to the failover relationship  failed.

�The relationship cannot be created on the DHCP server as the maximum number of allowed relationship has exceeded.

0A 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.

4Number 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.

�A scope supporting BOOTP clients cannot be added to a failover relationship.

xAn 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.

�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.

8A scope configured for failover has settings that are not supported if one of the servers in the failover relationship is running Windows Server 2012.

IP Address range cannot be defined for the DHCP server policy because it has fully qualified domain name based conditions.

�Option values cannot be defined for the DHCP server policy  because it has fully qualified domain name based conditions.

�Fully qualified domain name based conditions cannot be used in a policy with configured options or IP address ranges.

|Network Access Protection is not supported by the server.

DERROR_LAST_DHCP_SERVER_ERROR

�Address allocation triggered for the failover relationship %1.

dScavenger started purging stateless entries.

dScavenger finished purging stateless entries.

dThe total leases deleted in scavenger are %1

Scope %1 which was part of failover relationship %2 was not found in DHCP server database. Please restore the DHCP server database.

Classic

(CreateFailover

(DeleteFailover

,AddFailoverScope

0RemoveFailoverScope

4ChangeFailoverConfig

0FailoverStateChange

$TimeOutOfSync

CommUp

CommDown

(BINDING-UPDATE

 BINDING-ACK

CONNECT

 CONNECT-ACK

0UPDATE-REQUEST-ALL

(UPDATE-REQUEST

 UPDATE-DONE

STATE

CONTACT

4MessageAuthentication

0InitializeFailover

8FailoverIPPoolTakeover

Error

Warning

 Information

$DHCP Failover

Policy

0Name Registration.

0Name Registration.

lMicrosoft-Windows-DHCP Server Events/Operational

|Microsoft-Windows-DHCP Server Events/FilterNotifications

`Microsoft-Windows-DHCP Server Events/Admin

hMicrosoft-Windows-DHCP Server Events/AuditLogs

hMicrosoft-Windows-DHCP Server Events/DebugLogs

System

XScope: %1 for IPv4 is Configured by %2.

TScope: %1 for IPv4 is Modified by %2.

TScope: %1 for IPv4 is Deleted by %2.

XScope: %1 for IPv4 is Activated by %2.

\Scope: %1 for IPv4 is DeActivated by %2.

Scope: %1 for IPv4 is Updated with Lease Duration: %2 seconds by %3. The previous configured Lease Duration was: %4 seconds.

�Scope: %1 for IPv4 is Updated with Option Settings: %2 by %3

�Scope: %1 for IPv4 is Enabled for DNS Dynamic updates by %2.

�Scope: %1 for IPv4 is Disabled for DNS Dynamic updates by %2.

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 .

�Scope: %1 for IPv4 is Updated with DNS Settings by %2: to always dynamically update DNS A and PTR records.

�Scope: %1 for IPv4 is Enabled for DNS Settings by %2: to discard DNS A and PTR records when lease is deleted.

�Scope: %1 for IPv4 is Disabled for DNS Settings by %2: to discard DNS A and PTR records when lease is deleted.

(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.

,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.

xPolicy based assignment has been disabled for scope %1.

xPolicy based assignment has been enabled for scope %1.

�Name Protection setting is Enabled on Scope: %1 for IPv4 by %2.

�Name Protection setting is Disabled on Scope: %1 for IPv4 by %2.

�Scope: %1 for IPv4 is Updated with support type: %2 by %3. The previous configured state was: %4.

xNAP Enforcement is Enabled on Scope: %1 for IPv4 by %2.

|NAP Enforcement is Disabled on Scope: %1 for IPv4 by %2.

�NAP Profile is configured on Scope: %1  for IPv4 with the following NAP Profile: %2 by %3.

NAP Profile is Updated on Scope: %1 for IPv4 with the following NAP Profile: %2 by %3. The previous configured NAP Profile was: %4.

�The following NAP Profile: %1 is deleted on Scope: %2 by %3.

lScope: %1 for Multicast IPv4 is Configured by %2.

hScope: %1 for Multicast IPv4 is Deleted by %2.

tScope: %1 for IPv4 is Added in Superscope: %2 by %3.

dSuperScope: %1 for IPv4 is Configured by %2.

\SuperScope: %1 for IPv4 is Deleted by %2.

�Scope: %1 within SuperScope: %2 for IPv4 is Activated by %3.

�Scope: %1 within SuperScope: %2 for IPv4 is DeActivated by %3.

�Scope: %1 for IPv4 is Removed in Superscope: %2 by %3. However, the Scope exists outside the Superscope.

�Scope: %1 for IPv4 is Deleted in Superscope: %2 as well as Deleted permanently by %3.

dDelay 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.

xServer level option %1 for IPv4 has been updated by %2.

�Reservation: %1 for IPv4 is Configured under Scope %2 by %3.

|Reservation: %1 for IPv4 is Deleted under Scope %2 by %3.

�Reservation: %1 for IPv4 under Scope: %2 is Enabled for DNS Dynamic updates by %3.

�Reservation: %1 for IPv4 under Scope: %2 is Disabled for DNS Dynamic updates by %3.

<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.

Reservation: %1 for IPv4 under Scope: %2 is Updated with DNS Settings by %3: to always dynamically update DNS A and PTR records.

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.

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.

TReservation: %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.

XReservation: %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.

�Reservation: %1 for IPv4 under Scope: %2 is Updated with Option Setting: %3 by %4.

�Policy based assignment has been disabled at server level.

|Policy based assignment has been enabled at server level.

�Added exclusion IP Address range %1 in the Address Pool for IPv4 under Scope: %2 by %3.

�Deleted exclusion IP Address range %1 in the Address Pool for IPv4 under Scope: %2 by %3.

�Link Layer based filtering is Enabled in the Allow List of the IPv4 by %1 

�Link Layer based filtering is Disabled in the Allow List of the IPv4 by %1 

�Filter for physical address: %1, hardware type: %3 added to the IPv4 Allow List by %2. 

�Filter for physical address: %1, hardware type: %3 removed from the IPv4 Allow List by %2. 

�Link Layer based filtering is Enabled in the Deny List of the IPv4 by %1 

�Link Layer based filtering is Disabled in the Deny List of the IPv4 by %1 

�Filter for physical address: %1, hardware type: %3 added to the IPv4 Deny List by %2. 

�Filter for physical address: %1, hardware type: %3 removed from the IPv4 Deny List by %2. 

XScope: %1 for IPv6 is Configured by %2.

TScope: %1 for IPv6 is Deleted by %2.

XScope: %1 for IPv6 is Activated by %2.

\Scope: %1 for IPv6 is DeActivated by %2.

Scope: %1 for IPv6 is Updated with Lease Preferred Lifetime:  %2 by %3. The previous configured Lease Preferred Lifetime was: %4.

�Scope: %1 for IPv6 is Updated with Lease Valid Lifetime: %2 by %3. The previous configured Lease Valid Lifetime was: %4.

�Scope: %1 for IPv6 is Updated with Option Setting: %2 by %3.

�Scope: %1 for IPv6 is Enabled for DNS Dynamic updates by %2.

�Scope: %1 for IPv6 is Disabled for DNS Dynamic updates by %2.

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.

�Scope: %1 for IPv6 is Updated with DNS Settings by %2: to always dynamically update DNS AAAA and PTR records.

�Scope: %1 for IPv6 is Enabled for DNS Settings by %2: to discard DNS AAAA and PTR records when lease is deleted.

�Scope: %1 for IPv6 is Disabled for DNS Settings by %2: to discard DNS AAAA and PTR records when lease is deleted.

�Name Protection setting is Enabled on Scope: %1 for IPv6 by %2.

�Name Protection setting is Disabled on Scope: %1 for IPv6 by %2.

�Reservation: %1 for IPv6 is Configured under Scope %2 by %3.

|Reservation: %1 for IPv6 is Deleted under Scope %2 by %3.

�Reservation: %1 for IPv6 under Scope: %2 is Enabled for DNS Dynamic updates by %3.

�Reservation: %1 for IPv6 under Scope: %2 is Disabled for DNS Dynamic updates by %3.

DReservation: %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.

Reservation: %1 for IPv6 under Scope: %2 is Updated with DNS Settings by %3: to always dynamically update DNS AAAA and PTR records.

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.

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.

�Reservation: %1 for IPv6 under Scope: %2 is Updated with Option Setting: %3 by %4.

�Added exclusion IP Address range %1 in the Address Pool for IPv6 under Scope: %2 by %3.

�Deleted exclusion IP Address range %1 in the Address Pool for IPv6 under Scope: %2 by %3.

TScope: %1 for IPv6 is Modified by %2.

�DHCPv6 Stateless client inventory has been enabled for the scope %1.

�DHCPv6 Stateless client inventory has been disabled for the scope %1.

�DHCPv6 Stateless client inventory has been enabled for the server.

�DHCPv6 Stateless client inventory has been disabled for the server.

�Purge time interval for DHCPv6 stateless client inventory for scope %1 has been set to %2 hours.

�Purge time interval for DHCPv6 stateless client inventory for server has been set to %1 hours.

�Scope: %1 for IPv4 is Enabled for DNS Settings by %2: to disable dynamic updates for DNS PTR records.

�Scope: %1 for IPv4 is Disabled for DNS Settings by %2: to disable dynamic updates for DNS PTR records.

xServer level option %1 for IPv6 has been updated by %2.

xServer level option %1 for IPv4 has been removed by %2.

�Option setting: %2 has been removed from IPv4 scope: %1 by %3.

�Option setting: %3 has been removed from the reservation: %1 in IPv4 scope: %2 by %4.

xServer level option %1 for IPv6 has been removed by %2.

�Option setting: %2 has been removed from IPv6 scope: %1 by %3.

�Option setting: %3 has been removed from the reservation: %1 in IPv6 scope: %2 by %4.

0DHCP 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.

@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.

DDHCP 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.

TDHCP 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.

@Policy %2 for server is %1.

DPolicy %2 for scope %3 is %1.

�The conditions for server policy %3 have been set to %1. The conditions are grouped by logical operator %2.

�The conditions for scope %4 policy %3 have been set to %1. The conditions are grouped by logical operator %2.

�A new server wide IPv4 policy %1 was created. The processing order of the policy is %2.

�A new scope policy %1 was created in scope %3. The processing order of the policy is %2.

PPolicy %1 was deleted from server.

TPolicy %1 was deleted from scope %2.

�The IP address range from %1 was set for the scope %3 policy %2.

�The IP address range from %1 was removed from the scope %3 policy %2.

�The value %2 was set for the option %1 for the server policy %3.

�The value %2 was set for the option %1 for the scope %4 policy %3.

�The value %2 was removed from the option %1 for the server policy %3.

�The value %2 was removed from the option %1 for the scope %4 policy %3.

\Server policy %2 has been renamed to %1.

`Scope %3 policy %2 has been renamed to %1.

hDescription of server policy %2 was set to %1.

lDescription of scope %3 policy %2 was set to %1.

�Processing order of server policy %3 was changed to %1 from %2.

�Processing order of scope %4 policy %3 was changed to %1 from %2.

 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.

TA 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.

�Failover relationship %1 between %2 and %3 has been deleted.

�Scope %1 has been added to the failover relationship %2 with server %3.

�Scope %1 has been removed from the failover relationship %2 with server %3.

The failover configuration parameter MCLT for failover relationship %1 with server %2 has been changed from %3 seconds to %4 seconds.

@The failover configuration parameter auto switch over interval for failover relationship %1 with server %2 has been changed from %3 seconds to %4 seconds.

 The failover configuration parameter reserve address percentage for failover relationship %1 with server %2 has been changed from %3 to %4.

8The failover configuration parameter load balance percentage for failover relationship %1 with server %2 has been changed from %3 to %4 on this server.

The failover configuration parameter mode for failover relationship %1 with server %2 has been changed from hot standby to load balance.

The failover configuration parameter mode for failover relationship %1 with server %2 has been changed from load balance to hot standby.

�The failover state of server: %1 for failover relationship: %2 changed from: %3 to %4.

�The failover state of server: %1 for failover relationship: %2 changed from: %3 to %4.

@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 .

�Server has established contact with failover partner server %1 for relationship %2 .

�Server has lost contact with failover partner server  %1 for relationship %2 .

 Failover protocol message BINDING-UPDATE from server %1 for failover relationship %2 was rejected because message digest failed to compare.

$Failover protocol message  BINDING-UPDATE from server %1 for failover relationship %2 was rejected because message digest was not configured.

Failover protocol message  BINDING-UPDATE from server %1 for failover relationship %2 is rejected because message digest was not present.

�The failover state of server: %1 for failover relationship: %2 changed to : %3.

�The failover state of server: %1 for failover relationship: %2 changed to: %3.

Failover protocol message BINDING-ACK from server %1 for failover relationship %2 was rejected because message digest failed to compare.

 Failover protocol message  BINDING-ACK from server %1 for failover relationship %2 was rejected because message digest was not configured.

Failover protocol message  BINDING-ACK from server %1 for failover relationship %2 is rejected because message digest was not present.

Failover protocol message CONNECT from server %1 for failover relationship %2 was rejected because message digest failed to compare.

Failover protocol message  CONNECT from server %1 for failover relationship %2 was rejected because message digest was not configured.

Failover protocol message  CONNECT from server %1 for failover relationship %2 is rejected because message digest was not present.

Failover protocol message CONNECTACK from server %1 for failover relationship %2 was rejected because message digest failed to compare.

Failover protocol message  CONNECTACK from server %1 for failover relationship %2 was rejected because message digest was not configured.

Failover protocol message  CONNECTACK from server %1 for failover relationship %2 is rejected because message digest was not present.

Failover protocol message UPDREQALL from server %1 for failover relationship %2 was rejected because message digest failed to compare.

Failover protocol message  UPDREQALL from server %1 for failover relationship %2 was rejected because message digest was not configured.

Failover protocol message  UPDREQALL from server %1 for failover relationship %2 is rejected because message digest was not present.

Failover protocol message UPDDONE from server %1 for failover relationship %2 was rejected because message digest failed to compare.

Failover protocol message  UPDDONE from server %1 for failover relationship %2 was rejected because message digest was not configured.

Failover protocol message  UPDDONE from server %1 for failover relationship %2 is rejected because message digest was not present.

Failover protocol message UPDREQ from server %1 for failover relationship %2 was rejected because message digest failed to compare.

Failover protocol message  UPDREQ from server %1 for failover relationship %2 was rejected because message digest was not configured.

Failover protocol message  UPDREQ from server %1 for failover relationship %2 is rejected because message digest was not present.

Failover protocol message STATE from server %1 for failover relationship %2 was rejected because message digest failed to compare.

Failover protocol message  STATE from server %1 for failover relationship %2 was rejected because message digest was not configured.

Failover protocol message  STATE from server %1 for failover relationship %2 is rejected because message digest was not present.

Failover protocol message CONTACT from server %1 for failover relationship %2 was rejected because message digest failed to compare.

Failover protocol message  CONTACT from server %1 for failover relationship %2 was rejected because message digest was not configured.

Failover protocol message  CONTACT from server %1 for failover relationship %2 is rejected because message digest was not present.

�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.

HBINDING 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.

�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.

4This 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.

<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.

HA 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.

8A 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.

HA 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.

�A UPDREQ message with transaction id: %1 was sent to partner server: %2 for failover relationship: %3.

�A UPDREQ message with transaction id: %1 was received from partner server: %2 for failover relationship: %3

�A UPDDONE message with transaction id: %1 was sent to partner server: %2 for failover relationship: %3.

�A UPDDONE message with transaction id: %1 was received from partner server: %2 for failover relationship: %3.

�A UPDREQALL message with transaction id: %1 was sent to partner server: %2 for failover relationship: %3

�A UPDREQALL message with transaction id: %1 was received from partner server: %2 for failover relationship: %3

�A CONTACT message with transaction id: %1 was sent to partner server: %2 for failover relationship: %3.

�A CONTACT message with transaction id: %1 was received from partner server: %2 for failover relationship: %3.

�A CONNECT message with transaction id: %1 was sent to partner server: %2 for failover relationship: %3.

�A CONNECT message with transaction id: %1 was received from partner server: %2 for failover relationship: %3.

,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.

4A 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.

�A CONNECTACK message with transaction id %1 was sent to partner server : %2  for failover relationship: %3.

�A CONNECTACK message with transaction id %1 was received from partner server : %2  for failover relationship: %3.

A BINDING-ACK message with transaction id: %1 was sent for IP address: %2  to partner server: %3 for failover relationship: %4.

A BINDING-ACK message with transaction id: %1 was received for IP address: %2 from partner server: %3 for failover relationship: %4.

A CONNECTACK message with transaction id %1 was sent to partner server : %2  for failover relationship: %3 with reject reason: %4.

A CONNECTACK message with transaction id %1 was received from partner server : %2  for failover relationship: %3 with reject reason: %4.

�The shared secret for failover relationship %2 with server %1 has been changed.

�Message authentication for failover relationship %2 with server %1 has been enabled.

�Message authentication for failover relationship %2 with server %1 has been disabled.

%1

hDNSSuffix of scope %3 policy %2 was set to %1.

dDNSSuffix of server policy %2 was set to %1.

|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.

�Forward record registration for IPv4 address %1 and FQDN %2 failed with error %3.

�Forward record registration for IPv4 address %1 and FQDN %2 failed with error %3 (%4).

tPTR 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.

�PTR record registration for IPv4 address %1 and FQDN %2 failed with error %3.

�PTR record registration for IPv4 address %1 and FQDN %2 failed with error %3 (%4).

|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.

�Forward record registration for IPv6 address %1 and FQDN %2 failed with error %3.

�Forward record registration for IPv6 address %1 and FQDN %2 failed with error %3 (%4).

tPTR 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.

�PTR record registration for IPv6 address %1 and FQDN %2 failed with error %3.

�PTR record registration for IPv6 address %1 and FQDN %2 failed with error %3 (%4).

�4VS_VERSION_INFO��
cE
cE?�StringFileInfo�040904B0LCompanyNameMicrosoft CorporationZFileDescriptionDHCP Server API Stub DLLh$FileVersion10.0.17763.1 (WinBuild.160101.0800):
InternalNamedhcpsapi.dll�.LegalCopyright� Microsoft Corporation. All rights reserved.JOriginalFilenamedhcpsapi.dll.muij%ProductNameMicrosoft� Windows� Operating System>
ProductVersion10.0.17763.1DVarFileInfo$Translation	�PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGX

Youez - 2016 - github.com/yon3zu
LinuXploit