NetWare Core Protocol

Last updated

The NetWare Core Protocol (NCP) is a network protocol used in some products from Novell, Inc. It is usually associated with the client-server operating system Novell NetWare which originally supported primarily MS-DOS client stations, but later support for other platforms such as Microsoft Windows, the classic Mac OS, Linux, Windows NT, Mac OS X, and various flavors of Unix was added. [1]

Contents

The NCP is used to access file, print, directory, clock synchronization, messaging, remote command execution and other network service functions. It originally took advantage of an easy network configuration and small memory footprint of the IPX/SPX protocol stack. Since 1991 the TCP/IP implementation is available. [1]

Novell eDirectory uses NCP for synchronizing data changes between the servers in a directory service tree.

Technical information

The original IPX/SPX server implementation was provided only for Novell NetWare platform and now is obsolete. The TCP/IP implementation uses TCP/UDP port 524 and relies on SLP for name resolution.

For NCP operation in IPX/SPX networks the bare IPX protocol was used with Packet Type field set to 17. On the workstation (client station) side the IPX socket number of 0x4003 was used, on the server side the socket number of 0x0451.

The NCP PDU has the following structure:

OctetsField
2NCP type
1Sequence Number
1Connection Number, lower octet
1Task Number
1Connection Number, higher octet
1Completion Code (only in Reply packet)
1Connection Status (only in Reply packet)
varData

The NCP Type field determines the type of operation: [2]

ValueMeaning
0x1111Create a Service Connection
0x2222Service Request
0x3333Service Reply
0x5555Destroy Service Connection
0x7777Burst Mode Transfer
0x9999Request Being Processed (Server Busy)

Individual requests are identified by the Sequence Number (modulo 256). The Connection Number identifies an individual client station connection on the server. Novell Netware servers of version up to 2.x supported up to 255 connections and the Connection Number occupied only 1 octet. Later it was extended to 2 octets. Task number has value 3 in requests and 1 in replies. The Data field starts with NCP Function number octet which distinguishes individual services.

NumberFunction
0Login User Object
1Change User Password
2Map User to Station Set
3Map Object to Number
4Map Number to Object
5Get Station's Logged Information
8Map Number to Group Name
9Get Member Set M of Group G
10Enter Login Area
12Verify Network Serial Number
13Log Network Message
14Get Disk Utilization
15Scan File Information
16Set File Information
17Get File Server Information
18Get Network Serial Number
19Get Internet Address
20Login Object
21Get Object Connection List
22Get Station's Logged Information
23Get Encryption Key
24Login Object Encrypted
31Get Connection List from Object
50Create Bindery Object
51Delete Bindery Object
52Rename Object
53Get Bindery Object Id
54Get Bindery Object Name
55Scan Bindery Object
56Change Bindery Object Security
57Create Property
58Delete Property
59Change Bindery Property Security
60Scan Property
61Read Property Value
62Write Property Value
63Verify Bindery Object Password
64Change Bindery Object Password
65Add Bindery Object to Set
66Delete Bindery Object from Set
67Is Bindery Object In Set?
68Close Bindery
69Open Bindery
70Get Bindery Access Level
71Sacn Bindery Object Trustee Paths
72Get Bindery Object Access Level
73Is Calling Station a Manager?
74Verify Bindery Object Password Encrypted
75Change Bindery Object Password Encrypted
76List Relations of an Object
100Create Queue
101Destroy Queue
102Read Queue Current Status
103Set Queue Current Status
104Create Queue Job and File
105Close File and Start Queue Job
106Remove Job from Queue
107Get Queue Job List
108Read Queue Job Entry
109Change Queue Job Entry
110Change Queue Job Position
111Attach Queue Server to Queue
112Detach Queue Server from Queue
113Service Queue Job
114Finish Servicing Queue Job
115Abort Servicing Queue Job
116Change to Client's Rights
117Restore Queue Server Rights
118Read Queue Server Current Status
119Set Queue Server Current Status
120Get Queue Job Size
150Get Current Account Status
151Submit Account Charge
152Submit Account Hold
153Submit Account Note
200Check Console Privileges
201Get File Server Description Strings
202Set File Server Date and Time
203Disable File Server Login
204Enable File Server Login
205Get File Server Login Status
206Purge All Erased Files
207Disable Transaction Tracking
208Enable Transaction Tracking
209Set Console Broadcast
210Clear Connection Number
211Down File Server
212Get File System Statistics
213TTS Get Statistics
214Get Disk Cache Statistics
215Get Drive Mapping Table
216Get Physical Disk Statistics
217Get Disk Channel Statistics
218Get Connection's Task Information
219Get Connection's Open Files
220Get Connection's Using a File
221Get Physical Record Locks by Connection and File
222Get Physical Record Locks by File
223Get Logical Records by Connection
224Get Logical Record Information
225Get Connection's Semaphores
226Get Semaphore Information
227Get LAN Driver's Configuration Information
229Get Connection's Usage Statistics
230Get Object's Remaining Disk Space
231Get File Server LAN I/O Statistics
232Get File Server Misc Information
233Get Volume Information

