| 20001 | Cannot load the NetBIOS gateway DLL component because of the following error: … | Operational | N | N |
| 20002 | Cannot access registry key values. | Operational | N | N |
| 20003 | Cannot enumerate Registry key values. | Operational | N | N |
| 20004 | Parameter param1 has an invalid type. | Operational | N | N |
| 20005 | Cannot enumerate the Remote Access Connection Manager ports. | Operational | N | N |
| 20006 | The Remote Access Service is not configured to receive calls or all ports … | Operational | N | N |
| 20007 | Cannot receive initial frame on port {param1} because of the following error: … | Operational | N | N |
| 20008 | The user connected to port {param1} has been disconnected due to inactivity. | Operational | N | N |
| 20009 | The user connected to port param1 has been disconnected because there is not … | Operational | N | N |
| 20010 | The user connected to port param1 has been disconnected due to a system error. | Operational | N | N |
| 20011 | The user connected to port param1 has been disconnected due to a critical … | Operational | N | N |
| 20012 | The user connected to port param1 has been disconnected due to a critical … | Operational | N | N |
| 20013 | The communication device attached to port param1 is not functioning. | Operational | N | N |
| 20014 | The user {param1} has connected and failed to authenticate on port {param2}. | Operational | N | N |
| 20015 | The user {param1} has connected and has been successfully authenticated on port … | Operational | N | N |
| 20016 | The user connected to port param1 has been disconnected because there was a … | Operational | N | N |
| 20018 | Cannot reset the network adapter for LANA param1. | Operational | N | N |
| 20019 | Remote Access Server Security Failure. | Operational | N | N |
| 20020 | Remote Access Server Security Failure. | Operational | N | N |
| 20021 | Remote Access Server Security Failure. | Operational | N | N |
| 20022 | Remote Access Server Security Failure. | Operational | N | N |
| 20023 | Remote Access Server Security Failure. | Operational | N | N |
| 20024 | Remote Access Server Security Failure. | Operational | N | N |
| 20025 | The user connected to port param1 has been disconnected because there are no … | Operational | N | N |
| 20026 | The user connected to port param1 has been disconnected because of a failure to … | Operational | N | N |
| 20027 | Remote Access Connection Manager failed to start because NDISWAN could not be … | Operational | N | N |
| 20028 | Remote Access Connection Manager failed to start because it could not initialize … | Operational | N | N |
| 20029 | Remote Access Connection Manager failed to start because no endpoints were … | Operational | N | N |
| 20030 | Remote Access Connection Manager failed to start because it could not load one … | Operational | N | N |
| 20031 | Remote Access Connection Manager failed to start because it could not locate … | Operational | N | N |
| 20032 | Remote Access Connection Manager failed to start because it could not access … | Operational | N | N |
| 20033 | Remote Access Connection Manager failed to start because it could not register … | Operational | N | N |
| 20034 | Remote Access Connection Manager failed to start because it could not create … | Operational | N | N |
| 20035 | Remote Access Connection Manager failed to start because it could not create … | Operational | N | N |
| 20036 | Remote Access Connection Manager failed to start because it could not access … | Operational | N | N |
| 20037 | Remote Access Connection Manager service failed to start because it could not … | Operational | N | N |
| 20038 | Remote Access Server Configuration Error. | Operational | N | N |
| 20039 | RASSER. | Operational | N | N |
| 20040 | An attempt by RASSER. | Operational | N | N |
| 20041 | RASMXS. | Operational | N | N |
| 20042 | The Remote Access server cannot allocate a route for the user connected on port … | Operational | N | N |
| 20043 | Cannot allocate memory in the admin support thread for the Remote Access … | Operational | N | N |
| 20044 | Cannot create an instance thread in the admin support thread for the Remote … | Operational | N | N |
| 20045 | Cannot create a named pipe instance in the admin support thread for the Remote … | Operational | N | N |
| 20046 | General named pipe failure occurred in the admin support thread for the Remote … | Operational | N | N |
| 20047 | An invalid request was sent to the admin support thread for the Remote Access … | Operational | N | N |
| 20048 | The user {param1} connected on port {param2} on {param3} at {param4} and … | Operational | N | N |
| 20049 | The user connected to port {param1} has been disconnected because the … | Operational | N | N |
| 20050 | The user {param1} connected to port {param2} has been disconnected because no … | Operational | N | N |
| 20051 | The user connected to port param1 has been disconnected because an internal … | Operational | N | N |
| 20052 | The NetBIOS gateway has been configured to access the network but there are no … | Operational | N | N |
| 20053 | The user param1 established a NetBIOS session between the remote workstation … | Operational | N | N |
| 20054 | Remote Access Service failed to start because the Remote Access Connection … | Operational | N | N |
| 20055 | Cannot add the remote computer name param1 on LANA param2 for the client being … | Operational | N | N |
| 20056 | Cannot delete the remote computer name param1 from LANA param2 for the client … | Operational | N | N |
| 20057 | Cannot add the remote computer group name param1 on LANA param2. | Operational | N | N |
| 20058 | Cannot delete the remote computer group name param1 from LANA param2. | Operational | N | N |
| 20059 | The modem on param1 moved to an unsupported BPS rate. | Operational | N | N |
| 20060 | The serial driver could not allocate adequate I/O queues. | Operational | N | N |
| 20061 | Remote Access Connection Manager could not reopen biplex port param1. | Operational | N | N |
| 20062 | Internal Error: Disconnect operation on param2 completed with an error. | Operational | N | N |
| 20063 | Remote Access Connection Manager failed to start because the Protocol engine … | Operational | N | N |
| 20064 | Remote Access service failed to start because the all Protocol engine failed to … | Operational | N | N |
| 20065 | The Remote Access Gateway Proxy could not create a process. | Operational | N | N |
| 20066 | The Remote Access Gateway Proxy could not create a named pipe. | Operational | N | N |
| 20067 | The Remote Access Gateway Proxy could not establish a named pipe connection with … | Operational | N | N |
| 20068 | A general error occurred reading from the named pipe in the Remote Access Proxy. | Operational | N | N |
| 20069 | Cannot open or obtain information about the PPP key or one of its subkeys. | Operational | N | N |
| 20070 | Point to Point Protocol engine was unable to load the param1 module. | Operational | N | N |
| 20071 | The Point to Point Protocol module param1 returned an error while initializing. | Operational | N | N |
| 20072 | The Point to Point Protocol failed to load the required PAP and/or CHAP … | Operational | N | N |
| 20073 | The following error occurred in the Point to Point Protocol module on port: … | Operational | N | N |
| 20076 | The password for user {param1}\{param2} connected on port {param3} has expired. | Operational | N | N |
| 20077 | The account for user {param1}\{param2} connected on port {param3} has expired. | Operational | N | N |
| 20078 | The account for user {param1}\{param2} connected on port {param3} does not have … | Operational | N | N |
| 20079 | The software version of the user param1\param2 connected on port param3 is … | Operational | N | N |
| 20080 | The server machine is configured to require data encryption. | Operational | N | N |
| 20081 | Remote Access Server Security Failure. | Operational | N | N |
| 20082 | The Remote Access Server could not reset lana param1 (the error code is the … | Operational | N | N |
| 20084 | The Remote Access Server will stop using IP Address param1. | Operational | N | N |
| 20085 | The Remote Access Server was unable to renew the lease for IP Address param1 … | Operational | N | N |
| 20086 | The Remote Access Server was unable to acquire an IP Address from the DHCP … | Operational | N | N |
| 20087 | The Remote Access Server was unable to acquire an IP Address from the DHCP … | Operational | N | N |
| 20088 | The Remote Access Server acquired IP Address param1 to be used on the Server … | Operational | N | N |
| 20089 | The Remote Access Server's attempt to callback user {param1} on port {param2} at … | Operational | N | N |
| 20090 | A general error occurred writing to the named pipe in the Remote Access Proxy. | Operational | N | N |
| 20091 | Cannot open the RAS security host Registry key. | Operational | N | N |
| 20092 | Cannot load the Security host module component. | Operational | N | N |
| 20093 | The user param1 has connected and failed to authenticate with a third party … | Operational | N | N |
| 20094 | The user connected to port param1 has been disconnected because the following … | Operational | N | N |
| 20095 | Cannot receive initial data on port {param1} because of the following error: … | Operational | N | N |
| 20096 | The user was authenticated as param1 by the third party security host module but … | Operational | N | N |
| 20097 | A user was unable to connect on port {param1}. | Operational | N | N |
| 20098 | A user was unable to connect on port param1. | Operational | N | N |
| 20099 | Cannot access Registry value for param1. | Operational | N | N |
| 20100 | Cannot access the Registry key param1. | Operational | N | N |
| 20101 | Using the default value for Registry parameter param1 because the value given is … | Operational | N | N |
| 20102 | Cannot enumerate keys of Registry key param1. | Operational | N | N |
| 20103 | Unable to load param1. | Operational | N | N |
| 20104 | Memory allocation failure. | Operational | N | N |
| 20105 | Unable to load the interface param1 from the registry. | Operational | N | N |
| 20106 | RoutingDomainID- param1: Unable to add the interface param2 with the Router … | Operational | N | N |
| 20107 | RoutingDomainID- param1: Unable to remove the interface param2 with the Router … | Operational | N | N |
| 20108 | Unable to open the port param1 for use. | Operational | N | N |
| 20109 | Cannot recognize initial frame received on port {param1}. | Operational | N | N |
| 20110 | An error occurred in the Point to Point Protocol module on port param1 while … | Operational | N | N |
| 20111 | RoutingDomainID- param1: A Demand Dial connection to the remote interface param2 … | Operational | N | N |
| 20112 | Cannot open the RAS third party administration host DLL Registry key. | Operational | N | N |
| 20113 | Cannot load the RAS third party administration DLL component. | Operational | N | N |
| 20114 | The Service will not accept calls. | Operational | N | N |
| 20125 | RoutingDomainID- param1: A Demand Dial persistent connection to the remote … | Operational | N | N |
| 20126 | A packet from param1 destined to param2 over protocol 0xparam3 caused interface … | Operational | N | N |
| 20127 | RoutingDomainID- param1: The Demand Dial interface param2 was not loaded. | Operational | N | N |
| 20128 | Cannot load the Appletalk Remote Access DLL component because of the following … | Operational | N | N |
| 20129 | An error occurred in the Appletalk Remote Access Protocol module on port … | Operational | N | N |
| 20130 | The following error occurred in the Appletalk Remote Access Protocol module on … | Operational | N | N |
| 20131 | A user was unable to connect on port {param1}. | Operational | N | N |
| 20132 | Remote Access Connection Manager failed to start because the RAS RPC module … | Operational | N | N |
| 20138 | RoutingDomainID- param1: A Demand Dial connection to the remote interface param2 … | Operational | N | N |
| 20139 | The port {param1} has been disconnected due to inactivity. | Operational | N | N |
| 20140 | The port {param1} has been disconnected because the user reached the maximum … | Operational | N | N |
| 20141 | The user {param1} has connected and has been successfully authenticated on port … | Operational | N | N |
| 20142 | The user {param1} has connected and has been successfully authenticated on port … | Operational | N | N |
| 20143 | Unable to load the interface param1 from the registry. | Operational | N | N |
| 20144 | The Demand-Dial interface param1 was not registered with the Router. | Operational | N | N |
| 20145 | Cannot initialize the Remote Access and Router service to accept calls using the … | Operational | N | N |
| 20146 | The RADIUS server param1 did not respond to the initial request. | Operational | N | N |
| 20147 | The Remote Access service failed to start because the Point to Point was not … | Operational | N | N |
| 20148 | The RADIUS server name param1 could not be successfully resolved to an IP … | Operational | N | N |
| 20149 | No global configuration was supplied to the IP Router Manager. | Operational | N | N |
| 20150 | Unable to add demand dial filters for interface param1. | Operational | N | N |
| 20151 | The Control Protocol param1 in the Point to Point Protocol module param2 … | Operational | N | N |
| 20152 | The currently configured authentication provider failed to load and initialize … | Operational | N | N |
| 20153 | The currently configured accounting provider failed to load and initialize … | Operational | N | N |
| 20157 | The interface param1 could not be enabled for multicast. | Operational | N | N |
| 20158 | The user {param1} successfully established a connection to {param2} using the … | Operational | N | N |
| 20159 | The connection to {param1} made by user {param2} using device {param3} was … | Operational | N | N |
| 20161 | The user {param1} successfully established a connection to {param2} using the … | Operational | N | N |
| 20162 | The Remote Access Server established a connection to {param1} for the user … | Operational | N | N |
| 20163 | The connection to {param1} made by user {param2} using device {param3} was … | Operational | N | N |
| 20164 | The Remote Access Server wants to disconnect a link in the connection to … | Operational | N | N |
| 20165 | A connection has been established on port param1 using interface param2, but no … | Operational | N | N |
| 20166 | A connection has been established on port param1 using interface param2, but the … | Operational | N | N |
| 20167 | RoutingDomainID- param1: No IP address is available to hand out to the dial-in … | Operational | N | N |
| 20168 | Could not retrieve the Remote Access Server's certificate due to the following … | Operational | N | N |
| 20169 | Unable to contact a DHCP server. | Operational | N | N |
| 20170 | The user param1 has connected and failed to authenticate because of the … | Operational | N | N |
| 20171 | Failed to apply IP Security on port param1 because of error: param2. | Operational | N | N |
| 20172 | Multicast scope mismatch with param1: Locally-configured name "param2", … | Operational | N | N |
| 20173 | Multicast scope address mismatch for scope "param1", Locally-configured range is … | Operational | N | N |
| 20174 | Possible leaky multicast Local Scope detected between this machine and param1, … | Operational | N | N |
| 20175 | Multicast scope 'param1' is non-convex, since border router param2 appears to be … | Operational | N | N |
| 20176 | A leak was detected in multicast scope 'param1'. | Operational | N | N |
| 20177 | Interface param1 is unreachable because of reason param2. | Operational | N | N |
| 20178 | Interface param1 is now reachable. | Operational | N | N |
| 20179 | RoutingDomainID- param1: Interface param2 is unreachable because there are no … | Operational | N | N |
| 20180 | RoutingDomainID- param1: Interface param2 is unreachable because the connection … | Operational | N | N |
| 20181 | RoutingDomainID- param1: Interface param2 is unreachable because it has been … | Operational | N | N |
| 20182 | RoutingDomainID- param1: Interface param2 is unreachable because the Routing and … | Operational | N | N |
| 20183 | RoutingDomainID- param1: Interface param2 is unreachable because it is not … | Operational | N | N |
| 20184 | RoutingDomainID- param1: Interface param2 is unreachable because it is not … | Operational | N | N |
| 20185 | RoutingDomainID- param1: Interface param2 is unreachable because the network … | Operational | N | N |
| 20186 | RoutingDomainID- param1: Interface param2 is now reachable. | Operational | N | N |
| 20187 | The user {param1} failed an authentication attempt due to the following reason: … | Operational | N | N |
| 20188 | The user {param1}; attempting to connect on {param2}; was disconnected because … | Operational | N | N |
| 20189 | The user {param1} connected from {param2} but failed an authentication attempt … | Operational | N | N |
| 20190 | Because no certificate has been configured for clients dialing in with EAP-TLS, … | Operational | N | N |
| 20191 | Because the certificate that was configured for clients dialing in with EAP-TLS … | Operational | N | N |
| 20192 | A certificate could not be found. | Operational | N | N |
| 20193 | CoID=param1: An error occurred while configuring IP packet filters for user … | Operational | N | N |
| 20194 | The user {param1} connected on port {param2} on {param3} at {param4} and … | Operational | N | N |
| 20195 | The user {param1} has been disconnected on port {param2}. | Operational | N | N |
| 20196 | An invalid response was received from the RADIUS server param1. | Operational | N | N |
| 20197 | Ras Audio Acceleration failed to param1. | Operational | N | N |
| 20198 | Choosing radius server param1 for authentication. | Operational | N | N |
| 20199 | IPinIP tunnel interfaces are no longer supported | Operational | N | N |
| 20200 | The user {param1} connected on port {param2} has been assigned address {param3}. | Operational | N | N |
| 20201 | The user with ip address {param1} has disconnected. | Operational | N | N |
| 20202 | An error occurred while trying to revert impersonation. | Operational | N | N |
| 20203 | Cannot load the Security host module component. | Operational | N | N |
| 20204 | Cannot load the RAS third party administration DLL component. | Operational | N | N |
| 20205 | IPX routing is no longer supported. | Operational | N | N |
| 20206 | Disk full. | Operational | N | N |
| 20207 | Disk full. | Operational | N | N |
| 20208 | Disk full. | Operational | N | N |
| 20209 | A connection between the VPN server and the VPN client param1 has been … | Operational | N | N |
| 20210 | The Network Access Protection (NAP) enforcement client failed to register with … | Operational | N | N |
| 20211 | The Network Access Protection (NAP) enforcement client could not start PPP … | Operational | N | N |
| 20212 | The request sent to the Network Access Protection Agent (NAPAgent) failed. | Operational | N | N |
| 20213 | The Network Access Protection (NAP) enforcement client received an invalid … | Operational | N | N |
| 20214 | The Network Access Protection (NAP) enforcement client received an invalid … | Operational | N | N |
| 20215 | The IAS/RADIUS server has passed an invalid value to the server running Routing … | Operational | N | N |
| 20216 | The Routing and Remote Access service could not start. | Operational | N | N |
| 20217 | An error occurred while trying to disable param1 packet filtering for Routing … | Operational | N | N |
| 20218 | An error occurred while trying to enable param1 packet filtering for Routing and … | Operational | N | N |
| 20219 | param1 packet filtering has been disabled. | Operational | N | N |
| 20220 | The connection to param1 made using device param2 was terminated. | Operational | N | N |
| 20221 | CoId=. | Operational | N | N |
| 20222 | CoId=. | Operational | N | N |
| 20223 | CoId=. | Operational | N | N |
| 20224 | CoId=param1: The link to the Remote Access Server has been established by user … | Operational | N | N |
| 20225 | CoId=. | Operational | N | N |
| 20226 | CoId=param1: The user param2 dialed a connection named param3 which has … | Operational | N | N |
| 20227 | CoId=param1: The user param2 dialed a connection named param3 which has failed. | Operational | N | N |
| 20228 | The remote access connection with the correlation ID param1 has Network Access … | Operational | N | N |
| 20229 | The remote access connection with the correlation ID param1 received an … | Operational | N | N |
| 20230 | The connection from user param1 on port param2 has been disconnected because the … | Operational | N | N |
| 20247 | CoId=param1: Cannot receive initial frame on port param2 because of the … | Operational | N | N |
| 20248 | CoId=param1: The user connected to port param2 has been disconnected due to … | Operational | N | N |
| 20249 | CoId=param1: The user param2 has connected and failed to authenticate on port … | Operational | N | N |
| 20250 | RoutingDomainID- param1: CoID=param2: The user param3 has connected and has been … | Operational | N | N |
| 20251 | RoutingDomainID- param1: CoId=param2: The user param3 connected on port param4 … | Operational | N | N |
| 20252 | CoId=param1: The user connected to port param2 has been disconnected because the … | Operational | N | N |
| 20253 | RoutingDomainID- param1: CoId=param2: The user param3 connected to port param4 … | Operational | N | N |
| 20254 | CoId=param1: The user param2 on port param3 was called back at the number … | Operational | N | N |
| 20255 | CoId=param1: The following error occurred in the Point to Point Protocol module … | Operational | N | N |
| 20256 | CoId=param1: The password for user param2\param3 connected on port param4 has … | Operational | N | N |
| 20257 | CoId=param1: The account for user param2\param3 connected on port param4 has … | Operational | N | N |
| 20258 | CoId=param1: The account for user param2\param3 connected on port param4 does … | Operational | N | N |
| 20259 | CoId=param1: The Remote Access Server's attempt to callback user param2 on port … | Operational | N | N |
| 20260 | CoId=param1: Cannot receive initial data on port param2 because of the following … | Operational | N | N |
| 20261 | CoId=param1: A user was unable to connect on port param2. | Operational | N | N |
| 20262 | CoId=param1: Cannot recognize initial frame received on port param2. | Operational | N | N |
| 20263 | CoID=param1: The port param2 has been disconnected due to inactivity. | Operational | N | N |
| 20264 | CoID=param1: The port param2 has been disconnected because the user reached the … | Operational | N | N |
| 20265 | RoutingDomainID- param1: CoID=param2: The user param3 has connected and has been … | Operational | N | N |
| 20266 | RoutingDomainID- param1: CoID=param2: The user param3 has connected and has been … | Operational | N | N |
| 20267 | CoID=param1: The user param2 successfully established a connection to param3 … | Operational | N | N |
| 20268 | CoID=param1: The connection to param2 made by user param3 using device param4 … | Operational | N | N |
| 20269 | CoId=param1: The user param2 failed an authentication attempt due to the … | Operational | N | N |
| 20270 | CoID=param1: The user param2, attempting to connect on param3, was disconnected … | Operational | N | N |
| 20271 | CoId=param1: The user param2 connected from param3 but failed an authentication … | Operational | N | N |
| 20272 | RoutingDomainID- param1: CoID=param2: The user param3 connected on port param4 … | Operational | N | N |
| 20273 | CoId=. | Operational | N | N |
| 20274 | RoutingDomainID- param1: CoID=param2: The user param3 connected on port param4 … | Operational | N | N |
| 20275 | RoutingDomainID- param1: CoID=param2: The user with ip address param3 has … | Operational | N | N |
| 20276 | CoId=. | Operational | N | N |
| 20277 | CoId=param1: Successfully processed MOBIKE update for connection named 'param2'. | Operational | N | N |
| 20278 | CoId=param1: Unable to process MOBIKE update for connection named 'param2'. | Operational | N | N |
| 20279 | CoId=param1: Disabling PPP AUTH for param2\\param3 on port param4. | Operational | N | N |
| 20280 | RoutingDomainID- param1: CoID=param2: The correlation ID on the server is … | Operational | N | N |
| 20281 | CoID=param1: Connection supports MOBIKE. | Operational | N | N |
| 20282 | RoutingDomainID- param1: Failed to enable IPv4 forwarding on interface param2 … | Operational | N | N |
| 20283 | RoutingDomainID- param1: Failed to disable IPv4 forwarding on interface param2 … | Operational | N | N |
| 20284 | RoutingDomainID- param1: Failed to plumb IKEv2 policies for one or more demand … | Operational | N | N |
| 20285 | Did not find the certificate configured to be used for IKEv2 local … | Operational | N | N |
| 20286 | Failed to plumb the custom IKEv2 policy. | Operational | N | N |
| 20287 | RoutingDomainID- param1: Did not find the PreSharedKey configured to be used for … | Operational | N | N |
| 20288 | RoutingDomainID- param1: IPv4 routes are not added for the demand dial … | Operational | N | N |
| 20289 | RoutingDomainID- param1: IPv6 routes are not added for the demand dial … | Operational | N | N |
| 20290 | Disabling S2S interface param1 (RoutingDomain: param2) because either there is … | Operational | N | N |
| 20291 | param1 requires attention. | Operational | N | N |
| 20292 | Retrieving Max connections failed. | Operational | N | N |