Windows 2000 stops at event ID 20193.
Windows XP stops at event ID 20202.
Windows Server 2003 can record all of the listed event IDs.
The RRAS event IDs are:
20001 - Cannot load the NetBIOS gateway DLL component because of the following error: %1
20002 - Cannot access registry key values.
20003 - Cannot enumerate Registry key values. %1
20004 - Parameter %1 has an invalid type.
20005 - Cannot enumerate the Remote Access Connection Manager ports. %1
20006 - The Remote Access Service is not configured to receive calls or all ports configured for receiving calls are in use by other applications.
20007 - Cannot receive initial frame on port %1 because of the following error: %2 The user has been disconnected.
20008 - The user connected to port %1 has been disconnected because of inactivity.
20009 - The user connected to port %1 has been disconnected because there is not sufficient memory available in the system.
20010 - The user connected to port %1 has been disconnected because of a system error.
20011 - The user connected to port %1 has been disconnected because of a critical network error on the local network.
20012 - The user connected to port %1 has been disconnected because of a critical network error on the async network.
20013 - The communication device attached to port %1 is not functioning.
20014 - The user %1 has connected and did not authenticate on port %2. 2. The line has been disconnected.
20015 - The user %1 has connected and has been successfully authenticated on port %2.
20016 - The user connected to port %1 has been disconnected because there was a transport-level error during the authentication conversation.
20018 - Cannot reset the network adapter for LANA %1. The error code is the data.
20019 - Remote Access Server Security Failure. Cannot locate the computer name. GetComputerName call has failed.
20020 - Remote Access Server Security Failure. Cannot add the name for communication with the security agent on LANA %1.
20021 - Remote Access Server Security Failure. Cannot access the network adapter address on LANA %1.
20022 - Remote Access Server Security Failure. The security agent has rejected the Remote Access server's call to establish a session on LANA %1.
20023 - 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.
20024 - Remote 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.
20025 - The user connected to port %1 has been disconnected because there are no operating system resources available.
20026 - The user connected to port %1 has been disconnected because of a failure to lock user memory.
20027 - Remote Access Connection Manager could not start because NDISWAN could not be opened.
20028 - Remote Access Connection Manager could not start because it could not initialize the security attributes. Restart the computer. %1
20029 - Remote Access Connection Manager could not start because no endpoints were available. Restart the computer.
20030 - Remote Access Connection Manager could not start because it could not load one or more communication DLLs. Make sure that your communication hardware is installed and then restart the computer. %1
20031 - Remote Access Connection Manager could not start because it could not locate port information from media DLLs. %1
20032 - Remote Access Connection Manager could not start because it could not access protocol information from the Registry. %1
20033 - Remote Access Connection Manager could not start because it could not register with the local security authority. Restart the computer. %1
20034 - Remote Access Connection Manager could not start because it could not create shared file mapping. Restart the computer. %1
20035 - Remote Access Connection Manager could not start because it could not create buffers. Restart the computer. %1
20036 - Remote Access Connection Manager could not start because it could not access resources. Restart the computer. %1
20037 - Remote Access Connection Manager service could not start because it could not start worker threads. Restart the computer.
20038 - 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 computer.
20039 - RASSER.DLL cannot open the SERIAL.INI file.
20040 - An attempt by RASSER.DLL to obtain an async media access control handle failed.
20041 - RASMXS.DLL cannot load RASSER.DLL.
20042 - 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.
20043 - Cannot allocate memory in the admin support thread for the Remote Access Service.
20044 - Cannot create an instance thread in the admin support thread for the Remote Access Service.
20045 - Cannot create a named pipe instance in the admin support thread for the Remote Access Service.
20046 - General named pipe failure occurred in the admin support thread for the Remote Access Service.
20047 - An 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.
20048 - The user %1 connected on port %2 on %3 at %4 and disconnected on %5 at %6. The user was active for %7 minutes %8 seconds. %9 bytes were sent and %10 bytes were received. The port speed was %11. The reason for disconnecting was %12.
20049 - The user connected to port %1 has been disconnected because the authentication process did not complete within the required time.
20050 - The user %1 connected to port %2 has been disconnected because no network protocols were successfully negotiated.
20051 - The user connected to port %1 has been disconnected because an internal authentication error occurred.
20052 - 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 computer.
20053 - The user %1 established a NetBIOS session between the remote workstation %2 and the network server %3.
20054 - Remote Access Service could not start because the Remote Access Connection Manager could not initialize because of the following error: %1
20055 - Cannot add the remote computer name %1 on LANA %2 for the client being connected on port %3. The error code is the data.
20056 - Cannot delete the remote computer name %1 from LANA %2 for the client being disconnected on port %3. The error code is the data.
20057 - Cannot add the remote computer group name %1 on LANA %2. The error code is the data.
20058 - Cannot delete the remote computer group name %1 from LANA %2. The error code is the data.
20059 - The modem on %1 moved to an unsupported BPS rate.
20060 - The serial driver could not allocate sufficient I/O queues. This may result in an unreliable connection.
20061 - Remote 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.
20062 - Internal Error: Disconnect operation on %1 completed with an error. %1
20063 - Remote Access Connection Manager could not start because the Point-to-Point Protocol could not initialize. %1
20064 - The user %1 on port %2 was called back at the number %3.
20065 - The Remote Access Gateway Proxy could not create a process.
20066 - The Remote Access Gateway Proxy could not create a named pipe.
20067 - The Remote Access Gateway Proxy could not establish a named pipe connection with the Remote Access Supervisor Proxy.
20068 - A general error occurred reading from the named pipe in the Remote Access Proxy.
20069 - Cannot open or obtain information about the PPP key or one of its subkeys. %1
20070 - Point-to-Point Protocol engine was not able to load the %1 module. %2
20071 - The Point-to-Point Protocol module %1 returned an error while initializing. %2
20072 - The Point-to-Point Protocol could not load the required PAP or CHAP authentication modules.
20073 - The following error occurred in the Point-to-Point Protocol module on port: %1, User Name: %2. %3
20074 - The IPX network number %1 requested by the remote side for the WAN interface is already in use on the local LAN. Possible solution: Disconnect this computer from the LAN and wait 3 minutes before dialing again.
20075 - The IPX network number %1 requested by the remote workstation for the WAN interface cannot be used on the local IPX router because the router is configured to give the same network number to all the remote workstations. If you want to connect a remote workstation with a different network number, you must reconfigure the router to disable the common network number option.
20076 - The password for user %1\%2 connected on port %3 has expired. The line has been disconnected.
20077 - The account for user %1\%2 connected on port %3 has expired. The line has been disconnected.
20078 - The account for user %1\%2 connected on port %3 does not have Remote Access privilege. The line has been disconnected.
20079 - The software version of the user %1\%2 connected on port %3 is unsupported. The line has been disconnected.
20080 - The server computer is configured to require data encryption. The computer for user %1\%2 connected on port %3 does not support encryption. The line has been disconnected.
20081 - Remote Access Server Security Failure. Could not reset LANA %1 (the error code is the data. Security check not performed.
20082 - The Remote Access Server could not reset LANA %1 (the error code is the data and will not be active on it.
20083 - The IPX network number %1 configured for the pool of WAN network numbers cannot be used because it conflicts with another network number on the net. You must re-configure the pool to have unique network numbers.
20084 - The Remote Access Server will stop using IP Address %1 (either because it was not able 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 not able to access network resources. Users can re-connect to the server to restore IP connectivity.
20085 - The Remote Access Server was not able to renew the lease for IP Address %1 from the DHCP Server. The user assigned with this IP address will be not able to access network resources using IP. Re-connecting to the server will restore IP connectivity.
20086 - The Remote Access Server was not able to acquire an IP Address from the DHCP Server to assign to the incoming user.
20087 - The Remote Access Server was not able to acquire an IP Address from the DHCP Server to be used on the Server Adapter. Incoming user will be not able to connect using IP.
20088 - The Remote Access Server acquired IP Address %1 to be used on the Server Adapter.
20089 - The Remote Access Server's attempt to callback user %1 on port %2 at %3 failed because of the following error: %4
20090 - A general error occurred writing to the named pipe in the Remote Access Proxy.
20091 - Cannot open the RAS security host Registry key. The following error occurred: %1
20092 - Cannot load the Security host module component. The following error occurred: %1
20093 - The user %1 has connected and did not authenticate with a third party security on port %2. The line has been disconnected.
20094 - The user connected to port %1 has been disconnected because the following internal authentication error occurred in the third party security module: %2
20095 - Cannot receive initial data on port %1 because of the following error: %2 The user has been disconnected.
20096 - 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.
20097 - A user was not able to connect on port %1. No more connections can be made to this remote computer because the computer has exceeded its client license limit.
20098 - A user was not able to connect on port %1. The NetBIOS protocol has been disabled for the Remote Access Server.
20099 - Cannot access Registry value for %1.
20100 - Cannot access the Registry key %1.
20101 - Using the default value for Registry parameter %1 because the value given is not in the valid range for the parameter.
20102 - Cannot enumerate keys of Registry key %1.
20103 - Not able to load %1.
20104 - Memory allocation failure.
20105 - Unable to load the interface %1 from the registry. The following error occurred: %2
20106 - Unable to add the interface %1 with the Router Manager for the %2 protocol. The following error occurred: %3
20107 - Unable to remove the interface %1 with the Router Manager for the %2 protocol. The following error occurred: %3
20108 - Unable to open the port %1 for use. %2
20109 - Cannot recognize initial frame received on port %1. The line has been disconnected.
20110 - An error occurred in the Point-to-Point Protocol module on port %1 while trying to initiate a connection. %2
20111 - A Demand Dial connection to the remote interface %1 on port %2 was successfully initiated but could not complete successfully because of the following error: %3
20112 - Cannot open the RAS third party administration host DLL Registry key. The following error occurred: %1
20113 - Cannot load the RAS third party administration DLL component. The following error occurred: %1
20114 - The Service will not accept calls. No protocols were configured for use.
20115 - IPX Routing requires an internal network number for correct operation.
20116 - Cannot load routing protocol DLL %1. The error code is in data.
20117 - Cannot register routing protocol 0x %1. The error code is in data.
20118 - Cannot start routing protocol 0x %1. The error code is in data.
20119 - Cannot load IPX CP protocol DLL. The error code is in data.
20120 - Could not open IPX SAP socket for exclusive access. The error code is in data.
20121 - Server %1 has changed its IPX address. Old and new addresses are in data.
20122 - Server %1 is advertised with different IPX address. Old and new addresses are in data.
20123 - Could not open IPX RIP socket for exclusive access. The error code is in data.
20124 - Another IPX router claims different network number for interface %1. Offending router IPX address is in data.
20125 - A Demand Dial persistent connection to the remote interface %1 could not be initiated successfully. The following error occurred: %2
20126 - 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.
20127 - The Demand Dial interface %1 was not loaded. The router was not started in Demand Dial mode.
20128 - Cannot load the AppleTalk Remote Access DLL component because of the following error: %1
20129 - An error occurred in the AppleTalk Remote Access Protocol module on port %1 while trying to initiate a connection. %2
20130 - The following error occurred in the AppleTalk Remote Access Protocol module on port %1. %2
20131 - A user was not able to connect on port %1. The AppleTalk Remote Access protocol has been disabled for the Remote Access Server.
20132 - Remote Access Connection Manager could not start because the RAS RPC module failed to initialize. %1
20133 - IPX Routing could not start because IPX forwarder driver could not be loaded.
20134 - IPX global configuration information is corrupted.
20135 - IPX dial-in client configuration information is corrupted.
20136 - IPX configuration information for interface %1 is corrupted.
20137 - An IPX packet caused interface %1 to be brought up. The first %2 bytes of the packet are in data.
20138 - A Demand Dial connection to the remote interface%1 could not be initiated successfully. The following error occurred: %2
20139 - The port %1 has been disconnected because of inactivity.
20140 - The port %1 has been disconnected because the user reached the maximum connect time permitted by the administrator.
20141 - The user %1 has connected and has been successfully authenticated on port %2. Data sent and received over this link is encrypted.
20142 - The user %1 has connected and has been successfully authenticated on port %2. Data sent and received over this link is strongly encrypted.
20143 - Not able 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 Remote Access 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.
20144 - The Demand-Dial interface %1 was not registered with the Router. Demand-Dial interfaces are not supported on a Windows NT Workstation.
20145 - Cannot initialize the Remote Access and Router service to accept calls using the TCP IP transport protocol. The following error occurred: %1
20146 - The RADIUS server %1 did not respond to the initial request. Make sure that the server name or IP address and secret are correct.
20147 - The Remote Access service could not start because the Point-to-Point was not initialized successfully. %1
20148 - The RADIUS server name %1 could not be successfully resolved to an IP address. Make sure that the name is spelled correctly and that the RADIUS server is running correctly.
20149 - No global configuration was supplied to the IP Router Manager. - Rerun setup.
20150 - Not able to add demand dial filters for interface %1
20151 - The Control Protocol %1 in the Point-to-Point Protocol module %2 returned an error while initializing. %3
20152 - The currently configured authentication provider could not load and initialize successfully. %1
20153 - The currently configured accounting provider could not load and initialize successfully. %1
20154 - The IPX Internal Network Number is not valid and the IPX Router Manager was unsuccessful in its attempt to automatically assign a valid one. Reconfigure the IPX Internal Network Number through the connections folder and restart the Routing and Remote Access service.
20155 - In order for the IPX Router Manager (that runs as part of the Routing and Remote Access Service) to run, it had to start the IPX Protocol Stack Driver. This driver was either manually stopped or marked as demand start. The Routing and Remote Access Service was probably started by the creation of Incoming Connections or through the Routing and Remote Access snap in.
20156 - The IPX Router Manager was not able to start because the IPX Protocol Stack Driver could not be started.
20157 - The interface %1 could not be enabled for multicast. %2 will not be activated over this interface.
20158 - The user %1 successfully established a connection to %2 using the device %3.
20159 - The connection to %1 made by user %2 using device %3 was disconnected.
20161 - The user %1 successfully established a connection to %2 using the device %3. This connection occurred automatically because the bandwidth use was high.
20162 - The Remote Access Server established a connection to %1 for the user %2 using the device %3. This connection occurred automatically because the bandwidth use was high.
20163 - The connection to %1 made by user %2 using device %3 was disconnected. This disconnection occurred automatically because the bandwidth use was low.
20164 - The Remote Access Server wants to disconnect a link in the connection to %1 made by user %2 because the bandwidth use is too low.
20165 - A connection has been established on port %1 using interface %2, but no IP address was obtained.
20166 - A connection has been established on port %1 using interface %2, but the remote side got no IP address.
20167 - No IP address is available to hand out to the dial-in client.
20168 - Could not retrieve the Remote Access Server's certificate because of the following error: %1
20169 - Not able to contact a DHCP server. The Automatic Private IP Address %1 will be assigned to dial-in clients. Clients may not be able to access resources on the network.
20170 - The user %1 has connected and could not authenticate because of the following error: %2
20171 - Could not, apply IP Security on port %1 because of error: %2. No calls will be accepted to this port.
20172 - Multicast scope mismatch with %1: Locally-configured name "%2", Remotely-configured name "%3".
20173 - Multicast scope address mismatch for scope "%1", Locally-configured range is %4 - %5; Remotely-configured range is %2-%3
20174 - Possible leaky multicast Local Scope detected between this computer and %1, because a boundary appears to exist for %2, but not for the local scope. If this warning continues to occur, a problem likely exists.
20175 - Multicast scope '%1' is non-convex, because border router %2 appears to be outside.
20176 - A leak was detected in multicast scope '%1'. One of the following routers is misconfigured: %2
20177 - Interface %1 is unreachable because of reason %2.
20178 - Interface %1 is now reachable.
20179 - Interface %1 is unreachable because there are no modems (or other connecting devices available for use by this interface.
20180 - Interface %1 is unreachable because the connection attempt failed.
20181 - Interface %1 is unreachable because it has been administratively disabled.
20182 - Interface %1 is unreachable because the Routing and Remote Access service is in a paused state.
20183 - Interface %1 is unreachable because it is not permitted to connect at this time. Check the dial-out hours configured on this interface.
20184 - Interface %1 is unreachable because it is not currently connected to the network.
20185 - Interface %1 is unreachable because the network card for this interface has been removed.
20186 - Interface %1 is now reachable.
20187 - The user %1 failed an authentication attempt because of the following reason: %2
20188 - The user %1, trying to connect on %2, was disconnected because of the following reason: %3
20189 - The user %1 connected from %2 but failed an authentication attempt because of the following reason: %3
20190 - Because no certificate has been configured for clients dialing in with EAP-TLS, a default certificate is being sent to user %1. Go to the user's Remote Access Policy and configure the Extensible Authentication Protocol (EAP).
20191 - 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. Go to the user's Remote Access Policy and configure the Extensible Authentication Protocol (EAP).
20192 - 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.
20193 - An error occurred while configuring IP packet filters over %1. This is frequently the result of another service, for example Microsoft Proxy Server, also using the Windows 2000 filtering services.
20194 - The user %1 connected on port %2 on %3 at %4 and disconnected on %5 at %6. The user was active for %7 minutes %8 seconds. %9 bytes were sent and %10 bytes were received. The reason for disconnecting was %11.
20195 - The user %1 has been disconnected on port %2. %3
20196 - An invalid response was received from the RADIUS server %1. %2
20197 - Ras Audio Acceleration failed to %1. %2
20198 - Choosing radius server %1 for authentication.
20199 - IP in IP tunnel interfaces are no longer supported
20200 - The user %1 connected on port %2 has been assigned address %3
20201 - The user with ip address %1 has disconnected
20202 - An error occurred while trying to revert impersonation.
20203 - Cannot load the Security host module component. The following error occurred: %1 is not a valid win32 application.
20204 - Cannot load the RAS third party administration DLL component. The following error occurred: %1 is not a valid win32 application.
20205 - IPX routing is no longer supported.
20206 - Disk full. Deleted older log file %1 to create free space.
20207 - Disk full. Could not delete older log file %1 to create free space.
20208 - Disk full. Could not find older log file to delete and create free space.