The contents and the length of the rest of the Data field depends on the NCP Function.

Client-side implementations

Related Research Articles

Internetwork Packet Exchange (IPX) is the network layer protocol in the IPX/SPX protocol suite. IPX is derived from Xerox Network Systems' IDP. It also has the ability to act as a transport layer protocol.

In computer networking, Point-to-Point Protocol (PPP) is a data link layer communication protocol between two routers directly without any host or any other networking in between. It can provide loop detection, authentication, transmission encryption, and data compression.

A network operating system (NOS) is a specialized operating system for a network device such as a router, switch or firewall.

Network File System (NFS) is a distributed file system protocol originally developed by Sun Microsystems (Sun) in 1984, allowing a user on a client computer to access files over a computer network much like local storage is accessed. NFS, like many other protocols, builds on the Open Network Computing Remote Procedure Call system. NFS is an open IETF standard defined in a Request for Comments (RFC), allowing anyone to implement the protocol.

NetBIOS is an acronym for Network Basic Input/Output System. It provides services related to the session layer of the OSI model allowing applications on separate computers to communicate over a local area network. As strictly an API, NetBIOS is not a networking protocol. Operating systems of the 1980s ran NetBIOS over IEEE 802.2 and IPX/SPX using the NetBIOS Frames (NBF) and NetBIOS over IPX/SPX (NBX) protocols, respectively. In modern networks, NetBIOS normally runs over TCP/IP via the NetBIOS over TCP/IP (NBT) protocol. This results in each computer in the network having both an IP address and a NetBIOS name corresponding to a host name. NetBIOS is also used for identifying system names in TCP/IP (Windows). Simply stated, it is a protocol that allows communication of data for files and printers through the Session Layer of the OSI Model in a LAN.

In computing, the Windows Sockets API (WSA), later shortened to Winsock, is an application programming interface (API) that defines how Windows network application software should access network services, especially TCP/IP. It defines a standard interface between a Windows TCP/IP client application and the underlying TCP/IP protocol stack. The nomenclature is based on the Berkeley sockets API used in BSD for communications between programs.

NetBIOS Frames (NBF) is a non-routable network- and transport-level data protocol most commonly used as one of the layers of Microsoft Windows networking in the 1990s. NBF or NetBIOS over IEEE 802.2 LLC is used by a number of network operating systems released in the 1990s, such as LAN Manager, LAN Server, Windows for Workgroups, Windows 95 and Windows NT. Other protocols, such as NBT, and NBX (NetBIOS-over-IPX/SPX) also implement the NetBIOS/NetBEUI services over other protocol suites.

<span class="mw-page-title-main">Server Message Block</span> Network communication protocol for providing shared access to resources

Server Message Block (SMB) is a communication protocol used to share files, printers, serial ports, and miscellaneous communications between nodes on a network. On Microsoft Windows, the SMB implementation consists of two vaguely named Windows services: "Server" and "Workstation". It uses NTLM or Kerberos protocols for user authentication. It also provides an authenticated inter-process communication (IPC) mechanism.

