MZ@ !L!This program cannot be run in DOS mode. $Rؕ3}3}3}H̴3}H̱3}Rich3}PEL!  :PQ@9.rsrc@:@@( @Xp   4TFMUIŪX_ jͦdWԷH؛Ψ MUI en-US6;BG4 IK@ OO SS X`T bcex $&'H6P??  A  B  G! " H$ ' HI/ / J2 2 K4 5 lK: : LB G dLI O (OQ Q TQU U QW X $R` e S~ $U |W W 4\ ` ,a c l2 Q ld { 8z  P p X @ H * d0 < D E N P X _ b j pl r v ~ <    ! H!H L "N ] $ , (/ @2 x6 :LM ;RR<VWL<[`<bc?hiX@kkAmoB~0D$F$IKKMTNU[X[^e<>eABlfFPf\\k_aloqTmxydn{{o}o3q58:X$bvtԎ<l'*3T5;WbfxLztȱ\B !22,7:Hd@,hld |@ dD, T \The workstation driver is not installed. LThe server could not be located. An internal error occurred. The network cannot access a shared memory segment. XA network resource shortage occurred . lThis operation is not supported on workstations. DThe device is not connected. PThe Server service is not started. 0The queue is empty. XThe device or directory does not exist. pThe operation is invalid on a redirected resource. LThe name has already been shared. xThe server is currently out of the requested resource. |Requested addition of items exceeds the maximum allowed. xThe Peer service supports only two simultaneous users. PThe API return buffer is too small. DA remote API error occurred. An error occurred when opening or reading the configuration file. LA general network error occurred. The Workstation service is in an inconsistent state. Restart the computer before restarting the Workstation service. dThe Workstation service has not been started. `The requested information is not available. PAn internal Windows error occurred. hThe server is not configured for transactions. |The requested API is not supported on the remote server. @The event name is invalid. The computer name already exists on the network. Change it and restart the computer. The specified component could not be found in the configuration information. The specified parameter could not be found in the configuration information. dA line in the configuration file is too long. @The printer does not exist. DThe print job does not exist. \The printer destination cannot be found. XThe printer destination already exists. LThe printer queue already exists. HNo more printers can be added. LNo more print jobs can be added. `No more printer destinations can be added. This printer destination is idle and cannot accept control operations. This printer destination request contains an invalid control function. XThe print processor is not responding. @The spooler is not running. This operation cannot be performed on the print destination in its current state. This operation cannot be performed on the printer queue in its current state. This operation cannot be performed on the print job in its current state. dA spooler memory allocation failure occurred. LThe device driver does not exist. xThe data type is not supported by the print processor. TThe print processor is not installed. HThe service database is locked. @The service table is full. hThe requested service has already been started. lThe service does not respond to control actions. LThe service has not been started. DThe service name is invalid. xThe service is not responding to the control function. DThe service control is busy. The configuration file contains an invalid service program name. |The service could not be controlled in its present state. DThe service ended abnormally. The requested pause, continue, or stop is not valid for this service. The service control dispatcher could not find the service name in the dispatch table. lThe service control dispatcher pipe read failed. pA thread for the new service could not be created. This workstation is already logged on to the local-area network. The workstation is not logged on to the local-area network. lThe user name or group name parameter is invalid. PThe password parameter is invalid. pThe logon processor did not add the message alias. pThe logon processor did not add the message alias. xThe logoff processor did not delete the message alias. xThe logoff processor did not delete the message alias. @Network logons are paused. dA centralized logon-server conflict occurred. pThe server is configured without a valid user path. An error occurred while loading or running the logon script. The logon server was not specified. Your computer will be logged on as STANDALONE. TThe logon server could not be found. pThere is already a logon domain for this computer. hThe logon server could not validate the logon. \The security database could not be found. PThe group name could not be found. LThe user name could not be found. TThe resource name could not be found. <The group already exists. @The account already exists. dThe resource permission list already exists. This operation is only allowed on the primary domain controller of the domain. `The security database has not been started. xThere are too many names in the user accounts database. DA disk I/O failure occurred. pThe limit of 64 entries per resource was exceeded. hDeleting a user with a session is not allowed. `The parent directory could not be located. Unable to add to the security database session cache segment. tThis operation is not allowed on this special group. This user is not cached in user accounts database session cache. XThe user already belongs to this group. XThe user does not belong to this group. HThis user account is undefined. HThis user account has expired. |The user is not allowed to log on from this workstation. hThe user is not allowed to log on at this time. XThe password of this user has expired. \The password of this user cannot change. LThis password cannot be used now. 8The password does not meet the password policy requirements. Check the minimum password length, password complexity and password history requirements. pThe password of this user is too recent to change. PThe security database is corrupted. No updates are necessary to this replicant network/local security database. This replicant database is outdated; synchronization is required. `The network connection could not be found. <This asg_type is invalid. XThis device is currently being shared. hThe user name may not be same as computer name. The computer name could not be added as a message alias. The name may already exist on the network. \The Messenger service is already started. XThe Messenger service failed to start. tThe message alias could not be found on the network. hThis message alias has already been forwarded. |This message alias has been added but is still forwarded. `This message alias already exists locally. The maximum number of added message aliases has been exceeded. XThe computer name could not be deleted. Messages cannot be forwarded back to the same workstation. pAn error occurred in the domain message processor. The message was sent, but the recipient has paused the Messenger service. XThe message was sent but not received. xThe message alias is currently in use. Try again later. `The Messenger service has not been started. XThe name is not on the local computer. The forwarded message alias could not be found on the network. xThe message alias table on the remote station is full. Messages for this alias are not currently being forwarded. TThe broadcast message was truncated. HThis is an invalid device name. 8A write fault occurred. lA duplicate message alias exists on the network. \This message alias will be deleted later. The message alias was not successfully deleted from all networks. This operation is not supported on computers with multiple networks. TThis shared resource does not exist. @This device is not shared. lA session does not exist with that computer name. There is not an open file with that identification number. A failure occurred when executing a remote administration command. |A failure occurred when opening a remote temporary file. The data returned from a remote administration command has been truncated to 64K. This device cannot be shared as both a spooled and a non-spooled resource. |The information in the list of servers may be incorrect. `The computer is not active in this domain. The share must be removed from the Distributed File System before it can be deleted. \The operation is invalid for this device. DThis device cannot be shared. <This device was not open. LThis device name list is invalid. HThe queue priority is invalid. `There are no shared communication devices. XThe queue you specified does not exist. LThis list of devices is invalid. LThe requested device is invalid. dThis device is already in use by the spooler. |This device is already in use as a communication device. HThis computer name is invalid. dThe string and prefix specified are too long. HThis path component is invalid. XCould not determine the type of input. XThe buffer for types is not big enough. LProfile files cannot exceed 64K. LThe start offset is out of range. The system cannot delete current connections to network resources. The system was unable to parse the command line in this file. lAn error occurred while loading the profile file. Errors occurred while saving the profile file. The profile was partially saved. 4Log file %1 is full. \This log file has changed between reads. 8Log file %1 is corrupt. XThe source path cannot be a directory. @The source path is illegal. LThe destination path is illegal. The source and destination paths are on different servers. XThe Run server you requested is paused. xAn error occurred when communicating with a Run server. tAn error occurred when starting a background process. The shared resource you are connected to could not be found. PThe LAN adapter number is invalid. XThere are open files on the connection. HActive connections still exist. XThis share name or password is invalid. pThe device is being accessed by an active process. PThe drive letter is in use locally. The specified client is already registered for the specified event. <The alert table is full. lAn invalid or nonexistent alert name was raised. HThe alert recipient is invalid. A user's session with this server has been deleted because the user's logon hours are no longer valid. The log file does not contain the requested record number. xThe user accounts database is not configured correctly. This operation is not permitted when the Netlogon service is running. This operation is not allowed on the last administrative account. lCould not find domain controller for this domain. hCould not set logon information for this user. `The Netlogon service has not been started. dUnable to add to the user accounts database. This server's clock is not synchronized with the primary domain controller's clock. XA password mismatch has been detected. The server identification does not specify a valid server. The session identification does not specify a valid session. The connection identification does not specify a valid connection. There is no space for another entry in the table of available servers. The server has reached the maximum number of sessions it supports. The server has reached the maximum number of connections it supports. The server cannot open more files because it has reached its maximum number. |There are no alternate servers registered on this server. Try down-level (remote admin protocol) version of API instead. |The UPS driver could not be accessed by the UPS service. dThe UPS service is not configured correctly. |The UPS service could not access the specified Comm Port. The UPS indicated a line fail or low battery situation. Service not started. tThe UPS service failed to perform a system shut down. lThe program below returned an MS-DOS error code: TThe program below needs more memory: |The program below called an unsupported MS-DOS function: HThe workstation failed to boot. @The file below is corrupt. |No loader is specified in the boot-block definition file. NetBIOS returned an error: The NCB and SMB are dumped above. @A disk I/O error occurred. TImage parameter substitution failed. xToo many image parameters cross disk sector boundaries. The image was not generated from an MS-DOS diskette formatted with /S. TRemote boot will be restarted later. \The call to the Remoteboot server failed. \Cannot connect to the Remoteboot server. lCannot open image file on the Remoteboot server. XConnecting to the Remoteboot server... XConnecting to the Remoteboot server... Remote boot service was stopped; check the error log for the cause of the problem. Remote boot startup failed; check the error log for the cause of the problem. A second connection to a Remoteboot resource is not allowed. The browser service was configured with MaintainServerList=No. Service failed to start since none of the network adapters started with this service. Service failed to start due to bad startup information in the registry. Service failed to start because its database is absent or corrupt. |Service failed to start because RPLFILES share is absent. |Service failed to start because RPLUSER group is absent. LCannot enumerate service records. pWorkstation record information has been corrupted. LWorkstation record was not found. tWorkstation name is in use by some other workstation. hProfile record information has been corrupted. DProfile record was not found. dProfile name is in use by some other profile. `There are workstations using this profile. tConfiguration record information has been corrupted. PConfiguration record was not found. lAdapter id record information has been corrupted. XAn internal service error has occurred. lVendor id record information has been corrupted. lBoot block record information has been corrupted. |The user account for this workstation record is missing. `The RPLUSER local group could not be found. LBoot block record was not found. tChosen profile is incompatible with this workstation. Chosen network adapter id is in use by some other workstation. dThere are profiles using this configuration. There are workstations, profiles or configurations using this boot block. dService failed to backup Remoteboot database. DAdapter record was not found. DVendor record was not found. pVendor name is in use by some other vendor record. (boot name, vendor id) is in use by some other boot block record. |Configuration name is in use by some other configuration. The internal database maintained by the DFS service is corrupt One of the records in the internal DFS database is corrupt There is no DFS name whose entry path matches the input Entry Path lA root or link with the given name already exists xThe server share specified is already shared in the DFS The indicated server share does not support the indicated DFS namespace The operation is not valid on this portion of the namespace The operation is not valid on this portion of the namespace The operation is ambiguous because the link has multiple servers 8Unable to create a link @The server is not DFS Aware `The specified rename target path is invalid LThe specified DFS link is offline pThe specified server is not a server for this link TA cycle in the DFS name was detected tThe operation is not supported on a server-based DFS This link is already supported by the specified server-share Can't remove the last server-share supporting this root or link tThe operation is not supported for an Inter-DFS link The internal state of the DFS Service has become inconsistent The DFS Service has been installed on the specified server `The DFS data being reconciled is identical The DFS root cannot be deleted - Uninstall DFS if required A child or parent directory of the share is already in a DFS 0DFS internal error `This machine is already joined to a domain. lThis machine is not currently joined to a domain. This machine is a domain controller and cannot be unjoined from a domain. The destination domain controller does not support creating machine accounts in OUs. \The specified workgroup name is invalid. The specified computer name is incompatible with the default language used on the domain controller. The specified computer account could not be found. Contact an administrator to verify the account is in the domain. If the account has been deleted unjoin, reboot, and rejoin the domain. tThis version of Windows cannot be joined to a domain. ,An attempt to resolve the DNS name of a domain controller in the domain being joined has failed. Please verify this client is configured to reach a DNS server that can resolve DNS names in the target domain. For information about network troubleshooting, see Windows Help. PPassword must change at next logon 4Account is locked out 4Password is too long `Password doesn't meet the complexity policy Password doesn't meet the requirements of the filter dll's pOffline join completion information was not found. lThe offline join completion information was bad. Unable to create offline join information. Please ensure you have access to the specified path location and permissions to modify its contents. Running as an elevated administrator may be required. xThe domain join info being saved was incomplete or bad. Offline join operation successfully completed but a restart is needed. dThere was no offline join operation pending. Unable to set one or more requested machine or domain name values on the local computer. Could not verify the current machine's hostname against the saved value in the join completion information. Unable to load the specified offline registry hive. Please ensure you have access to the specified path location and permissions to modify its contents. Running as an elevated administrator may be required. The minimum session security requirements for this operation were not met. Computer account provisioning blob version is not supported. 8The specified domain controller does not meet the version requirement for this operation. Please select a domain controller capable of issuing claims. This operation requires a domain controller which supports LDAP. Please select an LDAP-capable domain controller. hA domain controller which meets the version requirement for this operation could not be located. Please ensure that a domain controller capable of issuing claims is available. The Windows version of the specified image does not support provisioning. tThe machine name is blocked from joining the domain. 8The domain controller does not meet the version requirement for this operation. See http://go.microsoft.com/fwlink/?LinkId=294288 for more information. An account with the same name exists in Active Directory. Re-using the account was blocked by security policy. TThis is the last error in NERR range. Drive %1 is nearly full. %2 bytes are available. Please warn users and delete unneeded files. %1 errors were logged in the last %2 minutes. Please review the server's error log. ,%1 network errors occurred in the last %2 minutes. Please review the server's error log. The server and/or network hardware may need service. There were %1 bad password attempts in the last %2 minutes. Please review the server's audit trail. There were %1 access-denied errors in the last %2 minutes. Please review the server's audit trail. The error log is full. No errors will be logged until the file is cleared or the limit is raised. @The error log is 80%% full. The audit log is full. No audit entries will be logged until the file is cleared or the limit is raised. @The audit log is 80%% full. An error occurred closing file %1. Please check the file to make sure it is not corrupted. LThe administrator has closed %1. There were %1 access-denied errors in the last %2 minutes. A power failure was detected at %1. The server has been paused. Power has been restored at %1. The server is no longer paused. The UPS service is starting shut down at %1 due to low battery. There is a problem with a configuration of user specified shut down command file. The UPS service started anyway. A defective sector on drive %1 has been replaced (hotfixed). No data was lost. You should run CHKDSK soon to restore full performance and replenish the volume's spare sector pool. The hotfix occurred while processing a remote request. A disk error occurred on the HPFS volume in drive %1. The error occurred while processing a remote request. The user accounts database (NET.ACC) is corrupted. The local security system is replacing the corrupted NET.ACC with the backup made on %1 at %2. Any updates made to the database after this time are lost. The user accounts database (NET.ACC) is missing. The local security system is restoring the backup database made on %1 at %2. Any updates made to the database after this time are lost. xLocal security could not be started because the user accounts database (NET.ACC) was missing or corrupted, and no usable backup database was present. THE SYSTEM IS NOT SECURE. The server cannot export directory %1, to client %2. It is exported from another server. The replication server could not update directory %2 from the source on %3 due to error %1. Master %1 did not send an update notice for directory %2 at the expected time. |User %1 has exceeded account limitation %2 on server %3. pThe primary domain controller for domain %1 failed. Failed to authenticate with %2, a Windows NT or Windows 2000 Domain Controller for domain %1. The replicator attempted to log on at %2 as %1 and failed. 0@I *LOGON HOURS %0 Replicator could not access %2 on %3 due to system error %1. Replicator limit for files in a directory has been exceeded. pReplicator limit for tree depth has been exceeded. The replicator cannot update directory %1. It has tree integrity and is the current directory for some process. @Network error %1 occurred. <System error %1 occurred. Cannot log on. User is currently logged on and argument TRYUSER is set to NO. HIMPORT path %1 cannot be found. HEXPORT path %1 cannot be found. dReplicated data has changed in directory %1. Replicator failed to update signal file in directory %2 due to %1 system error. The Registry or the information you just typed includes an illegal value for "%1". The required parameter was not provided on the command line or in the configuration file. xLAN Manager does not recognize "%1" as a valid option. hA request for resource could not be satisfied. hA problem exists with the system configuration. DA system error has occurred. `An internal consistency error has occurred. The configuration file or the command line has an ambiguous option. The configuration file or the command line has a duplicate parameter. The service did not respond to control and was stopped with the DosKillProc function. An error occurred when attempting to run the service program. LThe sub-service failed to start. There is a conflict in the value or use of these options: %1. LThere is a problem with the file. memory disk space thread process 4Security Failure. %0 `Bad or missing LAN Manager root directory. XThe network software is not installed. @The server is not started. The server cannot access the user accounts database (NET.ACC). tIncompatible files are installed in the LANMAN tree. TThe LANMAN\LOGS directory is invalid. XThe domain specified could not be used. The computer name is being used as a message alias on another computer. `The announcement of the server name failed. xThe user accounts database is not configured correctly. pThe server is not running with user-level security. `The workstation is not configured properly. LView your error log for details. DUnable to write to this file. ADDPAK file is corrupted. Delete LANMAN\NETPROG\ADDPAK.SER and reapply all ADDPAKs. The LM386 server cannot be started because CACHE.EXE is not running. There is no account for this computer in the security database. pThis computer is not a member of the group SERVERS. The group SERVERS is not present in the local security database. 8This computer is configured as a member of a workgroup, not as a member of a domain. The Netlogon service does not need to run in this configuration. The primary Domain Controller for this domain could not be located. pThis computer is configured to be the primary domain controller of its domain. However, the computer %1 is currently claiming to be the primary domain controller of the domain. The service failed to authenticate with the primary domain controller. There is a problem with the security database creation date or serial number. The operation failed because a network software error occurred. The system ran out of a resource controlled by the %1 option. The service failed to obtain a long-term lock on the segment for network control blocks (NCBs). The error code is the data. The service failed to release the long-term lock on the segment for network control blocks (NCBs). The error code is the data. There was an error stopping service %1. The error code from NetServiceControl is the data. Initialization failed because of a system execution failure on path %1. The system error code is the data. An unexpected network control block (NCB) was received. The NCB is the data. @The network is not started. tA DosDevIoctl or DosFsCtl to NETWKSTA.SYS failed. The data shown is in this format: DWORD approx CS:IP of call to ioctl or fsctl WORD error code WORD ioctl or fsctl number Unable to create or open system semaphore %1. The error code is the data. Initialization failed because of an open/create error on the file %1. The system error code is the data. An unexpected NetBIOS error occurred. The error code is the data. An illegal server message block (SMB) was received. The SMB is the data. Initialization failed because the requested service %1 could not be started. Some entries in the error log were lost because of a buffer overflow. Initialization parameters controlling resource usage other than net buffers are sized so that too much memory is needed. |The server cannot increase the size of a memory segment. Initialization failed because account file %1 is either incorrect or not present. |Initialization failed because network %1 was not started. The server failed to start. Either all three chdev parameters must be zero or all three must be nonzero. A remote API request was halted due to the following invalid description string: %1. The network %1 ran out of network control blocks (NCBs). You may need to increase NCBs for this network. The following information includes the number of NCBs submitted by the server when this error occurred: The server cannot create the %1 mailslot needed to send the ReleaseMemory alert message. The error received is: The server failed to register for the ReleaseMemory alert, with recipient %1. The error code from NetAlertStart is the data. The server cannot update the AT schedule file. The file is corrupted. The server encountered an error when calling NetIMakeLMFileName. The error code is the data. DInitialization failed because of a system execution failure on path %1. There is not enough memory to start the process. The system error code is the data. Longterm lock of the server buffers failed. Check swap disk's free space and restart the system to start the server. ,The service has stopped due to repeated consecutive occurrences of a network control block (NCB) error. The last bad NCB follows in raw data. The Message server has stopped due to a lock on the Message server shared data segment. hA file system error occurred while opening or writing to the system message log file %1. Message logging has been switched off due to the error. The error code is the data. Unable to display message POPUP due to system VIO call error. The error code is the data. An illegal server message block (SMB) was received. The SMB is the data. The workstation information segment is bigger than 64K. The size follows, in DWORD format: The workstation was unable to get the name-number of the computer. The workstation could not initialize the Async NetBIOS Thread. The error code is the data. The workstation could not open the initial shared segment. The error code is the data. PThe workstation host table is full. A bad mailslot server message block (SMB) was received. The SMB is the data. The workstation encountered an error while trying to start the user accounts database. The error code is the data. The workstation encountered an error while responding to an SSI revalidation request. The function code and the error codes are the data. The Alerter service had a problem creating the list of alert recipients. The error code is %1. There was an error expanding %1 as a group name. Try splitting the group into two or more smaller groups. There was an error sending %2 the alert message - ( %3 ) The error code is %1. There was an error in creating or reading the alerter mailslot. The error code is %1. hThe server could not read the AT schedule file. hThe server found an invalid AT schedule record. The server could not find an AT schedule file so it created one. The server could not access the %1 network with NetBiosOpen. `The AT command processor could not run %1. WARNING: Because of a lazy-write error, drive %1 now contains some corrupted data. The cache is stopped. A defective sector on drive %1 has been replaced (hotfixed). No data was lost. You should run CHKDSK soon to restore full performance and replenish the volume's spare sector pool. The hotfix occurred while processing a remote request. A disk error occurred on the HPFS volume in drive %1. The error occurred while processing a remote request. The user accounts database (NET.ACC) is corrupted. The local security system is replacing the corrupted NET.ACC with the backup made at %1. Any updates made to the database after this time are lost. The user accounts database (NET.ACC) is missing. The local security system is restoring the backup database made at %1. Any updates made to the database made after this time are lost. tLocal security could not be started because the user accounts database (NET.ACC) was missing or corrupted, and no usable backup database was present. THE SYSTEM IS NOT SECURE. 0Local security could not be started because an error occurred during initialization. The error code returned is %1. THE SYSTEM IS NOT SECURE. `A NetWksta internal error has occurred: %1 \The redirector is out of a resource: %1. A server message block (SMB) error occurred on the connection to %1. The SMB header is the data. A virtual circuit error occurred on the session to %1. The network control block (NCB) command and return code is the data. LHanging up a stuck session to %1. A network control block (NCB) error occurred (%1). The NCB is the data. |A write operation to %1 failed. Data may have been lost. Reset of driver %1 failed to complete the network control block (NCB). The NCB is the data. The amount of resource %1 requested was more than the maximum. The maximum amount was allocated. The server could not create a thread. The THREADS parameter in the CONFIG.SYS file should be increased. The server could not close %1. The file is probably corrupted. The replicator cannot update directory %1. It has tree integrity and is the current directory for some process. The server cannot export directory %1 to client %2. It is exported from another server. The replication server could not update directory %2 from the source on %3 due to error %1. Master %1 did not send an update notice for directory %2 at the expected time. This computer could not authenticate with %2, a Windows domain controller for domain %1, and therefore this computer might deny logon requests. This inability to authenticate might be caused by another computer on the same network using the same name or the password for this computer account is not recognized. If this message appears again, contact your system administrator. The replicator attempted to log on at %2 as %1 and failed. @Network error %1 occurred. Replicator limit for files in a directory has been exceeded. pReplicator limit for tree depth has been exceeded. `Unrecognized message received in mailslot. <System error %1 occurred. Cannot log on. User is currently logged on and argument TRYUSER is set to NO. HIMPORT path %1 cannot be found. HEXPORT path %1 cannot be found. Replicator failed to update signal file in directory %2 due to %1 system error. LDisk Fault Tolerance Error %1 Replicator could not access %2 on %3 due to system error %1. The primary domain controller for domain %1 has apparently failed. Changing machine account password for account %1 failed with the following error: %n%2 An error occurred while updating the logon or logoff information for %1. An error occurred while synchronizing with primary domain controller %1 0The session setup to the Windows NT or Windows 2000 Domain Controller %1 for the domain %2 failed because %1 does not support signing or sealing the Netlogon session. Either upgrade the Domain controller or set the RequireSignOrSeal registry entry on this machine to 0. `A power failure was detected at the server. `The UPS service performed server shut down. The UPS service did not complete execution of the user specified shut down command file. The UPS driver could not be opened. The error code is the data. <Power has been restored. There is a problem with a configuration of user specified shut down command file. The UPS service failed to execute a user specified shutdown command file %1. The error code is the data. Initialization failed because of an invalid or missing parameter in the configuration file %1. Initialization failed because of an invalid line in the configuration file %1. The invalid line is the data. Initialization failed because of an error in the configuration file %1. The file %1 has been changed after initialization. The boot-block loading was temporarily terminated. The files do not fit to the boot-block configuration file %1. Change the BASE and ORG definitions or the order of the files. Initialization failed because the dynamic-link library %1 returned an incorrect version number. There was an unrecoverable error in the dynamic- link library of the service. The system returned an unexpected error code. The error code is the data. The fault-tolerance error log file, LANROOT\LOGS\FT.LOG, is more than 64K. hThe fault-tolerance error-log file, LANROOT\LOGS\FT.LOG, had the update in progress bit set upon opening, which means that the system crashed while working on the error log. This computer has been successfully joined to domain '%1'. This computer has been successfully joined to workgroup '%1'. @%1 %2 %3 %4 %5 %6 %7 %8 %9. $Remote IPC %0 (Remote Admin %0 4Logon server share %0 DA network error occurred. %0 There is not enough memory to start the Workstation service. An error occurred when reading the NETWORKS entry in the LANMAN.INI file. LThis is an invalid argument: %1. The %1 NETWORKS entry in the LANMAN.INI file has a syntax error and will be ignored. There are too many NETWORKS entries in the LANMAN.INI file. An error occurred when opening network device driver %1 = %2. lDevice driver %1 sent a bad BiosLinkage response. xThe program cannot be used with this operating system. TThe redirector is already installed. lInstalling NETWKSTA.SYS Version %1.%2.%3 (%4) There was an error installing NETWKSTA.SYS. Press ENTER to continue. <Resolver linkage problem. Your logon time at %1 ends at %2. Please clean up and log off. dYou will be automatically disconnected at %1. LYour logon time at %1 has ended. PYour logon time at %1 ended at %2. hWARNING: You have until %1 to logoff. If you have not logged off at this time, your session will be disconnected, and any open files or devices you have open may lose data. WARNING: You must log off at %1 now. You have two minutes to log off, or you will be disconnected. You have open files or devices, and a forced disconnection may cause you to lose data. LDefault Share for Internal Use %0 4Messenger Service %0 PThe command completed successfully. @You used an invalid option. DSystem error %1 has occurred. tThe command contains an invalid number of arguments. hThe command completed with one or more errors. \You used an option with an invalid value. <The option %1 is unknown. 8Option %1 is ambiguous. dA command was used with conflicting switches. DCould not find subprogram %1. The software requires a newer version of the operating system. xMore data is available than can be returned by Windows. lMore help is available by typing NET HELPMSG %1. This command can be used only on a Windows Domain Controller. This command cannot be used on a Windows Domain Controller. PThese Windows services are started: HThe %1 service is not started. DThe %1 service is starting%0 TThe %1 service could not be started. \The %1 service was started successfully. Stopping the Workstation service also stops the Server service. HThe workstation has open files. DThe %1 service is stopping%0 TThe %1 service could not be stopped. \The %1 service was stopped successfully. The following services are dependent on the %1 service. Stopping the %1 service will also stop these services. The service is starting or stopping. Please try again later. TThe service did not report an error. \An error occurred controlling the device. `The %1 service was continued successfully. XThe %1 service was paused successfully. LThe %1 service failed to resume. HThe %1 service failed to pause. TThe %1 service continue is pending%0 LThe %1 service pause is pending%0 H%1 was continued successfully. @%1 was paused successfully. The %1 service has been started by another process and is pending.%0 XA service specific error occurred: %1. lThese workstations have sessions on this server: These workstations have sessions with open files on this server: HThe message alias is forwarded. PYou have these remote connections: XContinuing will cancel the connections. PThe session from %1 has open files. PNew connections will be remembered. XNew connections will not be remembered. An error occurred while saving your profile : Access Denied. The state of your remembered connections has not changed. dAn error occurred while reading your profile. xAn error occurred while restoring the connection to %1. LNo network services are started. LThere are no entries in the list. Users have open files on %1. Continuing the operation will force the files closed. The Workstation service is already running. Windows will ignore command options for the workstation. There are open files and/or incomplete directory searches pending on the connection to %1. The request will be processed at a domain controller for domain %1. The shared queue cannot be deleted while a print job is being spooled to the queue. T%1 has a remembered connection to %2. hAn error occurred while opening the Help file. 8The Help file is empty. @The Help file is corrupted. lCould not find a domain controller for domain %1. This operation is privileged on systems with earlier versions of the software. @The device type is unknown. LThe log file has been corrupted. TProgram filenames must end with .EXE. A matching share could not be found so nothing was deleted. A bad value is in the units-per-week field of the user record. HThe password is invalid for %1. lAn error occurred while sending a message to %1. dThe password or user name is invalid for %1. dAn error occurred when the share was deleted. <The user name is invalid. <The password is invalid. @The passwords do not match. pYour persistent connections were not all restored. lThis is not a valid computer name or domain name. tDefault permissions cannot be set for that resource. LA valid password was not entered. DA valid name was not entered. TThe resource named cannot be shared. tThe permissions string contains invalid permissions. You can only perform this operation on printers and communication devices. T%1 is an invalid user or group name. xThe server is not configured for remote administration. \No users have sessions with this server. TUser %1 is not a member of group %2. \User %1 is already a member of group %2. @There is no such user: %1. DThis is an invalid response. HNo valid response was provided. The destination list provided does not match the destination list of the printer queue. \Your password cannot be changed until %1. X%1 is not a recognized day of the week. hThe time range specified ends before it starts. D%1 is not a recognized hour. d%1 is not a valid specification for minutes. \Time supplied is not exactly on the hour. d12 and 24 hour time formats may not be mixed. L%1 is not a valid 12-hour suffix. \An illegal date format has been supplied. XAn illegal day range has been supplied. \An illegal time range has been supplied. Arguments to NET USER are invalid. Check the minimum password length and/or arguments supplied. XThe value for ENABLESCRIPT must be YES. lAn illegal country/region code has been supplied. The user was successfully created but could not be added to the USERS local group. TThe user context supplied is invalid. The dynamic-link library %1 could not be loaded, or an error occurred while trying to use it. TSending files is no longer supported. tYou may not specify paths for ADMIN$ and IPC$ shares. xUser or group %1 is already a member of local group %2. PThere is no such user or group: %1. HThere is no such computer: %1. HThe computer %1 already exists. `There is no such global user or group: %1. `Only disk shares can be marked as cacheable XThe system could not find message: %1. HThis schedule date is invalid. \The LANMAN root directory is unavailable. XThe SCHED.LOG file could not be opened. \The Server service has not been started. DThe AT job ID does not exist. PThe AT schedule file is corrupted. The delete failed due to a problem with the AT schedule file. hThe command line cannot exceed 259 characters. The AT schedule file could not be updated because the disk is full. The AT schedule file is invalid. Please delete the file and create a new one. LThe AT schedule file was deleted. ,The syntax of this command is: AT [id] [/DELETE] AT time [/EVERY:date | /NEXT:date] command The AT command schedules a program command to run at a later date and time on a server. It also displays the list of programs and commands scheduled to be run. You can specify the date as M,T,W,Th,F,Sa,Su or 1-31 for the day of the month. You can specify the time in the 24 hour HH:MM format. xThe AT command has timed-out. Please try again later. The minimum password age for user accounts cannot be greater than the maximum password age. You have specified a value that is incompatible with servers with down-level software. Please specify a lower value. L%1 is not a valid computer name. l%1 is not a valid Windows network message number. @Message from %1 to %2 on %3 **** P**** unexpected end of message **** ,Press ESC to exit ... <Current time at %1 is %2 The current local clock is %1 Do you want to set the local computer's time to match the time at %2? %3: %0 HCould not locate a time-server. pCould not find the domain controller for domain %1. HLocal time (GMT%3) at %1 is %2 pThe user's home directory could not be determined. lThe user's home directory has not been specified. The name specified for the user's home directory (%1) is not a universal naming convention (UNC) name. Drive %1 is now connected to %2. Your home directory is %3\%4. LDrive %1 is now connected to %2. `There are no available drive letters left. `%1 is not a valid domain or workgroup name. DThe current SNTP value is: %1 This computer is not currently configured to use a specific SNTP server. dThis current autoconfigured SNTP value is: %1 lYou specified too many values for the %1 option. hYou entered an invalid value for the %1 option. <The syntax is incorrect. TYou specified an invalid file number. `You specified an invalid print job number. tThe user or group account specified cannot be found. The user was added but could not be enabled for File and Print Services for NetWare. tFile and Print Services for NetWare is not installed. Cannot set user properties for File and Print Services for NetWare. 8Password for %1 is: %2 <NetWare compatible logon Yes%0 No%0 All%0 None%0 Always%0 Never%0 Unlimited%0 Sunday%0 Monday%0 Tuesday%0 Wednesday%0 Thursday%0 Friday%0 Saturday%0 Su%0 M%0 T%0 W%0 Th%0 F%0 S%0 Unknown%0 AM%0 A.M.%0 PM%0 P.M.%0 Server%0 $Redirector%0 $Application%0 Total%0 ? %1 %0 K%0 (none)%0 Device%0 Remark%0 At%0 Queue%0 Queues%0 User name%0 Path%0 (Y/N) [Y]%0 (Y/N) [N]%0 Error%0 OK%0 Y%0 N%0 Any%0 A%0 P%0 $(not found)%0 (unknown)%0 HFor help on %1 type NET HELP %1 Grant%0 Read%0 Change%0 Full%0 DPlease type the password: %0 DType the password for %1: %0 LType a password for the user: %0 dType the password for the shared resource: %0 8Type your password: %0 PRetype the password to confirm: %0 LType the user's old password: %0 LType the user's new password: %0 @Type your new password: %0 \Type the Replicator service password: %0 pType your user name, or press ENTER if it is %1: %0 Type the domain or server where you want to change a password, or press ENTER if it is for domain %1: %0. 8Type your user name: %0 @Network statistics for \\%1 8Printing options for %1 \Communication-device queues accessing %1 ,Print job detail PCommunication-device queues at \\%1 (Printers at %1 4Printers accessing %1 ,Print jobs at %1: 8Shared resources at %1 lThe following running services can be controlled: Statistics are available for the following running services: 8User accounts for \\%1 HThe syntax of this command is: LThe options of this command are: Please enter the name of the Primary Domain Controller: %0 The string you have entered is too long. The maximum is %1, please reenter. %0 Sunday%0 Monday%0 Tuesday%0 Wednesday%0 Thursday%0 Friday%0 Saturday%0 Su%0 M%0 T%0 W%0 Th%0 F%0 S%0 Sa%0 8Group Accounts for \\%1 $Group name%0 Comment%0 Members ,Aliases for \\%1 $Alias name%0 Comment%0 Members 8User Accounts for \\%1 User name%0 Full Name%0 Comment%0 ,User's comment%0 $Parameters%0 4Country/region code%0 ,Privilege level%0 4Operator privileges%0 ,Account active%0 ,Account expires%0 0Password last set%0 0Password expires%0 4Password changeable%0 8Workstations allowed%0 4Maximum disk space%0 Unlimited%0 <Local Group Memberships%0 0Domain controller%0 (Logon script%0 $Last logon%0 @Global Group memberships%0 4Logon hours allowed%0 All%0 None%0 (Daily %1 - %2%0 ,Home directory%0 0Password required%0 @User may change password%0 (User profile%0 Locked%0 (Computer name%0 User name%0 0Software version%0 8Workstation active on%0 @Windows NT root directory%0 4Workstation domain%0 (Logon domain%0 ,Other domain(s)%0 <COM Open Timeout (sec)%0 8COM Send Count (byte)%0 <COM Send Timeout (msec)%0 PDOS session print time-out (sec)%0 DMaximum error log size (K)%0 @Maximum cache memory (K)%0 @Number of network buffers%0 DNumber of character buffers%0 <Size of network buffers%0 @Size of character buffers%0 4Full Computer name%0 DWorkstation Domain DNS Name%0 (Windows 2002%0 $Server Name%0 ,Server Comment%0 HSend administrative alerts to%0 0Software version%0 $Peer Server%0 $Windows NT%0 (Server Level%0 0Windows NT Server%0 4Server is active on%0 (Server hidden%0 <Maximum Logged On Users%0 PMaximum concurrent administrators%0 @Maximum resources shared%0 PMaximum connections to resources%0 HMaximum open files on server%0 LMaximum open files per session%0 4Maximum file locks%0 <Idle session time (min)%0 $Share-level%0 $User-level%0 0Unlimited Server%0 pForce user logoff how long after time expires?:%0 pLock out account after how many bad passwords?:%0 HMinimum password age (days):%0 HMaximum password age (days):%0 @Minimum password length:%0 \Length of password history maintained:%0 ,Computer role:%0 tPrimary Domain controller for workstation domain:%0. 4Lockout threshold:%0 DLockout duration (minutes):%0 XLockout observation window (minutes):%0 0Statistics since%0 0Sessions accepted%0 4Sessions timed-out%0 8Sessions errored-out%0 ,Kilobytes sent%0 4Kilobytes received%0 @Mean response time (msec)%0 ,Network errors%0 ,Files accessed%0 4Print jobs spooled%0 (System errors%0 4Password violations%0 8Permission violations%0 LCommunication devices accessed%0 0Sessions started%0 8Sessions reconnected%0 <Sessions starts failed%0 8Sessions disconnected%0 <Network I/O's performed%0 @Files and pipes accessed%0 8Times buffers exhausted $Big buffers%0 ,Request buffers%0 HWorkstation Statistics for \\%1 @Server Statistics for \\%1 0Statistics since %1 0Connections made%0 4Connections failed%0 ,Bytes received%0 XServer Message Blocks (SMBs) received%0 0Bytes transmitted%0 `Server Message Blocks (SMBs) transmitted%0 ,Read operations%0 0Write operations%0 0Raw reads denied%0 0Raw writes denied%0 ,Network errors%0 0Connections made%0 4Reconnections made%0 4Server disconnects%0 0Sessions started%0 (Hung sessions%0 ,Failed sessions%0 0Failed operations%0 Use count%0 0Failed use count%0 D%1 was deleted successfully. <%1 was used successfully. \The message was successfully sent to %1. hThe message name %1 was forwarded successfully. `The message name %1 was added successfully. xThe message name forwarding was successfully canceled. @%1 was shared successfully. hThe server %1 successfully logged you on as %2. H%1 was logged off successfully. %1 was successfully removed from the list of shares the Server creates on startup. XThe password was changed successfully. 0%1 file(s) copied. ,%1 file(s) moved. The message was successfully sent to all users of the network. hThe message was successfully sent to domain %1. The message was successfully sent to all users of this server. hThe message was successfully sent to group *%1. LMicrosoft LAN Manager Version %1 ,Windows NT Server 8Windows NT Workstation @MS-DOS Enhanced Workstation $Created at %1 DServer Name Remark tCannot enumerate servers in non-default compartment. (UNC)%0 ...%0 Domain (Resources on %1 pInvalid network provider. Available networks are: Disk%0 Print%0 Comm%0 IPC%0 |Status Local Remote Network OK%0 Dormant%0 Paused%0 (Disconnected%0 Error%0 $Connecting%0 (Reconnecting%0 Status%0 $Local name%0 $Remote name%0 (Resource type%0 # Opens%0 (# Connections%0 $Unavailable%0 pShare name Resource Remark $Share name%0 Resource%0 Spooled%0 $Permission%0 (Maximum users%0 No limit%0 Users%0 The share name entered may not be accessible from some MS-DOS workstations. Are you sure you want to use this share name? %1: %0 Caching%0 ID Path User name # Locks File ID%0 Locks%0 $Permissions%0 $Share name%0 Type%0 Used as%0 Comment%0 Computer User name Client Type Opens Idle time Computer%0 Sess time%0 Idle time%0 HShare name Type # Opens $Client type%0 $Guest logon%0 DManual caching of documents%0 LAutomatic caching of documents%0 dAutomatic caching of programs and documents%0 xManual caching of documents with BranchCache enabled%0 0Caching disabled%0 Automatic%0 Manual%0 Documents%0 Programs%0 $BranchCache%0 None%0 Name%0 (Forwarded to%0 8Forwarded to you from%0 8Users of this server%0 Net Send has been interrupted by a Ctrl+Break from the user. Name Job # Size Status jobs%0 Print%0 Name%0 Job #%0 Size%0 Status%0 ,Separator file%0 Comment%0 Priority%0 $Print after%0 $Print until%0 ,Print processor%0 ,Additional info%0 $Parameters%0 (Print Devices%0 ,Printer Active%0 (Printer held%0 (Printer error%0 8Printer being deleted%0 <Printer status unknown%0 (Held until %1%0 Job #%0 ,Submitting user%0 Notify%0 (Job data type%0 ,Job parameters%0 Waiting%0 (Held in queue%0 Spooling%0 Paused%0 Offline%0 Error%0 (Out of paper%0 8Intervention required%0 Printing%0 on %0 (Paused on %1%0 (Offline on %1%0 $Error on%1%0 4Out of Paper on %1%0 4Check printer on %1%0 ,Printing on %1%0 Driver%0 pUser name Type Date%0 Lockout%0 Service%0 Server%0 ,Server started%0 (Server paused%0 0Server continued%0 ,Server stopped%0 Session%0 $Logon Guest%0 $Logon User%0 4Logon Administrator%0 (Logoff normal%0 Logon%0 (Logoff error%0 <Logoff auto-disconnect%0 LLogoff administrator-disconnect%0 TLogoff forced by logon restrictions%0 Service%0 (%1 Installed%0 4%1 Install Pending%0 %1 Paused%0 0%1 Pause Pending%0 (%1 Continued%0 4%1 Continue Pending%0 $%1 Stopped%0 ,%1 Stop Pending%0 Account%0 HUser account %1 was modified.%0 LGroup account %1 was modified.%0 DUser account %1 was deleted%0 HGroup account %1 was deleted%0 @User account %1 was added%0 DGroup account %1 was added%0 XAccount system settings were modified%0 0Logon restriction%0 @Limit exceeded: UNKNOWN%0 HLimit exceeded: Logon hours%0 PLimit exceeded: Account expired%0 \Limit exceeded: Workstation ID invalid%0 PLimit exceeded: Account disabled%0 PLimit exceeded: Account deleted%0 Share%0 Use %1%0 Unuse %1%0 LUser's session disconnected %1%0 `Administrator stopped sharing resource %1%0 @User reached limit for %1%0 (Bad password%0 PAdministrator privilege required%0 Access%0 8%1 permissions added%0 <%1 permissions modified%0 <%1 permissions deleted%0 (Access denied%0 Unknown%0 Other%0 Duration:%0 <Duration: Not available%0 LDuration: Less than one second%0 (none)%0 Closed %1%0 @Closed %1 (disconnected)%0 <Administrator closed %1%0 (Access ended%0 0Log on to network%0 (Logon denied%0 hProgram Message Time%0 \Account locked due to %1 bad passwords%0 PAccount unlocked by administrator%0 ,Log off network%0  LSubj: ** ADMINISTRATOR ALERT ** PSubj: ** PRINTING NOTIFICATION ** HSubj: ** USER NOTIFICATION ** 0From: %1 at \\%2 tPrint job %1 has been canceled while printing on %2. lPrint job %1 has been deleted and will not print. pPrinting Complete %1 printed successfully on %2. hPrint job %1 has not completed printing on %2. XPrint job %1 has paused printing on %2. PPrint job %1 is now printing on %2. DThe printer is out of paper. 8The printer is offline. <Printing errors occurred. tThere is a problem with the printer; please check it. \Print job %1 is being held from printing. TPrint job %1 is queued for printing. HPrint job %1 is being spooled. @Job was queued to %1 on %2 <Size of job is %1 bytes. To: %1 Date: %1 The error code is %1. There was an error retrieving the message. Make sure the file NET.MSG is available. Printing Failed "%1" failed to print on %2 on %3. For more help use the print troubleshooter. Printing Failed "%1" failed to print on %2 on %3. The Printer is %4. For more help use the print troubleshooter. Printing Complete "%1" printed successfully on %2 on %3. January%0 February%0 March%0 April%0 May%0 June%0 July%0 August%0 September%0 October%0 November%0 December%0 Jan%0 Feb%0 Mar%0 Apr%0 May%0 Jun%0 Jul%0 Aug%0 Sep%0 Oct%0 Nov%0 Dec%0 D%0 H%0 M%0 Sa%0 PRIMARY%0. BACKUP%0. (WORKSTATION%0. SERVER%0. ,System Default%0 (United States%0 ,Canada (French)%0 (Latin America%0 $Netherlands%0 Belgium%0 France%0 Italy%0 $Switzerland%0 ,United Kingdom%0 Spain%0 Denmark%0 Sweden%0 Norway%0 Germany%0 Australia%0 Japan%0 Korea%0 $China (PRC)%0 Taiwan%0 Asia%0 Portugal%0 Finland%0 Arabic%0 Hebrew%0 A power failure has occurred at %1. Please terminate all activity with this server. Power has been restored at %1. Normal operations have resumed. dThe UPS service is starting shut down at %1. tThe UPS service is about to perform final shut down. The Workstation must be started with the NET START command. $Remote IPC%0 (Remote Admin%0 (Default share%0 (User Profiles%0 xThe password entered is longer than 14 characters. Computers with Windows prior to Windows 2000 will not be able to use this account. Do you want to continue this operation? %1: %0 %1 has a remembered connection to %2. Do you want to overwrite the remembered connection? %3: %0 Do you want to resume loading the profile? The command which caused the error will be ignored. %1: %0 hDo you want to continue this operation? %1: %0 HDo you want to add this? %1: %0 hDo you want to continue this operation? %1: %0 DIs it OK to start it? %1: %0 tDo you want to start the Workstation service? %1: %0 Is it OK to continue disconnecting and force them closed? %1: %0 The printer does not exist. Do you want to create it? %1: %0 Never%0 Never%0 Never%0 NET.HLP%0 NET.HLP%0 Deny%0 The network control block (NCB) request completed successfully. The NCB is the data. $Illegal network control block (NCB) buffer length on SEND DATAGRAM, SEND BROADCAST, ADAPTER STATUS, or SESSION STATUS. The NCB is the data. The data descriptor array specified in the network control block (NCB) is invalid. The NCB is the data. The command specified in the network control block (NCB) is illegal. The NCB is the data. The message correlator specified in the network control block (NCB) is invalid. The NCB is the data. A network control block (NCB) command timed-out. The session may have terminated abnormally. The NCB is the data. An incomplete network control block (NCB) message was received. The NCB is the data. The buffer address specified in the network control block (NCB) is illegal. The NCB is the data. The session number specified in the network control block (NCB) is not active. The NCB is the data. No resource was available in the network adapter. The network control block (NCB) request was refused. The NCB is the data. The session specified in the network control block (NCB) was closed. The NCB is the data. The network control block (NCB) command was canceled. The NCB is the data. The message segment specified in the network control block (NCB) is illogical. The NCB is the data. The name already exists in the local adapter name table. The network control block (NCB) request was refused. The NCB is the data. The network adapter name table is full. The network control block (NCB) request was refused. The NCB is the data. The network name has active sessions and is now de-registered. The network control block (NCB) command completed. The NCB is the data. 8A previously issued Receive Lookahead command is active for this session. The network control block (NCB) command was rejected. The NCB is the data. The local session table is full. The network control block (NCB) request was refused. The NCB is the data. A network control block (NCB) session open was rejected. No LISTEN is outstanding on the remote computer. The NCB is the data. The name number specified in the network control block (NCB) is illegal. The NCB is the data. The call name specified in the network control block (NCB) cannot be found or did not answer. The NCB is the data. The name specified in the network control block (NCB) was not found. Cannot put '*' or 00h in the NCB name. The NCB is the data. The name specified in the network control block (NCB) is in use on a remote adapter. The NCB is the data. The name specified in the network control block (NCB) has been deleted. The NCB is the data. The session specified in the network control block (NCB) ended abnormally. The NCB is the data. The network protocol has detected two or more identical names on the network. The network control block (NCB) is the data. An unexpected protocol packet was received. There may be an incompatible remote device. The network control block (NCB) is the data. The NetBIOS interface is busy. The network control block (NCB) request was refused. The NCB is the data. There are too many network control block (NCB) commands outstanding. The NCB request was refused. The NCB is the data. The adapter number specified in the network control block (NCB) is illegal. The NCB is the data. The network control block (NCB) command completed while a cancel was occurring. The NCB is the data. The name specified in the network control block (NCB) is reserved. The NCB is the data. The network control block (NCB) command is not valid to cancel. The NCB is the data. There are multiple network control block (NCB) requests for the same session. The NCB request was refused. The NCB is the data. 0There has been a network adapter error. The only NetBIOS command that may be issued is an NCB RESET. The network control block (NCB) is the data. The maximum number of applications was exceeded. The network control block (NCB) request was refused. The NCB is the data. The requested resources are not available. The network control block (NCB) request was refused. The NCB is the data. A system error has occurred. The network control block (NCB) request was refused. The NCB is the data. A ROM checksum failure has occurred. The network control block (NCB) request was refused. The NCB is the data. A RAM test failure has occurred. The network control block (NCB) request was refused. The NCB is the data. A digital loopback failure has occurred. The network control block (NCB) request was refused. The NCB is the data. An analog loopback failure has occurred. The network control block (NCB) request was refused. The NCB is the data. An interface failure has occurred. The network control block (NCB) request was refused. The NCB is the data. An unrecognized network control block (NCB) return code was received. The NCB is the data. A network adapter malfunction has occurred. The network control block (NCB) request was refused. The NCB is the data. The network control block (NCB) command is still pending. The NCB is the data. The update log on %1 is over 80%% capacity. The primary domain controller %2 is not retrieving the updates. The update log on %1 is full, and no further updates can be added until the primary domain controller %2 retrieves the updates. The time difference with the primary domain controller %1 exceeds the maximum allowed skew of %2 seconds. The account of user %1 has been locked out on %2 due to %3 bad password attempts. LThe %1 log file cannot be opened. lThe %1 log file is corrupted and will be cleared. The Application log file could not be opened. %1 will be used as the default log file. The %1 Log is full. If this is the first time you have seen this message, take the following steps:%n 1. Click Start, click Run, type "eventvwr", and then click OK.%n 2. Click %1, click the Action menu, click Clear All Events, and then click No. %n If this dialog reappears, contact your helpdesk or system administrator. The security database full synchronization has been initiated by the server %1. Windows could not be started as configured. A previous working configuration was used instead. The exception 0x%1 occurred in the application %2 at location 0x%3. The servers %1 and %3 both claim to be an NT Domain Controller for the %2 domain. One of the servers should be removed from the domain because the servers have different security identifiers (SID). <The server %1 and %2 both claim to be the primary domain controller for the %3 domain. One of the servers should be demoted or removed from the domain. The computer %1 tried to connect to the server %2 using the trust relationship established by the %3 domain. However, the computer lost the correct security identifier (SID) when the domain was reconfigured. Reestablish the trust relationship. The computer has rebooted from a bugcheck. The bugcheck was: %1. %2 A full dump was not saved. The computer has rebooted from a bugcheck. The bugcheck was: %1. %2 A dump was saved in: %3. The computer or domain %1 trusts domain %2. (This may be an indirect trust.) However, %1 and %2 have the same machine security identifier (SID). NT should be re-installed on either %1 or %2. The computer or domain %1 trusts domain %2. (This may be an indirect trust.) However, %2 is not a valid name for a trusted domain. The name of the trusted domain should be changed to a valid name. \Could not share the User or Script path. The password for this computer is not found in the local security database. An internal error occurred while accessing the computer's local or network security database. <The Netlogon service could not initialize the replication data structures successfully. The service was terminated. The following error occurred: %n%1 The Netlogon service failed to update the domain trust list. The following error occurred: %n%1 The Netlogon service could not add the RPC interface. The service was terminated. The following error occurred: %n%1 The Netlogon service could not read a mailslot message from %1 due to the following error: %n%2 ,The Netlogon service failed to register the service with the service controller. The service was terminated. The following error occurred: %n%1 4The change log cache maintained by the Netlogon service for %1 database changes is inconsistent. The Netlogon service is resetting the change log. The Netlogon service could not create server share %1. The following error occurred: %n%2 The down-level logon request for the user %1 from %2 failed. The down-level logoff request for the user %1 from %2 failed. The Windows NT or Windows 2000 %1 logon request for the user %2\%3 from %4 (via %5) failed. The Windows NT or Windows 2000 %1 logoff request for the user %2\%3 from %4 failed. The partial synchronization request from the server %1 completed successfully. %2 changes(s) has(have) been returned to the caller. The partial synchronization request from the server %1 failed with the following error: %n%2 The full synchronization request from the server %1 completed successfully. %2 object(s) has(have) been returned to the caller. The full synchronization request from the server %1 failed with the following error: %n%2 \The partial synchronization replication of the %1 database from the primary domain controller %2 completed successfully. %3 change(s) is(are) applied to the database. The partial synchronization replication of the %1 database from the primary domain controller %2 failed with the following error: %n%3 The full synchronization replication of the %1 database from the primary domain controller %2 completed successfully. The full synchronization replication of the %1 database from the primary domain controller %2 failed with the following error: %n%3 This computer was not able to set up a secure session with a domain controller in domain %1 due to the following: %n%2 %nThis may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator. %n%nADDITIONAL INFO %nIf this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain. `The session setup to the Windows NT or Windows 2000 Domain Controller %1 for the domain %2 failed because the computer %3 does not have a local security database account. The session setup to the Windows NT or Windows 2000 Domain Controller %1 for the domain %2 failed because the Domain Controller did not have an account %4 needed to set up the session by this computer %3. %n%nADDITIONAL DATA %nIf this computer is a member of or a Domain Controller in the specified domain, the aforementioned account is a computer account for this computer in the specified domain. Otherwise, the account is an interdomain trust account with the specified domain. dThe session setup from the computer %1 failed to authenticate. The name(s) of the account(s) referenced in the security database is %2. The following error occurred: %n%3 The session setup from computer '%1' failed because the security database does not contain a trust account '%2' referenced by the specified computer. %n%nUSER ACTION %nIf this is the first occurrence of this event for the specified computer and account, this may be a transient issue that doesn't require any action at this time. If this is a Read-Only Domain Controller and '%2' is a legitimate machine account for the computer '%1' then '%1' should be marked cacheable for this location if appropriate or otherwise ensure connectivity to a domain controller capable of servicing the request (for example a writable domain controller). Otherwise, the following steps may be taken to resolve this problem: %n%nIf '%2' is a legitimate machine account for the computer '%1', then '%1' should be rejoined to the domain. %n%nIf '%2' is a legitimate interdomain trust account, then the trust should be recreated. %n%nOtherwise, assuming that '%2' is not a legitimate account, the following action should be taken on '%1': %n%nIf '%1' is a Domain Controller, then the trust associated with '%2' should be deleted. %n%nIf '%1' is not a Domain Controller, it should be disjoined from the domain. Could not register control handler with service controller %1. |Could not set service status with service controller %1. TCould not find the computer name %1. LCould not load %1 device driver. DCould not load any transport. Replication of the %1 Domain Object "%2" from primary domain controller %3 failed with the following error: %n%4 Replication of the %1 Global Group "%2" from primary domain controller %3 failed with the following error: %n%4 Replication of the %1 Local Group "%2" from primary domain controller %3 failed with the following error: %n%4 Replication of the %1 User "%2" from primary domain controller %3 failed with the following error: %n%4 Replication of the %1 Policy Object "%2" from primary domain controller %3 failed with the following error: %n%4 Replication of the %1 Trusted Domain Object "%2" from primary domain controller %3 failed with the following error: %n%4 Replication of the %1 Account Object "%2" from primary domain controller %3 failed with the following error: %n%4 Replication of the %1 Secret "%2" from primary domain controller %3 failed with the following error: %n%4 The system returned the following unexpected error code: %n%1 Netlogon has detected two machine accounts for server "%1". The server can be either a Windows 2000 Server that is a member of the domain or the server can be a LAN Manager server with an account in the SERVERS global group. It cannot be both. LThis domain has more global groups than can be replicated to a LanMan BDC. Either delete some of your global groups or remove the LanMan BDCs from the domain. The Browser driver returned the following error to Netlogon: %n%1 Netlogon could not register the %1<1B> name for the following reason: %n%2 Service failed to retrieve messages needed to boot remote boot clients. Service experienced a severe error and can no longer provide remote boot for 3Com 3Start remote boot clients. Service experienced a severe system error and will shut itself down. Client with computer name %1 failed to acknowledge receipt of the boot data. Remote boot of this client was not completed. Client with computer name %1 was not booted due to an error in opening file %2. Client with computer name %1 was not booted due to an error in reading file %2. Client with computer name %1 was not booted due to insufficient memory at the remote boot server. Client with computer name %1 will be booted without using checksums because checksum for file %2 could not be calculated. Client with computer name %1 was not booted due to too many lines in file %2. HClient with computer name %1 was not booted because the boot block configuration file %2 for this client does not contain boot block line and/or loader line. Client with computer name %1 was not booted due to a bad size of file %2. Client with computer name %1 was not booted due to remote boot service internal error. Client with computer name %1 was not booted because file %2 has an invalid boot header. Client with computer name %1 was not booted due to network error. Client with adapter id %1 was not booted due to lack of resources. xService experienced error copying file or directory %1. |Service experienced error deleting file or directory %1. Service experienced error setting permissions on file or directory %1. |Service experienced error evaluating RPL configurations. Service experienced error creating RPL profiles for all configurations. dService experienced error accessing registry. Service experienced error replacing possibly outdated RPLDISK.SYS. |Service experienced error adding security accounts or setting file permissions. These accounts are the RPLUSER local group and the user accounts for the individual RPL workstations. XService failed to back up its database. @Service failed to initialize from its database. The database may be missing or corrupted. Service will attempt restoring the database from the backup. Service failed to restore its database from the backup. Service will not start. Service successfully restored its database from the backup. Service failed to initialize from its restored database. Service will not start. The session setup to the Windows NT or Windows 2000 Domain Controller %1 from computer %2 using account %4 failed. %2 is declared to be a BDC in domain %3. However, %2 tried to connect as either a DC in a trusted domain, a member workstation in domain %3, or as a server in domain %3. Use the Active Directory Users and Computers tool or Server Manager to remove the BDC account for %2. The Remoteboot database was in NT 3.5 / NT 3.51 format and NT is attempting to convert it to NT 4.0 format. The JETCONV converter will write to the Application event log when it is finished. LGlobal group SERVERS exists in domain %1 and has members. This group defines Lan Manager BDCs in the domain. Lan Manager BDCs are not permitted in NT domains. The following DNS server that is authoritative for the DNS domain controller locator records of this domain controller does not support dynamic DNS updates: %n%nDNS server IP address: %1 %nReturned Response Code (RCODE): %2 %nReturned Status Code: %3 %n%nUSER ACTION %nConfigure the DNS server to allow dynamic DNS updates or manually add the DNS records from the file '%SystemRoot%\System32\Config\Netlogon.dns' to the DNS database. The dynamic registration of the DNS record '%1' failed on the following DNS server: %n%nDNS server IP address: %3 %nReturned Response Code (RCODE): %4 %nReturned Status Code: %5 %n%nFor computers and users to locate this domain controller, this record must be registered in DNS. %n%nUSER ACTION %nDetermine what might have caused this failure, resolve the problem, and initiate registration of the DNS records by the domain controller. To determine what might have caused this failure, run DCDiag.exe. To learn more about DCDiag.exe, see Help and Support Center. To initiate registration of the DNS records by this domain controller, run 'nltest.exe /dsregdns' from the command prompt on the domain controller or restart Net Logon service. %n Or, you can manually add this record to DNS, but it is not recommended. %n%nADDITIONAL DATA %nError Value: %2 The dynamic deletion of the DNS record '%1' failed on the following DNS server: %n%nDNS server IP address: %3 %nReturned Response Code (RCODE): %4 %nReturned Status Code: %5 %n%nUSER ACTION %nTo prevent remote computers from connecting unnecessarily to the domain controller, delete the record manually or troubleshoot the failure to dynamically delete the record. To learn more about debugging DNS, see Help and Support Center. %n%nADDITIONAL DATA %nError Value: %2 Failed to create/open file %1 with the following error: %n%2 Netlogon got the following error while trying to get the subnet to site mapping information from the DS: %n%1 '%1' tried to determine its site by looking up its IP address ('%2') in the Configuration\Sites\Subnets container in the DS. No subnet matched the IP address. Consider adding a subnet object for this IP address. LThe site name for this computer is '%1'. That site name is not a valid site name. A site name must be a valid DNS label. Rename the site to be a valid name. dThe subnet object '%1' appears in the Configuration\Sites\Subnets container in the DS. The name is not syntactically valid. The valid syntax is xx.xx.xx.xx/yy where xx.xx.xx.xx is a valid IP subnet number and yy is the number of bits in the subnet mask. Correct the name of the subnet object. Dynamic registration or deletion of one or more DNS records associated with DNS domain '%1' failed. These records are used by other computers to locate this server as a domain controller (if the specified domain is an Active Directory domain) or as an LDAP server (if the specified domain is an application partition). %n%nPossible causes of failure include: %n- TCP/IP properties of the network connections of this computer contain wrong IP address(es) of the preferred and alternate DNS servers %n- Specified preferred and alternate DNS servers are not running %n- DNS server(s) primary for the records to be registered is not running %n- Preferred or alternate DNS servers are configured with wrong root hints %n- Parent DNS zone contains incorrect delegation to the child zone authoritative for the DNS records that failed registration %n%nUSER ACTION %nFix possible misconfiguration(s) specified above and initiate registration or deletion of the DNS records by running 'nltest.exe /dsregdns' from the command prompt on the domain controller or by restarting Net Logon service on the domain controller. Dynamic registration or deregistration of one or more DNS records failed with the following error: %n%1 tThe session setup to the Windows NT or Windows 2000 Domain Controller %1 for the domain %2 is not responsive. The current RPC call from Netlogon on \\%3 to %1 has been cancelled. Site '%2' does not have any Domain Controllers for domain '%3'. Domain Controllers in site '%1' have been automatically selected to cover site '%2' for domain '%3' based on configured Directory Server replication costs. This Domain Controller no longer automatically covers site '%1' for domain '%2'. Site '%2' does not have any Global Catalog servers for forest '%3'. Global Catalog servers in site '%1' have been automatically selected to cover site '%2' for forest '%3' based on configured Directory Server replication costs. This Global Catalog server no longer automatically covers site '%1' for forest '%2'. tAttempt to update HOST Service Principal Names (SPNs) of the computer object in Active Directory failed. The updated values were '%1' and '%2'. The following error occurred: %n%3 0Attempt to update DNS Host Name of the computer object in Active Directory failed. The updated value was '%1'. The following error occurred: %n%2 No suitable Domain Controller is available for domain %1. An NT4 or older domain controller is available but it cannot be used for authentication purposes in the Windows 2000 or newer domain that this computer is a member of. The following error occurred:%n%2 The domain of this computer, %1 has been downgraded from Windows 2000 or newer to Windows NT4 or older. The computer cannot function properly in this case for authentication purposes. This computer needs to rejoin the domain. The following error occurred:%n%2 Site '%2' does not have any LDAP servers for non-domain NC '%3'. LDAP servers in site '%1' have been automatically selected to cover site '%2' for non-domain NC '%3' based on configured Directory Server replication costs. This LDAP server no longer automatically covers site '%1' for non-domain NC '%2'. Site '%2' is no longer manually configured in the registry as covered by this Domain Controller for domain '%3'. As a result, site '%2' does not have any Domain Controllers for domain '%3'. Domain Controllers in site '%1' have been automatically selected to cover site '%2' for domain '%3' based on configured Directory Server replication costs. This Domain Controller no longer automatically covers site '%1' for domain '%2'. However, site '%1' is still (manually) covered by this Domain Controller for domain '%2' since this site has been manually configured in the registry. Site '%2' is no longer manually configured in the registry as covered by this Global Catalog server for forest '%3'. As a result, site '%2' does not have any Global Catalog servers for forest '%3'. Global Catalog servers in site '%1' have been automatically selected to cover site '%2' for forest '%3' based on configured Directory Server replication costs. This Global Catalog server no longer automatically covers site '%1' for forest '%2'. However, site '%1' is still (manually) covered by this Global catalog for forest '%2' since this site has been manually configured in the registry. Site '%2' is no longer manually configured in the registry as covered by this LDAP server for non-domain NC '%3'. As a result, site '%2' does not have any LDAP servers for non-domain NC '%3'. LDAP servers in site '%1' have been automatically selected to cover site '%2' for non-domain NC '%3' based on configured Directory Server replication costs. This LDAP server no longer automatically covers site '%1' for non-domain NC '%2'. However, site '%1' is still (manually) covered by this LDAP server for non-domain NC '%2' since this site has been manually configured in the registry. \Attempt to update DnsHostName and HOST Service Principal Name (SPN) attributes of the computer object in Active Directory failed because the Domain Controller '%1' had more than one account with the name '%2' corresponding to this computer. Not having SPNs registered may result in authentication failures for this computer. Contact your domain administrator who may need to manually resolve the account name collision. Attempt to update DnsHostName and HOST Service Principal Name (SPN) attributes of the computer object in Active Directory failed because this computer account name, '%2' could not be mapped to the computer object on Domain Controller '%1'. Not having SPNs registered may result in authentication failures for this computer. Contact your domain administrator. The following technical information may be useful for the resolution of this failure:%n DsCrackNames status = 0x%3, crack error = 0x%4. None of the IP addresses (%2) of this Domain Controller map to the configured site '%1'. While this may be a temporary situation due to IP address changes, it is generally recommended that the IP address of the Domain Controller (accessible to machines in its domain) maps to the Site which it services. If the above list of IP addresses is stable, consider moving this server to a site (or create one if it does not already exist) such that the above IP address maps to the selected site. This may require the creation of a new subnet object (whose range includes the above IP address) which maps to the selected site object. The following error occurred while reading a parameter '%2' in the Netlogon %1 registry section:%n%3 The Netlogon %1 registry key contains an invalid value 0x%2 for parameter '%3'. The minimum and maximum values allowed for this parameter are 0x%4 and 0x%5, respectively. The value of 0x%6 has been assigned to this parameter. The session setup from the computer %1 failed to authenticate. The following error occurred: %n%2 ,Dynamic DNS updates have been manually disabled on this domain controller. %n%nUSER ACTION %nReconfigure this domain controller to use dynamic DNS updates or manually add the DNS records from the file '%SystemRoot%\System32\Config\Netlogon.dns' to the DNS database. During the past %1 hours there have been %2 connections to this Domain Controller from client machines whose IP addresses don't map to any of the existing sites in the enterprise. Those clients, therefore, have undefined sites and may connect to any Domain Controller including those that are in far distant locations from the clients. A client's site is determined by the mapping of its subnet to one of the existing sites. To move the above clients to one of the sites, please consider creating subnet object(s) covering the above IP addresses with mapping to one of the existing sites. The names and IP addresses of the clients in question have been logged on this computer in the following log file '%SystemRoot%\debug\netlogon.log' and, potentially, in the log file '%SystemRoot%\debug\netlogon.bak' created if the former log becomes full. The log(s) may contain additional unrelated debugging information. To filter out the needed information, please search for lines which contain text 'NO_CLIENT_SITE:'. The first word after this string is the client name and the second word is the client IP address. The maximum size of the log(s) is controlled by the following registry DWORD value 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\LogFileMaxSize'; the default is %3 bytes. The current maximum size is %4 bytes. To set a different maximum size, create the above registry value and set the desired maximum size in bytes. The deregistration of some DNS domain controller locator records was aborted at the time of this domain controller demotion because the DNS deregistrations took too long. %n%nUSER ACTION %nManually delete the DNS records listed in the file '%SystemRoot%\System32\Config\Netlogon.dns' from the DNS database.  The NetLogon service on this domain controller has been configured to use port %1 for incoming RPC connections over TCP/IP from remote machines. However, the following error occurred when Netlogon attempted to register this port with the RPC endpoint mapper service: %n%2 %nThis will prevent the NetLogon service on remote machines from connecting to this domain controller over TCP/IP that may result in authentication problems. %n%nUSER ACTION %nThe specified port is configured via the Group Policy or via a registry value 'DcTcpipPort' under the 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters' registry key; the value configured through the Group Policy takes precedence. If the port specified is in error, reset it to a correct value. You can also remove this configuration for the port in which case the port will be assigned dynamically by the endpoint mapper at the time the NetLogon service on remote machines makes RPC connections to this domain controller. After the misconfiguration is corrected, restart the NetLogon service on this machine and verify that this event log no longer appears. During the past %1 hours, this domain controller has received %2 connections from dual-stack IPv4/IPv6 clients with partial subnet-site mappings. A client has a partial subnet-site mapping if its IPv4 address is mapped to a site but its global IPv6 address is not mapped to a site, or vice versa. To ensure correct behavior for applications running on member computers and servers that rely on subnet-site mappings, dual-stack IPv4/IPv6 clients must have both IPv4 and global IPv6 addresses mapped to the same site. If a partially mapped client attempts to connect to this domain controller using its unmapped IP address, its mapped address is used for the client's site mapping. %n%nThe log files %SystemRoot%\debug\netlogon.log or %SystemRoot%\debug\netlogon.bak contain the name, unmapped IP address and mapped IP address for each partially mapped client. The log files may also contain unrelated debugging information. To locate the information pertaining to partial-subnet mappings, search for lines that contain the text 'PARTIAL_CLIENT_SITE_MAPPING:'. The first word after this text is the client name. Following the client name is the client's unmapped IP address (the IP address that does not have a subnet-site mapping) and the client's mapped IP address, which was used to return site information. %n%nUSER ACTION %nUse the Active Directory Sites and Services management console (MMC) snap-in to add the subnet mapping for the unmapped IP addresses to the same site being used by the mapped IP addresses. When adding site mappings for IPv6 addresses, you should use global IPv6 addresses and not for instance temporary, link-local or site-local IPv6 addresses. %n%nThe default maximum size of the log files is %3 bytes. The current maximum size is %4 bytes. To set a different maximum size, create the following registry DWORD value to specify the maximum size in bytes: %nHKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters\LogFileMaxSize The dynamic registration of the DNS record '%1' for the remote domain controller '%3' failed on the following DNS server: %n%nDNS server IP address: %4 %nReturned Response Code (RCODE): %5 %nReturned Status Code: %6 %n%nFor computers and users to locate the domain controller '%3', this record must be registered in DNS. %n%nUSER ACTION %nDetermine what might have caused this failure, resolve the problem, and initiate registration of the DNS records by the domain controller '%3'. For help with determining and resolving the problem, see Help and Support for information about troubleshooting DNS. To initiate registration of the DNS records by the domain controller '%3', run 'nltest.exe /dsregdns' from the command prompt on the domain controller '%3' or restart the Net Logon service on the domain controller '%3'. Nltest.exe is a command line tool that is built into Windows Server. %n As a workaround, you can manually add this record to DNS, but it is not recommended because you then must manually update any changes it requires hereafter. %n%nADDITIONAL DATA %nError Value: %2 The dynamic deregistration of the DNS record '%1' for the remote domain controller '%3' failed on the following DNS server: %n%nDNS server IP address: %4 %nReturned Response Code (RCODE): %5 %nReturned Status Code: %6 %n%nUSER ACTION %nTo prevent remote computers from attempting to connect to the domain controller '%3' using an invalid record, delete the record '%1' manually or troubleshoot the root cause behind the dynamic deregistration failure. To learn more about troubleshooting DNS, see Help and Support. %n%nADDITIONAL DATA %nError Value: %2 \The dynamic registration request for the DNS record '%1' has been rejected by the remote domain controller '%2'. Error: '%3' %n%nFor computers and users to locate this domain controller, this record must be registered in DNS. If the problem persists, please contact your domain administrator. The dynamic deregistration request of the DNS record '%1' has been rejected by the remote domain controller '%2'. Error: '%3' %n%nTo prevent remote computers from connecting unnecessarily to this domain controller, an administrator with sufficient privileges must manually delete the record on the DNS server that hosts it. The remoting of the dynamic update request for the local domain controller's DNS records through a secure session has failed with error '%1'. %n%nFor other computers and member servers to locate this domain controller, the appropriate records must be registered in DNS. On this domain controller, look for events related to failure to set up a secure session to determine why the request is failing. If the problem persists, please contact your domain administrator. Netlogon has failed an authentication request of account %1 in domain %2. The request timed out before it could be sent to domain controller %3 in domain %4. This is the first failure. If the problem continues, consolidated events will be logged about every %5 minutes. Please see http://support.microsoft.com/kb/2654097 for more information. Netlogon has failed an additional %1 authentication requests in the last %2 minutes. The requests timed out before they could be sent to domain controller %3 in domain %4. Please see http://support.microsoft.com/kb/2654097 for more information. Netlogon took more than %1 seconds for an authentication request of account %2 in domain %3, through domain controller %4 in domain %5. This is the first warning. If the problem persists, a recurring event will be logged every %6 minutes. Please see http://support.microsoft.com/kb/2654097 for more information on this error. Netlogon took more than %1 seconds for %2 authentication requests through domain controller %3 in domain %4 in the last %5 minutes. Please see http://support.microsoft.com/kb/2654097 for more information. The Netlogon service could not add the AuthZ RPC interface. The service was terminated. The following error occurred: '%1' The Netlogon service failed to initialize the AuthZ resource manager. The service was terminated. The following error occurred: '%1'. XThe Netlogon service failed to initialize the security descriptor for the Netlogon RPC interface. The service was terminated. The following error occurred: '%1'.  The system successfully changed its password on the domain controller %1. This event is logged when the password for the computer account is changed by the system. It is logged on the computer that changed the password. 4 The system successfully changed the password for managed service account %1 on the domain controller %2. This event is logged when the password for a standalone managed service account is changed by the system. It is logged on the computer that changed the password. The Netlogon service detected a non-windows account using secure RPC. %n%n Machine SamAccountName: %1 %n Domain: %2 %n Account Type: %3 %n Machine Os: %4 %n Machine Os Build Version: %5 %n Machine Os Service Pack: %6 8The Netlogon service denied a vulnerable Netlogon secure channel connection from a machine account. %n%n Machine SamAccountName: %1 %n Domain: %2 %n Account Type: %3 %n Machine Operating System: %4 %n Machine Operating System Build: %5 %n Machine Operating System Service Pack: %6 %n%nFor more information about why this was denied, please visit https://go.microsoft.com/fwlink/?linkid=2133485. pThe Netlogon service denied a vulnerable Netlogon secure channel connection using a trust account. %n%n Account Type: %1 %n Trust Name: %2 %n Trust Target: %3 %n Client IP Address: %4 %n%nFor more information about why this was denied, please visit https://go.microsoft.com/fwlink/?linkid=2133485. The Netlogon service allowed a vulnerable Netlogon secure channel connection. %n%nWarning: This connection will be denied once the enforcement phase is released. To better understand the enforcement phase, please visit https://go.microsoft.com/fwlink/?linkid=2133485. %n%n Machine SamAccountName: %1 %n Domain: %2 %n Account Type: %3 %n Machine Operating System: %4 %n Machine Operating System Build: %5 %n Machine Operating System Service Pack: %6 The Netlogon service allowed a vulnerable Netlogon secure channel connection because the machine account is allowed in the "Domain controller: Allow vulnerable Netlogon secure channel connections" group policy. %n%nWarning: Using vulnerable Netlogon secure channels will expose the domain-joined devices to attack. To protect your device from attack, remove a machine account from "Domain controller: Allow vulnerable Netlogon secure channel connections" group policy after the third-party Netlogon client has been updated. To better understand the risk of configuring machine accounts to be allowed to use vulnerable Netlogon secure channel connections, please visit https://go.microsoft.com/fwlink/?linkid=2133485. %n%n Machine SamAccountName: %1 %n Domain: %2 %n Account Type: %3 %n Machine Os: %4 %n Machine Os Build Version: %5 %n Machine Os Service Pack: %6 <The Netlogon service allowed a vulnerable Netlogon secure channel connection because the trust account is allowed in the "Domain controller: Allow vulnerable Netlogon secure channel connections" group policy. %n%nWarning: Using vulnerable Netlogon secure channels will expose Active Directory forests to attack. To protect your Active Directory forests from attack, all trusts must use secure RPC with Netlogon secure channel. Remove a trust account from "Domain controller: Allow vulnerable Netlogon secure channel connections" group policy after the third-party Netlogon client on the domain controllers have been updated. To better understand the risk of configuring trust accounts to be allowed to use vulnerable Netlogon secure channel connections, please visit https://go.microsoft.com/fwlink/?linkid=2133485. %n%n Account Type: %1 %n Trust Name: %2 %n Trust Target: %3 %n Client IP Address: %4 The Netlogon service allowed one or more unsecure pass-through NTLM authentication requests from trusted domains and/or forests during the most recent event throttling window. These unsecure requests would normally be blocked but were allowed to proceed due to the current trust configuration.%n %n Warning: Allowing unsecure pass-through authentication requests will expose your Active Directory forest to attack. For more information about this issue please visit https://go.microsoft.com/fwlink/?linkid=276811&.%n %n Count of unsecure requests allowed due to administrative override: %1%n The Netlogon service blocked one or more unsecure pass-through NTLM authentication requests from trusted clients, domains, and/or forests during the most recent event throttling window. For more information about this issue, including how to enable more verbose logging, please visit https://go.microsoft.com/fwlink/?linkid=276811&.%n %n Count of unsecure requests blocked: %1%n The Netlogon service allowed an unsecure pass-through NTLM authentication request from a trusted client, domain, or forest. This unsecure request would normally be blocked but was allowed to proceed due to the current trust configuration.%n %n Warning: Allowing unsecure pass-through authentication requests will expose your Active Directory forest to attack. For more information about this issue please visit https://go.microsoft.com/fwlink/?linkid=276811&.%n %n Account name: %1%n Trust name: %2%n Trust type: %3%n Client IP Address: %4%n Block reason: %5%n Resource server Netbios name: %6%n Resource server DNS name: %7%n Resource domain Netbios name: %8%n Resource domain DNS name: %9%n The Netlogon service blocked an unsecure pass-through NTLM authentication requests from a trusted client, domain, or forest. For more information, please visit https://go.microsoft.com/fwlink/?linkid=276811&. %n%n Account name: %1%n Trust name: %2%n Trust type: %3%n Client IP Address: %4%n Block reason: %5%n Resource server Netbios name: %6%n Resource server DNS name: %7%n Resource domain Netbios name: %8%n Resource domain DNS name: %9%n 4VS_VERSION_INFOP%P%?StringFileInfo040904B0LCompanyNameMicrosoft CorporationJFileDescriptionNet Messages DLL1FileVersion6.3.9600.20622 (winblue_ltsb_escrow.220926-1736)6 InternalNamenetmsg.DLL.LegalCopyright Microsoft Corporation. All rights reserved.FOriginalFilenamenetmsg.DLL.MUIj%ProductNameMicrosoft Windows Operating SystemBProductVersion6.3.9600.20622DVarFileInfo$Translation PADD