Routing and Remote Access stops responding in Windows Server 2003

Article translations Article translations
Article ID: 888090 - View products that this article applies to.
Expand all | Collapse all

On This Page


Assume the following scenario: You try to establish a virtual private network (VPN) connection with a remote site on a Microsoft Windows Server 2003-based computer that is running Routing and Remote Access. In this scenario, Routing and Remote Access becomes unresponsive, and you cannot quit the service. You must restart your computer to restart Routing and Remote Access. Additionally, you may experience either of the following symptoms:
  • If you try to reconnect the VPN connection, the VPN connection remains in the connecting state.
  • If you try to restart the Routing and Remote Access service, you may receive the following error message:
    Error 1053: The service did not respond to the start or control request in a timely fashion.


Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.


No prerequisites are required.

Restart requirement

You must restart your computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in coordinated universal time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.
Windows Server 2003, 32-Bit Editions
   Date         Time   Version            Size    File name
   18-Oct-2004  07:21  5.2.3790.223      335,360  Tcpip.sys
Windows Server 2003, 64-Bit Editions
   Date         Time   Version            Size    File name
   17-Oct-2004  23:21  5.2.3790.223      973,824  Tcpip.sys


Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.


For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates


Article ID: 888090 - Last Review: July 24, 2007 - Revision: 2.9
  • Microsoft Internet Security and Acceleration Server 2004 Standard Edition
  • Microsoft Windows Server 2003, Web Edition
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise x64 Edition
kbautohotfix kbqfe kbhotfixserver kbbug kbfix kbwinserv2003presp1fix KB888090

Give Feedback


Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from