A program that uses a remote access PPP connection to a Windows Server 2003-based computer is disconnected when the user logs off

A program that uses a remote access Point-to-Point Protocol (PPP) connection to a Windows Server 2003-based computer is disconnected when the user logs off. After the user logs off, the user cannot log back on.

This problem may occur when software that uses a Remote Access Service PPP connection runs a service in the context of the Local System account. The problem occurs because remote access connections automatically disconnect when a user logs off from a remote access client. The default behavior is to disconnect remote access sessions that are associated with the logged on user and with the Local System account.

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.

To work around this problem, follow these steps:

1. Run the service as a different account that has local Administrator rights instead of as the Local System account.
2. Enable the KeepRasConnections key in the registry. To enable the KeepRasConnections key, follow these steps:
   1. Start Registry Editor.
   2. Locate and then click the following key in the registry:
      HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Winlogon
   3. On the Edit menu, click Add Value, and then add the following registry value:
      Value Name: KeepRasConnections
      Data Type: REG_SZ
      Value: 1
      Default Value: 0 (disabled)
   4. Quit Registry Editor.

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

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.

Prerequisites

To apply this hotfix, you must have Microsoft Windows Server 2003 Service Pack 1 (SP1) installed.

Note Service Pack 1 is included in the x64-based and Itanium-based versions of Windows Server 2003.

Restart requirement

You must restart the 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, x86-based versions

Windows Server 2003, Itanium-based versions

Windows Server 2003, x64-based versions

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.