Error message when you establish an outgoing remote access connection in Windows Server 2003: "Error 734 - The PPP link control protocol terminated" or "TCP/IP CP reported error 31: A device attached to the system is not functioning"

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

SYMPTOMS

In Windows Server 2003, you cannot establish an outgoing remote access connection by using one of the following methods:
  • Dial-up
  • Point-to-Point Tunneling Protocol (PPTP)
  • Layer 2 Tunneling Protocol (L2TP)
Additionally, you receive one of the following error messages:
Error 734 - The PPP link control protocol terminated.
TCP/IP CP reported error 31: A device attached to the system is not functioning.
This problem may occur for the following outgoing connections:
  • Virtual private network (VPN) client connections
  • Dial-up client connections
  • Dial-On-Demand connections

CAUSE

This problem occurs because the Remote Access Connection Manager times out while it tries to plumb the route of the newly established connection to the routing table.

RESOLUTION

To resolve this problem, follow these steps:
  1. Install one of the following updates:
    • The hotfix that is mentioned in the following Microsoft Knowledge Base article:
      888090 Routing and Remote Access stops responding in Windows Server 2003
    • Windows Server 2003 Service Pack 1 or later service packs.
  2. Click Start, click Run, type regedit, and then click OK.
  3. Locate and then click the following registry subkey:
    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan\Parameters
  4. Right-click the IpOutLowWatermark registry entry, and then click Modify.
  5. Increase the value in the Value data box, and then click OK.

    Note We recommend that you set the value of IpOutLowWatermark to the number of Demand Dial interfaces plus 5 or to the number of client connections plus 5. For example, assume that you have 5 Demand Dial interfaces or 5 client connections. In this case, set the value of IpOutLowWatermark to 10.
  6. Right-click the IpOutHighWatermark registry entry, and then click Modify.
  7. Increase the value in the Value data box, and then click OK.

    Note We recommend that you set the value of IpOutHighWatermark to the value of IpOutLowWatermark plus 5. For example, if the value of IpOutLowWatermark is 10, set the value of IpOutHighWatermark to 15.
  8. On the File menu, click Exit.
Note Do not set the values of these two entries to a very large number. This can cause the resources to be wasted because the system is maintaining excess adapters.

MORE INFORMATION

For more information about the IpOutLowWatermark registry entry and about the IpOutHighWatermark registry entry, visit the following Microsoft Web sites:
http://technet2.microsoft.com/windowsserver/en/library/dca16e97-833f-4465-99d1-063289f819de1033.mspx
http://technet2.microsoft.com/windowsserver/en/library/ff35a293-c2fc-4ac3-a72f-5c2a42a43e421033.mspx
If you start remote access tracing by running the NETSH RAS SET TRACING * ENABLED command, the following information will be logged:

The PPP.log file
[3228] 08-23 13:09:23:215: RasIPCPProjectionNotification returned 31
The RASMAN.log file
[3228] 08-23 13:09:23:215: d:\nt\net\rras\ras\rasman\rasman\request.c, 7070: Activate Route failed for VPN3-4. dwErr = 31
The RASIPCP.Log file
[3228] 08-23 13:09:23:215: IPCP: RasActivateRoute done(31)

Properties

Article ID: 951013 - Last Review: April 11, 2008 - Revision: 1.0
APPLIES TO
  • Microsoft Windows Server 2003 Service Pack 1
  • Microsoft Windows Server 2003 Service Pack 2
  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
  • Microsoft Windows Server 2003, Datacenter x64 Edition
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
Keywords: 
kbexpertiseinter kbtshoot kbprb KB951013

Give Feedback

 

Contact us for more help

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