Set the precedence of the NCP and CIFS protocols

  • 7012129
  • 11-Apr-2013
  • 11-Apr-2013


Novell Client 2 SP3 for Windows 7
Novell Client 2 SP3 for Windows 8
Novell Client 2 SP3 for Windows Server 2008 R2
Novell Client 2 SP3 for Windows Server 2012
Novell CIFS (Common Interface File System)
Novell NCP (Novell Core Protocol)
Microsoft Windows Network
Client for Windows Networks


Using an appliance that can accelerate CIFS/SMB traffic, but not NCP traffic.

Desired configuration is:
     - Use the Novell Client (NCP) to login to a new server
     - Use the Microsoft Client (CIFS) to connect to NSS volumes


Supply a UNC path name which is uniquely resolvable only using Microsoft methods such as NetBIOS or WINS. This will cause the the Novell Client to fail its connection attempt (because SLP and DNS fail to resolve the name specified in the UNC path), while the Microsoft Client will succeed.  (This is how the default CIFS advertising name of "NCPSERVERNAME_W" is helpful in contrast to just "NCPSERVERNAME" for the NCP server. See Novell CIFS Administration Guide.)
If the name provided in a UNC path or mapped drive target path can be resolved using DNS, both the Novell Client and the Microsoft Client will attempt connecting for that path, since both clients can resolve DNS information to an IPv4 address to make their respective NCP and SMB connection attempts.  In this case, the Windows "Network Provider Order" is used to decide which network provider Windows MPR will attempt to use first, and which network provider should be favored in the event of any "ties" at a Windows MUP level.
Moving the Microsoft Client to the top of the Windows "Network Provider Order" will ensure the Microsoft Client is given first chance at connecting for any UNC path provided at the MPR level, and is favored over the Novell Client at the MUP level for any paths both clients report being able to successfully access.  To set or verify the "Network Provider Order" on Windows Vista and later platforms, see TID 7000693