Article ID: 306193 - View products that this article applies to.
This article was previously published under Q306193
On a Windows 2000-based server that is running the remote access service and that you have configured for L2TP connections, the following event may be recorded in Event Viewer:
In addition, the L2TP clients cannot connect to the remote access server when this event is logged.
Event Type: Warning
Event Source: RemoteAccess
Event Category: None
Event ID: 20171
Description: Failed to apply IP Security on port Server name and L2tp Port number because of error: The RPC server is unavailable. No calls will be accepted to this port.
This event is typically logged on Windows 2000 servers that are running the remote access service and Internet Security and Acceleration (ISA) Server on the same server, which is due to a race condition between these two services.
To work around this problem, configure the remote access service to start manually instead of automatically, and then after you start the computer, you can manually start the remote access service.
To configure the remote access service to start manually, use the Services tool in the Administrative Tools folder (Click Start, point to Programs, and then click Administrative Tools), or change the configuration in the properties of the remote access service.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
Simply setting dependencies for the remote access service may not resolve this race condition, which is why the workaround that is provided in this article is suggested.