Mini Kabibi Habibi

Current Path : C:/Windows/System32/en-US/

Current File : C:/Windows/System32/en-US/mprmsg.dll.mui

MZ����@��� �!�L�!This program cannot be run in DOS mode.

$5�<�q�R�q�R�q�R�e���p�R�e�P�p�R�Richq�R�PEL�!�

�2o@ ��8.rdata�@@.rsrc� �@@�s��
T88�s��$��8.rdata8x.rdata$zzzdbg p.rsrc$01p!`�.rsrc$02 Ft�T�`�V{�ĳ ֙��L�� ��äs��`�0�H�h��������������� 0 @ Ph!�� "~��"��P'�������MUI����Lk�f�v}a�S0�-����f~.�59D�(7�YQ���MUIen-USInternalLoopbackTroubleshoot VPN related issuesPARAS Asynchronous Media DriverRemote Access NDIS TAPI DriverRemote Access NDIS WAN DriverWAN Miniport (IrDA)WAN Miniport (IrDA Modem)WAN Miniport (L2TP)WAN Miniport (PPTP)Remote Access PPPOE DriverGAllows you to securely connect to a private network using the Internet.GAllows you to securely connect to a private network using the Internet.]Provides the ability to connect a host to a Remote Access Concentrator that supports RFC2516.Remote Access IP ARP DriverRemote Access IPv6 ARP DriverIP Traffic Filter Driver$Remote Access LEGACY NDIS WAN Driver%Point to Point Protocol Over EthernetXmT��������!N&N��)N-N��0N0N��2NFN��JNONSNhN�oNrN,&tNxNP*zN~Nl2�N�N�6�N�N�7�N�NX>�N�N�B�N�N@F�N�NG�N�N<H�N�N$T�N�N�T�N�N�g�N�N�m�NOloO0O<�2ODO�88H���`�@An operation is pending.%0

XAn invalid port handle was detected.%0

TThe specified port is already open.%0

PThe caller's buffer is too small.%0

XIncorrect information was specified.%0

XThe specified port is not connected.%0

dA device was specified that does not exist.%0

pA device type was specified that does not exist.%0

PAn invalid buffer was specified.%0

hA route was specified that is not allocated.%0

PThe specified port was not found.%0

TAn asynchronous request is pending.%0

�The modem (or other connecting device) is already disconnecting.%0

LThe specified port is not open.%0

�A connection to the remote computer could not be established, so the port used for this connection was closed.%0

lThe system could not open the phone book file.%0

lThe system could not load the phone book file.%0

�The system could not find the phone book entry for this connection.%0

pThe system could not update the phone book file.%0

�The system found invalid information in the phone book file.%0

@A key could not be found.%0

�The connection was terminated by the remote computer before it could be completed.%0

pThe connection was closed by the remote computer.%0

�The modem (or other connecting device) was disconnected due to hardware failure.%0

�The user disconnected the modem (or other connecting device).%0

`An incorrect structure size was detected.%0

�The modem (or other connecting device) is already in use or is not configured properly.%0

DThere was an unknown error.%0

�The device attached to the port is not the one expected.%0

�The remote server is not responding in a timely fashion.%0

dThere was an internal authentication error.%0

�The account is not permitted to log on at this time of day.%0

@The account is disabled.%0

dThe password for this account has expired.%0

pThe account does not have permission to dial in.%0

�The modem (or other connecting device) has reported an error.%0

�There was an unrecognized response from the modem (or other connecting device).%0

�A macro required by the modem (or other connecting device) was not found in the device.INF file.%0

�A command or response in the device.INF file section refers to an undefined macro.%0

�The <message> macro was not found in the device.INF file section.%0

�The <defaultoff> macro in the device.INF file section contains an undefined macro.%0

`The device.INF file could not be opened.%0

�The device name in the device.INF or media.INI file is too long.%0

xThe media.INI file refers to an unknown device name.%0

�The device.INF file contains no responses for the command.%0

`The device.INF file is missing a command.%0

�There was an attempt to set a macro not listed in device.INF file section.%0

xThe media.INI file refers to an unknown device type.%0

PThe system has run out of memory.%0

�The modem (or other connecting device) is not properly configured.%0

�The modem (or other connecting device) is not functioning.%0

pThe system was unable to read the media.INI file.%0

LThe connection was terminated.%0

xThe usage parameter in the media.INI file is invalid.%0

�The system was unable to read the section name from the media.INI file.%0

�The system was unable to read the device type from the media.INI file.%0

�The system was unable to read the device name from the media.INI file.%0

�The system was unable to read the usage from the media.INI file.%0

<The phone line is busy.%0

�A person answered instead of a modem (or other connecting device).%0

�The remote computer did not respond. To make sure that the server can be reached, ping the remote computer.%0

`The system could not detect the carrier.%0

<There was no dial tone.%0

�The remote connection was denied because the user name and password combination you provided is not recognized, or the selected authentication protocol is not permitted on the remote access server.%0

�There was a hardware failure in the modem (or other connecting device).%0

<ERROR_NOT_BINARY_MACRO%0

4ERROR_DCB_NOT_FOUND%0

TThe state machines are not started.%0

\The state machines are already started.%0

\The response looping did not complete.%0

�A response keyname in the device.INF file is not in the expected format.%0

�The modem (or other connecting device) response caused a buffer overflow.%0

�The expanded command in the device.INF file is too long.%0

�The modem moved to a connection speed not supported by the COM driver.%0

hDevice response received when none expected.%0

�The connection needs information from you, but the application does not allow user interaction.%0

LThe callback number is invalid.%0

TThe authorization state is invalid.%0

pThere was an error related to the X.25 protocol.%0

@The account has expired.%0

0There was an error changing the password on the domain. The password might have been too short or might have matched a previously used password.%0

�Serial overrun errors were detected while communicating with the modem.%0

,The operation could not finish because it could not start the Remote Access Connection Manager service in time. Please try the operation again.%0

TNo active ISDN lines are available.%0

|The Remote Access Service IP configuration is unusable.%0

�No IP addresses are available in the static pool of Remote Access Service IP addresses.%0

�The connection was terminated because the remote computer did not respond in a timely manner.%0

A connection to the remote computer could not be established. You might need to change the network settings for this connection.%0

�A connection to the remote access server was not made because the remote access server did not respond.%0

�Invalid data was received from the remote computer. This data was ignored.%0

�The phone number, including prefix and suffix, is too long.%0

�The IPX protocol cannot be used for dialing out on more than one modem (or other connecting device) at a time.%0

XThe system cannot find an IP adapter.%0

�SLIP cannot be used unless the IP protocol is installed.%0

LThe protocol is not configured.%0

�Your computer and the remote computer could not agree on PPP control protocols.%0

�A connection to the remote computer could not be completed. You might need to adjust the protocols on this computer.%0

hThe PPP link control protocol was terminated.%0

pThe requested address was rejected by the server.%0

xThe remote computer terminated the control protocol.%0

<Loopback was detected.%0

�The remote connection was not made because the remote access server did not assign an IP address.%0

The authentication protocol required by the remote server cannot use the stored password. Redial, entering the password explicitly.%0

XAn invalid dialing rule was detected.%0

�The local computer does not support the required data encryption type.%0

�The remote computer does not support the required data encryption type.%0

�The destination address or phone number is either invalid or not present.%0

�A syntax error was encountered while processing a script.%0

�The connection could not be disconnected because the user does not have the required permission to disconnect.%0

pThe system could not find the multi-link bundle.%0

�The system cannot perform automated dial because this connection has a custom dialer specified.%0

`This connection is already being dialed.%0

�Remote Access Services could not be started automatically. Additional information is provided in the event log.%0

TNo smart card reader is installed.%0

@Internet Connection Sharing cannot be enabled. A LAN connection is already configured with the IP address that is required for automatic IP addressing.%0

hA certificate could not be found. Connections that use the L2TP protocol over IPSec require the installation of a machine certificate, also known as a computer certificate.%0

Internet Connection Sharing cannot be enabled. The LAN connection selected as the private network has more than one IP address configured. Please reconfigure the LAN connection with a single IP address before enabling Internet Connection Sharing.%0

�The connection attempt failed because of failure to encrypt data.%0

dThe specified destination is not reachable.%0

xThe remote computer rejected the connection attempt.%0

�The connection attempt failed because the network is busy.%0

�The remote computer's network hardware is incompatible with the type of call requested.%0

�The connection attempt failed because the destination number has changed.%0

�The connection attempt failed because of a temporary failure. Try connecting again.%0

hThe call was blocked by the remote computer.%0

�The call could not be connected because the remote computer has invoked the Do Not Disturb feature.%0

�The connection attempt failed because the modem (or other connecting device) on the remote computer is out of order.%0

�It was not possible to verify the identity of the server.%0

|An attempted function is not valid for this connection.%0

�Internet Connection Sharing (ICS) and Internet Connection Firewall (ICF) cannot be enabled because Routing and Remote Access has been enabled on this computer. To enable ICS or ICF, first disable Routing and Remote Access. For more information about Routing and Remote Access, ICS, or ICF, see Help and Support.%0

Internet Connection Sharing cannot be enabled. The LAN connection selected as the private network is either not present, or is disconnected from the network. Please ensure that the LAN adapter is connected before enabling Internet Connection Sharing.%0

�You cannot dial using this connection at logon time, because it is configured to use a user name different than the one on the smart card. If you want to use it at logon time, you must configure it to use the user name on the smart card.%0

�You cannot dial using this connection at logon time, because it is not configured to use a smart card. If you want to use it at logon time, you must edit the properties of this connection so that it uses a smart card.%0

The connection attempt failed because there is no valid machine certificate on your computer for security authentication.%0

�The L2TP connection attempt failed because the security layer could not authenticate the remote computer.%0

The L2TP connection attempt failed because the security layer could not negotiate compatible parameters with the remote computer.%0

4The L2TP connection attempt failed because the security layer encountered a processing error during initial negotiations with the remote computer.%0

�The L2TP connection attempt failed because certificate validation of the remote computer failed.%0

�The L2TP connection attempt failed because security policy for the connection was not found.%0

�The L2TP connection attempt failed because security negotiation timed out.%0

�The L2TP connection attempt failed because an error occurred while negotiating security.%0

�The Framed Protocol RADIUS attribute for this user is not PPP.%0

�The remote connection request was denied because the VPN tunnel type being used is not allowed.%0

�The Service Type RADIUS attribute for this user is neither Framed nor Callback Framed.%0

�A connection to the remote access server was not made because the modem was not found.%0

�A certificate could not be found that can be used with this Extensible Authentication Protocol.%0

�Internet Connection Sharing (ICS) cannot be enabled due to an IP address conflict on the network. ICS requires the host be configured to use 192.168.137.1. Please ensure that no other client on the network is configured to use 192.168.137.1.%0

The remote connection was not made because the attempted VPN tunnels failed. The VPN server might be unreachable. If this connection is attempting to use an L2TP/IPsec tunnel, the security parameters required for IPsec negotiation might not be configured properly.%0

4This connection is configured to validate the identity of the access server, but Windows cannot verify the digital certificate sent by the server.%0

�The card supplied was not recognized. Please check that the card is inserted correctly, and fits tightly.%0

�The PEAP configuration stored in the session cookie does not match the current session configuration.%0

�The PEAP identity stored in the session cookie does not match the current identity.%0

�You cannot dial using this connection at logon time, because it is configured to use logged on user's credentials.%0

@The VPN connection between your computer and the VPN server could not be completed. The most common cause for this failure is that at least one Internet device (for example, a firewall or a router) between your computer and the VPN server is not configured to allow Generic Routing Encapsulation (GRE) protocol packets. If the problem persists, contact your network administrator or Internet Service Provider.%0

The network connection between your computer and the VPN server was interrupted. This can be caused by a problem in the VPN transmission and is commonly the result of internet latency or simply that your VPN server has reached capacity. Please try to reconnect to the VPN server. If this problem persists, contact the VPN administrator and analyze quality of network connectivity.%0

�The network connection between your computer and the VPN server could not be established because the remote server refused the connection. This is typically caused by a mismatch between the server's configuration and your connection settings. Please contact the remote server's Administrator to verify the server configuration and your connection settings.%0

TThe network connection between your computer and the VPN server could not be established because the remote server is not responding. This could be because one of the network devices (e.g, firewalls, NAT, routers, etc) between your computer and the remote server is not configured to allow VPN connections. Please contact your Administrator or your service provider to determine which device may be causing the problem.%0

�A network connection between your computer and the VPN server was started, but the VPN connection was not completed. This is typically caused by the use of an incorrect or expired certificate for authentication between the client and the server. Please contact your Administrator to ensure that the certificate being used for authentication is valid.%0

�The network conection between your computer and the VPN server could not be established because the remote server is not responding. This is typically caused by a pre-shared key problem between the client and server. A pre-shared key is used to guarantee you are who you say you are in an IP Security (IPSec) communication cycle. Please get the assistance of your administrator to determine where the pre-shared key problem is originating.%0

�The connection was prevented because of a policy configured on your RAS/VPN server. Specifically, the authentication method used by the server to verify your username and password may not match the authentication method configured in your connection profile. Please contact the Administrator of the RAS server and notify them of this error.%0

�You have attempted to establish a second broadband connection while a previous broadband connection is already established using the same device or port. Please disconnect the earlier connection and then reestablish the connection.%0

�The underlying Ethernet connectivity required for the broadband connection was not found. Please install and enable the Ethernet adapter on your computer via the Network Connections folder before attempting this connection.%0

�The broadband network conection could not be established on your computer because the remote server is not responding. This could be caused by an invalid value for the 'Service Name' field for this connection. Please contact your Internet Service Provider and inquire about the correct value for this field and update it in the Connection Properties.%0

�A feature or setting you have tried to enable is no longer supported by the remote access service.%0

pCannot delete a connection while it is connected.%0

|The Network Access Protection (NAP) enforcement client could not create system resources for remote access connections. Some network services or resources might not be available. If the problem persists, disconnect and retry the remote access connection or contact the administrator for the remote access server.

hThe Network Access Protection Agent (NAPAgent) service has been disabled or is not installed on this computer. Some network services or resources might not be available. If the problem persists, disconnect and retry the remote access connection or contact the administrator for the remote access server.

�The Network Access Protection (NAP) enforcement client failed to register with the Network Access Protection Agent (NAPAgent) service. Some network services or resources might not be available. If the problem persists, disconnect and retry the remote access connection or contact the administrator for the remote access server.

�The Network Access Protection (NAP) enforcement client was unable to process the request because the remote access connection does not exist. Retry the remote access connection. If the problem persists, make sure that you can connect to the Internet, and then contact the administrator for the remote access server.

The Network Access Protection (NAP) enforcement client did not respond. Some network services or resources might not be available. If the problem persists, disconnect and retry the remote access connection or contact the administrator for the remote access server.

\Received Crypto-Binding TLV is invalid.%0

TCrypto-Binding TLV is not received.%0

0The remote connection was not made because Point-to-Point Tunneling Protocol (PPTP) is incompatible with IPv6. Use any other tunneling protocol. %0

�EAPTLS validation of the cached credentials failed. Please discard

cached credentials.

XThe VPN connection cannot be completed because the 'IKE and AuthIP IPSec Keying Modules' service and/or the 'Base Filtering Engine' service is not running. These services are required to establish the connection. Please ensure that these services have been started before dialing the connection.

|The connection was terminated because of idle timeout.%0

�The modem (or other connecting device) was disconnected due to link failure.%0

|The connection was terminated because user logged off.%0

�The connection was terminated because user switch happened.%0

xThe connection was terminated because of hibernation.%0

�The connection was terminated because the system got suspended.%0

�The connection was terminated because Remote Access Connection manager stopped.%0

The L2TP connection attempt failed because the security layer could not authenticate the remote computer. This could be because one or more fields of the certificate presented by the remote server could not be validated as belonging to the target destination.

�The Network Access Protection (NAP) health state of the computer cannot be determined. Contact your administrator to verify that the NAP enforcement client is enabled, the NAP Agent service is running, and NAP is enforced in the Protected Extensible Authentication Protocol (PEAP) properties of the remote access connection.

4Invalid Tunnel ID.%0

�Another Update connection request is in progress. RAS allows only one Update Connection request at a time.%0

Negotiating using configured protocol is disable. Edit connection properties and select different protocol for negotiation and try again.%0

XInternal address negotiation failed.%0

|Client has to request a Internal IPv4 or IPv6 address.%0

XTraffic Selectors negotiation failed.%0

\Mobility is disabled for this connection.

LThe VPN Connection is still connecting or reauthenticating because of Quarantine state change. Initiate mobike update only when connection state is 'Connected'.

�Server rejected client authentication, due unexpected TLV or value mismatch for a TLV.

�Either VPN Destination preference is not selected by the user or it is no longer valid.

\Cached smart card credential is invalid.

�VPN connection attempt failed due to internal error occurred while adding cookies to the Secure Socket Tunneling Protocol (SSTP). Please see the System Event Log for the detailed information.

�The PEAP inner method attributes stored in the cookie is invalid

The Extensible Authentication Protocol type required for authentication of the remote access connection is not installed on your computer.

�The Extensible Authentication Protocol type configured on the remote access connection does not support single sign-on.

The Extensible Authentication Protocol type configured on the remote access connection does not support the requested operation.

�The remote access connection completed, but authentication failed because the certificate that authenticates the client to the server is not valid. Ensure that the certificate used for authentication is valid.

\The remote access connection completed, but authentication failed because the certificate that authenticates the client to the server is expired. Renew the certificate.

,The remote access connection completed, but authentication failed because the certificate that authenticates the client to the server is revoked.

4The remote access connection completed, but authentication failed because of an error in the certificate that authenticates the client to the server.

8The remote access connection completed, but authentication failed because the certificate that the client uses to authenticate the server is not valid.

4The remote access connection completed, but authentication failed because the certificate that the client uses to authenticate the server is expired.

4The remote access connection completed, but authentication failed because the certificate that the client uses to authenticate the server is revoked.

<The remote access connection completed, but authentication failed because of an error in the certificate that the client uses to authenticate the server.

�The remote access connection completed, but authentication failed because a trusted root certificate that validates the user certificate was not found in the Trusted Root Certification Authorities certificate store.

PThe remote access connection completed, but authentication failed because the trusted root certificate that is used to validate the user certificate is not valid.

�The remote access connection completed, but authentication failed because the certificate in the Trusted Root Certification Authorities certificate store that authenticates the user certificate is expired. Renew the certificate.

�The remote access connection completed, but authentication failed because a certificate that validates the server certificate was not found in the Trusted Root Certification Authorities certificate store.

�The remote zccess connection completed, but authentication failed because the certificate in the Trusted Root Certification Authorities certificate store that validates the server certificate is not valid.

8The remote access connection completed, but authentication failed because the certificate on the server computer does not have a server name specified.

�The PEAP outer identity is not same as the inner identity when identity privacy is turned OFF.

�The remote connection was not made because the name of the remote access server did not resolve.

hPassword provided for certificate is not valid.

�The Interface could not be enabled as more than one interface with same destination has been created with authentication method as Pre Shared Key. Change the destination/auth method and enable the interface.

8The Interface could not be enabled as no valid destination is found for it. Ensure that a valid/resolvable destination IP is configured and try again.

lThe configuration for the interface is not valid

DCouldn't connect to the VPN.

�Couldn't connect because we couldn't find a certificate for single sign-on. Please contact your support person.

�Couldn't connect because there was a problem with device compliance.

The app %1!ws! is required for this VPN connection. Please download it in the Microsoft Store or contact your IT administrators.

tThe connection requires an input state from the user.

DThe router is not running.%0

TThe interface is already connected.%0

�The specified protocol identifier is not known to the router.%0

pThe Demand-dial Interface Manager is not running.%0

�An interface with this name is already registered with the router.%0

�An interface with this name is not registered with the router.%0

LThe interface is not connected.%0

TThe specified protocol is stopping.%0

|The interface is connected and hence cannot be deleted.%0

hThe interface credentials have not been set.%0

|This interface is already in the process of connecting.%0

�An update of routing information on this interface is already in progress.%0

The interface confugration in invalid. There is already another interface that is connected to the same inteface on the remote router.%0

�A Remote Access Client attempted to connect over a port that was reserved for Routers only.%0

�A Demand Dial Router attempted to connect over a port that was reserved for Remote Access Clients only.%0

�The client interface with this name already exists and is currently connected.%0

XThe interface is in a disabled state.%0

�The authentication protocol was rejected by the remote peer.%0

�There are no authentication protocols available for use.%0

�The connection could not be established because the authentication protocol used by the RAS/VPN server to verify your username and password could not be matched with the settings in your connection profile.%0

�The remote account does not have Remote Access permission.%0

LThe remote account has expired.%0

LThe remote account is disabled.%0

�The remote account is not permitted to logon at this time of day.%0

�Access was denied to the remote peer because username and/or password is invalid on the domain.%0

�There are no routing enabled ports available for use by this demand dial interface.%0

pThe port has been disconnected due to inactivity.%0

hThe interface is not reachable at this time.%0

hThe Demand Dial service is in a paused state.%0

�The interface has been disconnected by the administrator.%0

�The authentication server did not respond to authentication requests in a timely fashion.%0

�The maximum number of ports allowed for use in the multilinked connection has been reached.%0

�The connection time limit for the user has been reached.%0

�The maximum limit on the number of LAN interfaces supported has been reached.%0

�The maximum limit on the number of Demand Dial interfaces supported has been reached.%0

�The maximum limit on the number of Remote Access clients supported has been reached.%0

xThe port has been disconnected due to the BAP policy.%0

�Because another connection of your type is in use, the incoming connection cannot accept your connection request.%0

lNo RADIUS servers were located on the network.%0

PAn invalid response was received from the RADIUS authentication server.

Make sure that the case sensitive secret pasword for the RADIUS server is set correctly.%0

tYou do not have permission to connect at this time.%0

�You do not have permission to connect using the current device type.%0

�The connection could not be established because the authentication method used by your connection profile is not permitted for use by an access policy configured on the RAS/VPN server. Specifically, this could be due to configuration differences between the authentication method selected on the RAS/VPN server and the access policy configured for it.%0

LBAP is required for this user.%0

xThe interface is not allowed to connect at this time.%0

�The saved router configuration is incompatible with the current router.%0

RemoteAccess has detected older format user accounts that will not be

migrated automatically. To migrate these manually, run XXXX.

tThe transport is already installed with the router.%0

�Received invalid signature length in packet from RADIUS server.%0

�Received invalid signature in packet from RADIUS server.%0

�Did not receive signature along with EAPMessage from RADIUS server.%0

�Received packet with invalid length or Id from RADIUS server.%0

�Received packet with attribute with invalid length from RADIUS server.%0

dReceived invalid packet from RADIUS server.%0

�Authenticator does not match in packet from RADIUS server.%0

�Routing and Remote access server is either not configured or not running.%0

�Cannot load the NetBIOS gateway DLL component because of the following error: %1

PCannot access registry key values.

\Cannot enumerate Registry key values. %1

LParameter %1 has an invalid type.

�Cannot enumerate the Remote Access Connection Manager ports. %1

The Remote Access Service is not configured to receive calls or all ports configured for receiving calls are in use by other applications.

�The user connected to port %1 has been disconnected because there is not enough memory available in the system.

�The user connected to port %1 has been disconnected due to a system error.

�The user connected to port %1 has been disconnected due to a critical network error on the local network.

�The user connected to port %1 has been disconnected due to a critical network error on the async network.

�The communication device attached to port %1 is not functioning.

The user connected to port %1 has been disconnected because there was a transport-level error during the authentication conversation.

�Cannot reset the network adapter for LANA %1. The error code is the data.

�Remote Access Server Security Failure. Cannot locate the computer name. GetComputerName call has failed.

�Remote Access Server Security Failure. Cannot add the name for communication with the security agent on LANA %1.

�Remote Access Server Security Failure. Cannot access the network adapter address on LANA %1.

Remote Access Server Security Failure. The security agent has rejected the Remote Access server's call to establish a session on LANA %1.

@Remote Access Server Security Failure. The security agent has rejected the Remote Access server's request to start the service on this computer on LANA %1.

XRemote Access Server Security Failure. A network error has occurred when trying to establish a session with the security agent on LANA %1. The error code is the data.

�The user connected to port %1 has been disconnected because there are no operating system resources available.

�The user connected to port %1 has been disconnected because of a failure to lock user memory.

�Remote Access Connection Manager failed to start because NDISWAN could not be opened.

�Remote Access Connection Manager failed to start because it could not initialize the security attributes. Try restarting the Remote Access Connection Manager service. If the problem persists, contact the system administrator. %1

�Remote Access Connection Manager failed to start because no endpoints were available. Try restarting the Remote Access Connection Manager service. If the problem persists, contact the system administrator.

DRemote Access Connection Manager failed to start because it could not load one or more communication DLLs. Ensure that your communication hardware is installed and then restart the Remote Access Connection Manager service. If the problem persists, contact the system administrator. %1

�Remote Access Connection Manager failed to start because it could not locate port information from media DLLs. %1

�Remote Access Connection Manager failed to start because it could not access protocol information from the Registry. %1

�Remote Access Connection Manager failed to start because it could not register with the local security authority. Try restarting the Remote Access Connection Manager service. If the problem persists, contact the system administrator. %1

�Remote Access Connection Manager failed to start because it could not create shared file mapping. Try restarting the Remote Access Connection Manager service. If the problem persists, contact the system administrator. %1

�Remote Access Connection Manager failed to start because it could not create buffers. Try restarting the Remote Access Connection Manager service. If the problem persists, contact the system administrator. %1

�Remote Access Connection Manager failed to start because it could not access resources. Try restarting the Remote Access Connection Manager service. If the problem persists, contact the system administrator. %1

�Remote Access Connection Manager service failed to start because it could not start worker threads. Try restarting the Remote Access Connection Manager service. If the problem persists, contact the system administrator.

�Remote Access Server Configuration Error. Cannot find the LANA numbers for the network adapters. Remote clients connecting with the NBF protocol will only be able to access resources on the local machine.

�The Remote Access server cannot allocate a route for the user connected on port %1 because of the following error: %2 The user has been disconnected. Check the configuration of your Remote Access Service.

�Cannot allocate memory in the admin support thread for the Remote Access Service.

�Cannot create an instance thread in the admin support thread for the Remote Access Service.

�Cannot create a named pipe instance in the admin support thread for the Remote Access Service.

�General named pipe failure occurred in the admin support thread for the Remote Access Service.

DAn invalid request was sent to the admin support thread for the Remote Access Service, possibly from a down-level admin tool. The request was not processed.

�The user connected to port %1 has been disconnected because an internal authentication error occurred.

�The NetBIOS gateway has been configured to access the network but there are no network adapters available. Remote clients connecting with the NBF protocol will only be able to access resources on the local machine.

�The user %1 established a NetBIOS session between the remote workstation %2 and the network server %3.

Remote Access Service failed to start because the Remote Access Connection Manager failed to initialize because of the following error: %1

�Cannot add the remote computer name %1 on LANA %2 for the client being connected on port %3. The error code is the data.

Cannot delete the remote computer name %1 from LANA %2 for the client being disconnected on port %3. The error code is the data.

�Cannot add the remote computer group name %1 on LANA %2. The error code is the data.

�Cannot delete the remote computer group name %1 from LANA %2. The error code is the data.

lThe modem on %1 moved to an unsupported BPS rate.

�The serial driver could not allocate adequate I/O queues. This may result in an unreliable connection.

hRemote Access Connection Manager could not reopen biplex port %1. This port will not be available for calling in or calling out. Restart all Remote Access Service components.

�Internal Error: Disconnect operation on %2 completed with an error. %1

�Remote Access Connection Manager failed to start because the Protocol engine [%2] failed to initialize. %1

�Remote Access service failed to start because the all Protocol engine failed to initialize. %1

�The Remote Access Gateway Proxy could not create a process.

�The Remote Access Gateway Proxy could not create a named pipe.

�The Remote Access Gateway Proxy could not establish a named pipe connection with the Remote Access Supervisor Proxy.

�A general error occurred reading from the named pipe in the Remote Access Proxy.

�Cannot open or obtain information about the PPP key or one of its subkeys. %1

�Point to Point Protocol engine was unable to load the %1 module. %2

�The Point to Point Protocol module %1 returned an error while initializing. %2

�The Point to Point Protocol failed to load the required PAP and/or CHAP authentication modules.

�The software version of the user %1\%2 connected on port %3 is unsupported. The line has been disconnected.

`The server machine is configured to require data encryption. The machine for user %1\%2 connected on port %3 does not support encryption. The line has been disconnected.

Remote Access Server Security Failure. Could not reset lana %1 (the error code is the data). Security check not performed.

�The Remote Access Server could not reset lana %1 (the error code is the data) and will not be active on it.

<The Remote Access Server will stop using IP Address %1 (either because it was unable to renew the lease from the DHCP Server, the administrator switched between static address pool and DHCP addresses, or the administrator changed to a different network for DHCP addresses). All connected users using IP will be unable to access network resources. Users can re-connect to the server to restore IP connectivity.

�The Remote Access Server was unable to renew the lease for IP Address %1 from the DHCP Server. The user assigned with this IP address will be unable to access network resources using IP. Re-connecting to the server will restore IP connectivity.

�The Remote Access Server was unable to acquire an IP Address from the DHCP Server to assign to the incoming user.

TThe Remote Access Server was unable to acquire an IP Address from the DHCP Server to be used on the Server Adapter. Incoming user will be unable to connect using IP.

�The Remote Access Server acquired IP Address %1 to be used on the Server Adapter.

�A general error occurred writing to the named pipe in the Remote Access Proxy.

�Cannot open the RAS security host Registry key. The following error occurred: %1

�Cannot load the Security host module component. The following error occurred: %1

The user %1 has connected and failed to authenticate with a third party security on port %2. The line has been disconnected.

8The user connected to port %1 has been disconnected because the following internal authentication error occurred in the third party security module: %2

<The user was authenticated as %1 by the third party security host module but was authenticated as %2 by the RAS security. The user has been disconnected.

�A user was unable to connect on port %1. The NetBIOS protocol has been disabled for the Remote Access Server.

TCannot access Registry value for %1.

PCannot access the Registry key %1.

�Using the default value for Registry parameter %1 because the value given is not in the legal range for the parameter.

\Cannot enumerate keys of Registry key %1.

0Unable to load %1.

@Memory allocation failure.

�Unable to load the interface %1 from the registry. The following error occurred: %2

RoutingDomainID- %1: Unable to add the interface %2 with the Router Manager for the %3 protocol. The following error occurred: %4

RoutingDomainID- %1: Unable to remove the interface %2 with the Router Manager for the %3 protocol. The following error occurred: %4

XUnable to open the port %1 for use. %2

�An error occurred in the Point to Point Protocol module on port %1 while trying to initiate a connection. %2

xRoutingDomainID- %1: A Demand Dial connection to the remote interface %2 on port %3 was successfully initiated but failed to complete successfully because of the following error: %4

�Cannot open the RAS third party administration host DLL Registry key. The following error occurred: %1

�Cannot load the RAS third party administration DLL component. The following error occurred: %1

�The Service will not accept calls. No protocols were configured for use.

<RoutingDomainID- %1: A Demand Dial persistent connection to the remote interface %2 failed to be initiated successfully. The following error occurred: %3

A packet from %1 destined to %2 over protocol 0x%3 caused interface %4 to be brought up. The first %5 bytes of the packet are in the data.

�RoutingDomainID- %1: The Demand Dial interface %2 was not loaded. The router was not started in in Demand Dial mode.

�Remote Access Connection Manager failed to start because the RAS RPC module failed to initialize. %1

(RoutingDomainID- %1: A Demand Dial connection to the remote interface %2 failed to be initiated successfully. The following error occurred: %3

�Unable to load the interface %1 from the registry. There are no routing enabled ports available for use by this demand dial interface. Use the Routing and RemoteAccess Administration tool to configure this interface to use a device that is routing enabled. Stop and restart the router for this demand dial interface to be loaded from the registry.

The Demand-Dial interface %1 was not registered with the Router. Demand-Dial interfaces are not supported on a Windows NT Workstation.

$Cannot initialize the Remote Access and Router service to accept calls using the TCP/IP transport protocol. The following error occurred: %1

The RADIUS server %1 did not respond to the initial request. Please make sure that the server name or IP address and secret are correct.

�The Remote Access service failed to start because the Point to Point was not initialized successfully. %1

pThe RADIUS server name %1 could not be successfully resolved to an IP address. Please make sure that the name is spelled correctly and that the RADIUS server is running correctly.

�No global configuration was supplied to the IP Router Manager. Please rerun setup.

pUnable to add demand dial filters for interface %1

�The Control Protocol %1 in the Point to Point Protocol module %2 returned an error while initializing. %3

�The currently configured authentication provider failed to load and initialize successfully. %1

�The currently configured accounting provider failed to load and initialize successfully. %1

�The interface %1 could not be enabled for multicast. %2 will not be activated over this interface.

�A connection has been established on port %1 using interface %2, but no IP address was obtained.

�A connection has been established on port %1 using interface %2, but the remote side got no IP address.

�RoutingDomainID- %1: No IP address is available to hand out to the dial-in client.

�Could not retrieve the Remote Access Server's certificate due to the following error: %1

PUnable to contact a DHCP server. The Automatic Private IP Address %1 will be assigned to dial-in clients. Clients may be unable to access resources on the network.

�The user %1 has connected and failed to authenticate because of the following error: %2

�Failed to apply IP Security on port %1 because of error: %2. No calls will be accepted to this port.

�Multicast scope mismatch with %1: Locally-configured name "%2", Remotely-configured name "%3".

�Multicast scope address mismatch for scope "%1", Locally-configured range is %4-%5, Remotely-configured range is %2-%3

�Possible leaky multicast Local Scope detected between this machine and %1, since a boundary appears to exist for %2, but not for the local scope. If this warning continues to occur, a problem likely exists.

�Multicast scope '%1' is non-convex, since border router %2 appears to be outside.

�A leak was detected in multicast scope '%1'. One of the following routers is misconfigured: %2

lInterface %1 is unreachable because of reason %2.

HInterface %1 is now reachable.

,RoutingDomainID- %1: Interface %2 is unreachable because there are no modems (or other connecting devices) available for use by this interface.

�RoutingDomainID- %1: Interface %2 is unreachable because the connection attempt failed.

�RoutingDomainID- %1: Interface %2 is unreachable because it has been administratively disabled.

�RoutingDomainID- %1: Interface %2 is unreachable because the Routing and RemoteACcess service is in a paused state.

@RoutingDomainID- %1: Interface %2 is unreachable because it is not allowed to connect at this time. Check the dial-out hours configured on this interface.

�RoutingDomainID- %1: Interface %2 is unreachable because it is not currently connected to the network.

�RoutingDomainID- %1: Interface %2 is unreachable because the network card for this interface has been removed.

pRoutingDomainID- %1: Interface %2 is now reachable.

�Because no certificate has been configured for clients dialing in with EAP-TLS, a default certificate is being sent to user %1. Please go to the user's Remote Access Policy and configure the Extensible Authentication Protocol (EAP).

�Because the certificate that was configured for clients dialing in with EAP-TLS was not found, a default certificate is being sent to user %1. Please go to the user's Remote Access Policy and configure the Extensible Authentication Protocol (EAP).

�A certificate could not be found. Connections that use the L2TP protocol over IPsec require the installation of a machine certificate, also known as a computer certificate. No L2TP calls will be accepted.

�CoID=%1: An error occurred while configuring IP packet filters for user %2 over port %3.

�An invalid response was received from the RADIUS server %1. %2

XRas Audio Acceleration failed to %1. %2

dChoosing radius server %1 for authentication.

lIPinIP tunnel interfaces are no longer supported

xAn error occurred while trying to revert impersonation.

�Cannot load the Security host module component. The following error occurred: %1 is not a valid win32 application.

Cannot load the RAS third party administration DLL component. The following error occurred: %1 is not a valid win32 application.

PIPX routing is no longer supported.

|Disk full. Deleted older logfile %1 to create free space.

�Disk full. Could not delete older logfile %1 to create free space.

�Disk full. Could not find older logfile to delete and create free space.

xA connection between the VPN server and the VPN client %1 has been established, but the VPN connection cannot be completed. The most common cause for this is that a firewall or router between the VPN server and the VPN client is not configured to allow Generic Routing Encapsulation (GRE) packets (protocol 47).

�The Network Access Protection (NAP) enforcement client could not start PPP renegotiation on the following remote access connection: %d. Some network services or resources might not be available. If the problem persists, disconnect and retry the remote access connection or contact the administrator for the remote access server.

The request sent to the Network Access Protection Agent (NAPAgent) failed. Some network services or resources might not be available. If the problem persists, disconnect and retry the remote access connection or contact the administrator for the remote access server.

�The Network Access Protection (NAP) enforcement client received an invalid request for the following remote access connection: %d. The connection does not exist. Retry the remote access connection. If the problem persists, make sure that you can connect to the Internet, and then contact the administrator for the remote access server.

tThe Network Access Protection (NAP) enforcement client received an invalid request for the remote access connection. Some network services or resources might not be available. If the problem persists, disconnect and retry the remote access connection or contact the administrator for the remote access server.

�The IAS/RADIUS server has passed an invalid value to the server running Routing and Remote Access for the following RADIUS attribute: Attribute Type %1, Vendor ID %2, Vendor specific type %3. Use the netsh ras set trace command to enable packet tracing. Ensure that the RADIUS packets conform to the standards specified in RFC 2548.

<The Routing and Remote Access service could not start. The most common reason could be because %1 protocol is not installed on the remote access server.

�An error occurred while trying to disable %1 packet filtering for Routing and Remote Access service.

�An error occurred while trying to enable %1 packet filtering for Routing and Remote Access service.

%1 packet filtering has been disabled. Static filters configured for Routing and Remote Access service will not be applied.

�The connection to %1 made using device %2 was terminated. %3

CoId=%1: The user %2 has started dialing a %3 connection using a %4 connection profile named %5. The connection settings are: %6.

CoId=%1: The user %2 is trying to establish a link to the Remote Access Server for the connection named %3 using the following device: %4.

�CoId=%1: The user %2 has successfully established a link to the Remote Access Server using the following device: %3.

�CoId=%1: The link to the Remote Access Server has been established by user %2.

4CoId=%1: The user %2 has dialed a connection named %3 to the Remote Access Server which has successfully connected. The connection parameters are:%4.

�CoId=%1: The user %2 dialed a connection named %3 which has terminated. The reason code returned on termination is %4.

�CoId=%1: The user %2 dialed a connection named %3 which has failed. The error code returned on failure is %4.

xThe remote access connection with the correlation ID %1 has Network Access Protection (NAP)-Enforcement enabled on it. The corresponding NAP correlation ID for this connection is %2.

�The remote access connection with the correlation ID %1 received an unexpected/mismatched response to its Statement of Health (SoH) from the server. The NAP correlation ID for this transaction is %2.

�The connection from user %1 on port %2 has been disconnected because the Session Timeout received from the RADIUS server has expired. This connection received only an IPv6 address from the RRAS server and it is invalid to configure the MS-Quarantine-Session-Timeout attribute on the NPS server for IPv6-only connections.

�CoId=%1: Cannot receive initial frame on port %2 because of the following error: %3 The user has been disconnected.

�CoId=%1: The user connected to port %2 has been disconnected due to inactivity.

�CoId=%1: The user %2 has connected and failed to authenticate on port %3. The line has been disconnected.

�RoutingDomainID- %1: CoID=%2: The user %3 has connected and has been successfully authenticated on port %4.

�RoutingDomainID- %1: CoId=%2: The user %3 connected on port %4 on %5 at %6 and disconnected on %7 at %8. The user was active for %9 minutes %10 seconds. %11 bytes were sent and %12 bytes were received. The port speed was %13. The reason for disconnecting was %14. The tunnel used was %15. The quarantine state was %16.

4CoId=%1: The user connected to port %2 has been disconnected because the authentication process did not complete within the required amount of time.

(RoutingDomainID- %1: CoId=%2: The user %3 connected to port %4 has been disconnected because no network protocols were successfully negotiated.

�CoId=%1: The user %2 on port %3 was called back at the number %4.

�CoId=%1: The following error occurred in the Point to Point Protocol module on port: %2, UserName: %3. %4

�CoId=%1: The password for user %2\%3 connected on port %4 has expired. The line has been disconnected.

�CoId=%1: The account for user %2\%3 connected on port %4 has expired. The line has been disconnected.

CoId=%1: The account for user %2\%3 connected on port %4 does not have Remote Access privilege. The line has been disconnected.

CoId=%1: The Remote Access Server's attempt to callback user %2 on port %3 at %4 failed because of the following error: %5

�CoId=%1: Cannot receive initial data on port %2 because of the following error: %3 The user has been disconnected.

TCoId=%1: A user was unable to connect on port %2. No more connections can be made to this remote computer because the computer has exceeded its client license limit.

�CoId=%1: Cannot recognize initial frame received on port %2. The line has been disconnected.

�CoID=%1: The port %2 has been disconnected due to inactivity.

CoID=%1: The port %2 has been disconnected because the user reached the maximum connect time allowed by the administrator.

HRoutingDomainID- %1: CoID=%2: The user %3 has connected and has been successfully authenticated on port %4. Data sent and received over this link is encrypted.

\RoutingDomainID- %1: CoID=%2: The user %3 has connected and has been successfully authenticated on port %4. Data sent and received over this link is strongly encrypted.

�CoID=%1: The user %2 successfully established a connection to %3 using the device %4.

�CoID=%1: The connection to %2 made by user %3 using device %4 was disconnected.

�CoId=%1: The user %2 failed an authentication attempt due to the following reason: %3

�CoID=%1: The user %2, attempting to connect on %3, was disconnected because of the following reason: %4

�CoId=%1: The user %2 connected from %3 but failed an authentication attempt due to the following reason: %4

\RoutingDomainID- %1: CoID=%2: The user %3 connected on port %4 on %5 at %6 and disconnected on %7 at %8. The user was active for %9 minutes %10 seconds. %11 bytes were sent and %12 bytes were received. The reason for disconnecting was %13. The tunnel used was %14. The quarantine state was %15.

�RoutingDomainID- %1: CoID=%2: The user %3 connected on port %4 has been assigned address %5

�RoutingDomainID- %1: CoID=%2: The user with ip address %3 has disconnected

CoId=%1: Layer=%2: SubLayer=%3: The connection attempt failed on port: %4 because of the authentication protocol selected. Check to see if the authentication protocol is supported in the operating systems at the client and server ends of the connection

�CoId=%1: Successfully processed MOBIKE update for connection named '%2'. The new tunnel end points are %3.

�CoId=%1: Unable to process MOBIKE update for connection named '%2'. The error code returned is %3.

pCoId=%1: Disabling PPP AUTH for %2\\%3 on port %4.

�RoutingDomainID- %1: CoID=%2: The correlation ID on the server is %3.

TCoID=%1: Connection supports MOBIKE.

�RoutingDomainID- %1: Failed to enable IPv4 forwarding on interface %2 with error: %3.

�RoutingDomainID- %1: Failed to disable IPv4 forwarding on interface %2 with error: %3.

�RoutingDomainID- %1: Failed to plumb IKEv2 policies for one or more demand dial interfaces.

�Did not find the certificate configured to be used for IKEv2 local authentication.

\Failed to plumb the custom IKEv2 policy.

RoutingDomainID- %1: Did not find the PreSharedKey configured to be used for local or remote authentication for the IKEv2 connection.

,RoutingDomainID- %1: IPv4 routes are not added for the demand dial connection as IPv4 transport is not available on the corresponding interface.

,RoutingDomainID- %1: IPv6 routes are not added for the demand dial connection as IPv6 transport is not available on the corresponding interface.

�Disabling S2S interface %1 (RoutingDomain: %2) because either there is no destination IP configured or DNS resolution failed for the configured destination IP address. To enable this interface, configure destination IP address. If you are using FQDN, make sure it is getting resolved. Then try to enable the interface.

8%1 requires attention.

�Retrieving Max connections failed. MaxCon: %1. HResult: %2

Classic

<Microsoft-Windows-MPRMSG

�4VS_VERSION_INFO��
4aJ
4aJ?0StringFileInfo040904B0LCompanyNameMicrosoft Corporation~+FileDescriptionMulti-Protocol Router Service Messages DLLn'FileVersion10.0.19041.3636 (WinBuild.160101.0800):
InternalNameroutemsg.DLL�.LegalCopyright� Microsoft Corporation. All rights reserved.JOriginalFilenameroutemsg.DLL.MUIj%ProductNameMicrosoft� Windows� Operating SystemDProductVersion10.0.19041.3636DVarFileInfo$Translation �PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADD