Knowledge Base

XCLN: Shiva Error: Unable to Negotiate LCP Connection

Article ID: 175099

Article Last Modified on 10/28/2006

APPLIES TO

This article was previously published under Q175099

SYMPTOMS

When using the ShivaRemote client software to establish a connection through a Remote Access Service (RAS) server to an Exchange Server computer, you may receive the following error message:

Unable to negotiate LCP connection. Please check that
remote device is installed and configured and that
dial-in is enabled

CAUSE

The RAS server is a computer running Windows NT 4.0. If your RAS server is configured to "Allow any authentication including clear text," a RAS client is able to connect with Password Authentication Protocol (PAP), Shiva Password Authentication Protocol (SPAP), Challenge Handshake Authentication Protocol (CHAP), or Microsoft CHAP (MS- CHAP) depending on what the client supports. Normally, a client will attempt to connect with CHAP or MS-CHAP, if that is valid for the RAS server to which it is connecting. In the case of Shiva remote client connections, Shiva does not support MS-CHAP. Encountering this protocol causes the Shiva client to fail.

For additional information about Windows NT 4.0 RAS server authentication configuration, please see the following article in the Microsoft Knowledge Base:

172216 How to Force Routing and Remote Access to Use PAP

WORKAROUND

To work around the problem:

Keywords: kbbug kbpending KB175099


Send feedback to Microsoft

© Microsoft Corporation. All rights reserved.