Cannot Log On to NetWare Server Using GSNW or CSNW with NCP Signature Level Set to 3 (216489)


The information in this article applies to:

  • Microsoft Windows 2000 Server
  • Microsoft Windows 2000 Advanced Server
  • Microsoft Windows 2000 Professional
  • Microsoft Windows 2000 Datacenter Server
This article was previously published under Q216489

SYMPTOMS

When you attempt to log on to a NetWare server from a Windows 2000-based computer using either Gateway Services for NetWare (GSNW) or Client Services for NetWare (CSNW), you may receive the following error message:
Name or password incorrect

CAUSE

This behavior can occur if the NCP packet signature level on the NetWare server is set to 3.

RESOLUTION

NCP client signature levels and NCP client signing are not supported in the Windows 2000 version of GSNW or CSNW. Because NCP client signing is not supported using the Windows 2000 version of GSNW or CSNW, set the signature level on the NetWare server to 2 (the default) to enable Windows 2000-based computers using GSNW or CSNW to log on without NCP packet signing.

MORE INFORMATION

GSNW and CSNW are "client pieces" (redirectors and providers) that enable Windows 2000-based computers to gain access to resources on NetWare networks. GSNW installed on a Windows 2000 server enables that server to function as an NCP gateway, allowing Microsoft (SMB) clients to gain access to NetWare resources using the gateway.

CSNW installed on a Windows 2000 Professional workstation enables the workstation to function as an NCP client and gain direct access to resources on a NetWare network. Installing GSNW or CSNW installs NWLink IPX/SPX/NetBIOS-Compatible Transport Protocol. Both GSNW and CSNW use NWLink as the underlying protocol for connectivity to NetWare networks.

NCP packet signing is an enhanced security feature that began in NetWare version 3.12 and is designed to protect NetWare networks from forged data packets. This enhanced security uses a message digest algorithm and a per-connection/per-request session state. NCP packet signing occurs at both the server and at the client.

Signature Level Values

The signature level values are:
  • Client Level

    • 0: Client does not sign
    • 1: (Default) Client signs if server requests
    • 2: Client signs if server can sign
    • 3: Client always signs and requires server to sign (or logon does not succeed)
  • Server Level

    • 0: Server does not sign
    • 1: Server signs if client requests
    • 2: (Default) Server signs if client can sign
    • 3: Server always signs and requires all clients to sign (or logon does not succeed)

Setting the Signature Level Value

You can set the signature level value on a NetWare server console using the following command:

set ncp packet signature=

You can set the signature level value for an NCP client in the Net.cfg file (NetWare DOS Requester Option) using the following command:

signature level=

Modification Type:MajorLast Reviewed:11/21/2003
Keywords:kb3rdPartyNetClient kbenv kberrmsg kbnetwork kbprb KB216489
©2003 Microsoft Corporation. All rights reserved.