Conflicts Between Services Requesting Use of Network Address Translation Modules (254322)


The information in this article applies to:

  • Microsoft Windows 2000 Server
This article was previously published under Q254322

SUMMARY

This article describes errors that occur when components or services request use of the Network Address Translation (NAT) modules in Microsoft Windows 2000.

MORE INFORMATION

Several Microsoft services, as well as some third-party components, can request use of the Network Address Translation (NAT) modules in Windows 2000. These modules can only be used exclusively by one service or component at a time.

Examples of Microsoft services and components that can use these modules are Internet Connection Sharing (ICS), and the Routing and Remote Access Service connection sharing component itself (RRAS NAT).

A component or service that does not acquire access to the NAT modules must log a descriptive error indicating the reason, so that the user or administrator can resolve the conflict. If either RRAS NAT or ICS does not succeed in getting access to the NAT modules because another component or service currently has acquired them, it will record one of these error messages in the event log:
The ICS service could not start because another process has taken control of the kernel-mode translation module. This may occur when the Connection Sharing component has been installed in the Routing and Remote Access Manager. If this is the case, please remove the Connection Sharing component and restart the Internet Connection Sharing service.

The Connection Sharing component could not start because another process has taken control of the kernel-mode translation module. This may occur when Internet Connection Sharing has been enabled for a connection. If this is the case, please disable Internet Connection Sharing for the connection in the Network Connections folder and then restart Routing and Remote Access.
While these errors indicate a component that could be causing the conflict, other components or services could be the cause and should also be investigated. You need to determine which service is appropriate for the functionality you need. Removing the NAT protocol from the IP routing section of the RRAS administrative menu can disable the NAT capability of the RRAS service.
Modification Type:MajorLast Reviewed:10/11/2002
Keywords:kbinfo KB254322
©2002 Microsoft Corporation. All rights reserved.