Remote Access Service Callback Authentication Does Not Work

 Last reviewed: March 10, 1998
Article ID: Q182281
The information in this article applies to:
  • Microsoft Windows NT Workstation versions 3.5, 3.51, 4.0
  • Microsoft Windows NT Server versions 3.5, 3.51, 4.0
  • Microsoft Windows NT Server Enterprise Edition version 4.0

SYMPTOMS

Callback authentication may not work with Windows NT-based Remote Access Service (RAS) servers when you attempt to connect to a Shiva LanRover Access Switch version 4.5 or an IBM 8235 Remote Access Server.

CAUSE

This behavior can occur with remote access devices that do not support the Microsoft Call Back Challenge Protocol (CBCP) for callback authentication.

MORE INFORMATION

The Shiva LanRover Access Switch version 4.5 and the IBM 8235 Remote Access Server use Shiva's proprietary Shiva Password Authentication Protocol (SPAP) for callback authentication and do not support CBCP. Contact the manufacturer for more information.

For information about how to contact Shiva or IBM, query in the Knowledge Base for one of the following articles: 

   ARTICLE-ID: Q65416
   TITLE     : Hardware and Software Third-Party Vendor Contact List, A-K

   ARTICLE-ID: Q60781
   TITLE     : Hardware and Software Third-Party Vendor Contact List, L-P

   ARTICLE-ID: Q60782
   TITLE     : Hardware and Software Third-Party Vendor Contact List, Q-Z
The third-party products discussed here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.

Additional query words: 4.00
Keywords : NTRAS ntsecurity kb3rdparty kbhw kbnetwork
Version : WINNT:3.5,3.51,4.0
Platform : winnt
Issue type : kbprb

THE INFORMATION PROVIDED IN THE MICROSOFT KNOWLEDGE BASE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND. MICROSOFT DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL MICROSOFT CORPORATION OR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES WHATSOEVER INCLUDING DIRECT, INDIRECT, INCIDENTAL, CONSEQUENTIAL, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF MICROSOFT CORPORATION OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. SOME STATES DO NOT ALLOW THE EXCLUSION OR LIMITATION OF LIABILITY FOR CONSEQUENTIAL OR INCIDENTAL DAMAGES SO THE FOREGOING LIMITATION MAY NOT APPLY.

Last reviewed: March 10, 1998
© 1998 Microsoft Corporation. All rights reserved. Terms of Use.