<span class="mw-page-title-main">NetWare</span> Computer network operating system

NetWare is a discontinued computer network operating system developed by Novell, Inc. It initially used cooperative multitasking to run various services on a personal computer, using the IPX network protocol.

IPX/SPX stands for Internetwork Packet Exchange/Sequenced Packet Exchange. IPX and SPX are networking protocols used initially on networks using the Novell NetWare operating systems. They also became widely used on networks deploying Microsoft Windows LANS, as they replaced NetWare LANS, but are no longer widely used. IPX/SPX was also widely used prior to and up to Windows XP, which supported the protocols, while later Windows versions do not, and TCP/IP took over for networking.

The Apple Filing Protocol (AFP), formerly AppleTalk Filing Protocol, is a proprietary network protocol, and part of the Apple File Service (AFS), that offers file services for macOS, classic Mac OS, and Apple II computers. In OS X 10.8 Mountain Lion and earlier, AFP was the primary protocol for file services. Starting with OS X 10.9 Mavericks, Server Message Block (SMB) was made the primary file sharing protocol, with the ability to run an AFP server removed later in macOS 11 Big Sur. AFP supports Unicode file names, POSIX and access-control list permissions, resource forks, named extended attributes, and advanced file locking.

HP Jetdirect is the name of a technology sold by Hewlett-Packard that allows computer printers to be directly attached to a local area network. The "Jetdirect" designation covers a range of models from the external 1 and 3 port parallel print servers known as the 300x and 500x, to the internal EIO print servers for use with HP printers. The Jetdirect series also includes wireless print server models, as well as gigabit Ethernet and IPv6-compliant internal cards.

In computing, the NetWare File System (NWFS) was a file system based on a heavily optimized, journal-based FAT file system. It was used in the Novell NetWare network operating system. It was the only file system for all volumes in NetWare versions 2.x, 3.x and 4.x, and the default and only file system for the SYS: volume continuing through version 5.x. Novell developed two varieties of NWFS:

  1. 16-bit NWFS 286, used in NetWare 2.x
  2. 32-bit NWFS 386, used in NetWare 3.x through NetWare 6.x.
<span class="mw-page-title-main">Mercury Mail Transport System</span> Email server

Mercury Mail Transport System is a standards-compliant mail server developed by David Harris, who also develops the Pegasus Mail client.

NWLink is Microsoft's implementation of Novell's IPX/SPX protocols. NWLink includes an implementation of NetBIOS atop IPX/SPX.

A LAN Messenger is an instant messaging program for computers designed for use within a single local area network (LAN).

Novell Embedded Systems Technology (NEST) was a series of APIs, data formats and network protocol stacks written in a highly portable fashion intended to be used in embedded systems. The idea was to allow various small devices to access Novell NetWare services, provide such services, or use NetWare's IPX protocol as a communications system. Novell referred to this concept as "Extended Networks", and when the effort was launched they boasted that they wanted to see one billion devices connected to NetWare networks by year 2000. NEST was launched in mid-1994 countering Microsoft's similar Microsoft at Work efforts, which had been launched in 1993.

In computer networking, an Ethernet frame is a data link layer protocol data unit and uses the underlying Ethernet physical layer transport mechanisms. In other words, a data unit on an Ethernet link transports an Ethernet frame as its payload.

<span class="mw-page-title-main">GroupWise</span> Messaging and collaborative software platform

GroupWise is a messaging and collaboration platform from OpenText that supports email, calendaring, personal information management, instant messaging, and document management. The GroupWise platform consists of desktop client software, which is available for Windows,, and the server software, which is supported on Windows Server and Linux.

References

  1. 1 2 "Final Evaluation Report Novell, Incorporated NetWare 4.11 Server". NATIONAL COMPUTER SECURITY CENTER. 22 June 1998. Retrieved 2023-02-08., page 6
  2. "How to quickly identify error conditions with Ethereal". 15 Jul 2003. Retrieved 2023-02-08.