NWLink

Last updated

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

Contents

NWLink packages data to be compatible with client/server services on NetWare Networks. However, NWLink does not provide access to NetWare File and Print Services. To access the File and Print Services the Client Service for NetWare needs to be installed.

NWLink connects NetWare servers through the Gateway Service for NetWare or Client Service for NetWare and provides the transport protocol that connects Windows operating systems to IPX/SPX NetWare networks and compatible operating systems. NWLink supports NetBIOS and Windows Sockets application programming interfaces (API).

NWLink protocols are as follows:

NWLink also provides the following functionalities:

NWLink IPX/SPX/NetBIOS Compatible Transport is Microsoft's implementation of the Novell IPX/SPX (Internetwork Packet Exchange/Sequenced Packet Exchange) protocol stack. The Windows XP implementation of the IPX/SPX protocol stack adds NetBIOS support. The main function of NWLink is to act as a transport protocol to route packets through internetworks. By itself, the NWLink protocol does not allow you to access the data across the network. If you want to access NetWare File and Print Services, you must install NWLink and Client Services for NetWare (software that works at the upper layers of the OSI model to allow access to file and print services). One advantage of using NWLink is that is easy to install and configure.[ citation needed ]

The only options that are configured for NWLink are the internal network number and the frame type. Normally, you leave both settings at their default values. The internal network number is commonly used to identify NetWare file servers. It is also used when you are running File and Print Services for NetWare or using IPX routing. The frame type specifies how the data is packaged for transmission over the network. If the computers that are using NWLink use different frame types, they are not able to communicate with each other. The default setting for frame type is Auto Detect, which will attempt to automatically choose a compatible frame type for your network. If you need to connect to servers that use various frame types, you should configure Manual Frame Type Detection, which will allow you to use a different frame type for each network.

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 connection 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.

Xerox Network Systems (XNS) is a computer networking protocol suite developed by Xerox within the Xerox Network Systems Architecture. It provided general purpose network communications, internetwork routing and packet delivery, and higher level functions such as a reliable stream, and remote procedure calls. XNS predated and influenced the development of the Open Systems Interconnection (OSI) networking model, and was very influential in local area networking designs during the 1980s.

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. Older operating systems 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 saying, it is a protocol that allows communication of 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.

Server Message Block (SMB) is a communication protocol that Microsoft created for providing shared access to files and printers across nodes on a network. It also provides an authenticated inter-process communication (IPC) mechanism. Microsoft first implemented SMB in the LAN Manager operating system, at which time SMB used the NetBIOS protocol as its underlying transport. Later, Microsoft implemented SMB in Windows NT 3.1 and has been updating it ever since, adapting it to work with newer underlying transports: TCP/IP and NetBT. SMB implementation consists of two vaguely named Windows services: "Server" and "Workstation". It uses NTLM or Kerberos protocols for user authentication.

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.

Banyan VINES is a network operating system developed by Banyan Systems for computers running AT&T's UNIX System V.

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, and also became widely used on networks deploying Microsoft Windows LANS, as they replaced NetWare LANS, but is no longer widely used. IPX/SPX was also widely used prior to and up to Windows XP era, that supported the protocols, while later Windows versions do not, and TCP/IP took over for networking.

NetBIOS over TCP/IP is a networking protocol that allows legacy computer applications relying on the NetBIOS API to be used on modern TCP/IP networks.

Windows Messenger service Local network notification service for Microsoft Windows

Messenger service is a network-based system notification Windows service by Microsoft that was included in some earlier versions of Microsoft Windows.

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.

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

3+Share, also known simply as 3+ or 3 Plus, was a pioneering file and print sharing product from 3Com. Introduced in the early 1980s, 3+Share was competitive with Novell's NetWare in the network server business throughout the 1980s. It was replaced by the joint Microsoft-3Com LAN Manager in 1990, but 3Com exited the server market in 1991.

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.

NetWare Link Services Protocol (NLSP) is a routing protocol for Internetwork Packet Exchange based on the Intermediate-System-to-Intermediate-System (IS-IS) protocol developed by the International Organization for Standardization (ISO). NLSP enables NetWare servers to exchange routing and service information without the high broadcast overhead generated by Routing Information Protocol and Service Advertising Protocol. Instead of periodically retransmitting its information every few minutes like RIP and SAP, NLSP only transmits every two hours, or when there is a change in a route or service, making it much more suitable for use over a wide area network.

Routing and Remote Access Service (RRAS) is a Microsoft API and server software that makes it possible to create applications to administer the routing and remote access service capabilities of the operating system, to function as a network router. Developers can also use RRAS to implement routing protocols. The RRAS server functionality follows and builds upon the Remote Access Service (RAS) in Windows NT 4.0.

References

  1. "NWLink". Microsoft. Archived from the original on February 1, 2008.
  2. "Understanding NWLink". Microsoft. January 21, 2005. Archived from the original on April 22, 2008.
  3. "What is NetWare Link (NWLink)? - Definition from Techopedia". Techopedia.com. Retrieved 2019-06-05.