VINES is an acronym for Virtual Integrated NEtwork Service. Like Novell NetWare, VINES's network services are based on the Xerox XNSstack.
James Allchin, who later worked as Group Vice President for Platforms at Microsoft until his retirement on January 30, 2007, was the chief architect of Banyan VINES.
VINES technology
VINES ran on a low-level protocol known as VIP—the VINES Internetwork Protocol—that was essentially identical to the lower layers of the Xerox Network Systems (XNS) protocols. Addresses consist of a 32-bit address and a 16-bit subnet that map to the 48-bit Ethernet address to route to machines. This means that, like other XNS-based systems, VINES can only support a two-level internet.
A set of routing algorithms, however, set VINES apart from other XNS systems at this level. The key differentiator, ARP (Address Resolution Protocol), allowed VINES clients to automatically set up their own network addresses. When a client first boots up, it broadcast a request on the subnet asking for servers, which responds with suggested addresses. The client used the first to respond, although the servers could hand off "better" routing instructions to the client if the network changed. The overall concept resembled AppleTalk's AARP system, with the exception that VINES required at least one server, whereas AARP functioned as peer-to-peer. Like AARP, VINES required an inherently "chatty" network, sending updates about the status of clients to other servers on the internetwork.
Rounding out its lower-level system, VINES used RTP (the Routing Table Protocol), a low-overhead message system for passing around information about changes to the routing, and ARP to determine the address of other nodes on the system. These closely resembled the similar systems used in other XNS-based protocols. VINES also included ICP (the Internet Control Protocol), which it used to pass error-messages and metrics.
At the middle layer level, VINES used fairly standard software. The unreliable datagram service and data-stream service operated essentially identically to UDP and TCP on top of IP. VINES added a reliable message service as well, a hybrid of the two that offered guaranteed delivery of single packets.
Banyan offered customers TCP/IP as an extra cost option for owners of standard Vines servers. This extra charge for TCP/IP on VINES servers continued long after TCP/IP server availability had become commoditized.
At the topmost layer, VINES provided the standard file and print services, as well as the unique StreetTalk, a globally consistent name service. Banyan has a version of StreetTalk that ran natively on an NT server.[1] Using a globally distributed, partially replicated database, StreetTalk could meld multiple widely separated networks into a single network that allowed seamless resource-sharing. It accomplished this through its rigidly hierarchical naming-scheme; entries in the directory took the form item@group@organization (similar to the naming format used in the XNS Clearinghouse directory service: item:group:organization). This applied to user accounts as well as to resources like printers and file servers.
VINES client software ran on most earlier PC-based operating systems, including MS-DOS and earlier versions of Microsoft Windows. It was lightweight on the client, and hence remained in use during the latter half of the 1990s on many older machines that could not run other networking stacks. This occurred on the server side as well, as VINES generally offered good performance, even from mediocre hardware.
The U.S. State Department was an early adopter of the VINES technology. Able to take advantage of the then high-speed 56k modems for telephonic connectivity of the developed world to the limited telephone modem speeds of 300 baud over bad analog telephone systems in developing countries, VINES linked embassies around the world. VINES also features built-in point-to-point and group chat capability that was useful for basic communication over secure lines.
Defense Department adoption
By the late 1980s, the US Marine Corps was searching for simple, off-the-shelf worldwide network connectivity with rich built-in email, file, and print features. By 1988, the Marine Corps had standardized on VINES[2] as both its garrison (base) and forward-deployed ground-based battlefield email-centric network operating system.
Using both ground-based secure radio channels and satellite and military tactical phone switches, the Marine Corps was ready for its first big test of VINES: the 1990-1991 Gulf War. Units were able to seamlessly coordinate ground, naval, and air strikes across military boundaries by using the chat function to pass target lists and adjust naval gun fire on the fly. Ground fire support coordination agencies used VINES up and down command channels—from Battalion-to-Regiment through Division-to-Corps and Squadron-to-Group to Aircraft Wing-to-Corps, as well as in peer-to-peer unit communication. [citation needed]
3Com's journey into network operating system development began in the late 1970s. In 1979, they introduced their first network operating system, called 3+Share. It allowed multiple users to access files and resources on a shared server. However, it wasn't until 1982 that 3Com released 3Server, which was a significant step forward.
3Server was designed to work with 3Com's Ethernet hardware and was aimed at creating local area networks (LANs). It provided file and print sharing capabilities, enabling multiple computers to access common resources like printers and files. It operated on the XNS (Xerox Network Systems) protocol suite.
Over the years, 3Com continued to refine and improve its network operating systems. In 1985, they introduced 3+Open, which added support for third-party hardware. 3+Open was a significant advancement in 3Com's network operating system lineup. Introduced in 1985, it expanded on the capabilities of their previous offerings by providing support for third-party hardware and software. This allowed 3+Open to work with a wider range of network devices and systems, increasing its compatibility and appeal to a broader audience.
3Com's contribution to Microsoft's network and server software capabilities is closely tied to their collaboration on the development of LAN Manager. LAN Manager was Microsoft's networking software that aimed to provide file and print services for PCs connected in a network. In the late 1980s, Microsoft partnered with 3Com to integrate 3+Open's networking capabilities into LAN Manager.
This collaboration led to the creation of LAN Manager 2.0, which was released in 1989. This version of LAN Manager incorporated technologies from both Microsoft and 3Com, resulting in improved networking capabilities and compatibility. It enabled Microsoft to strengthen its networking offerings, making it a more competitive player in the network operating system space.
Microsoft's experience with LAN Manager laid the foundation for their subsequent development of Windows NT and Windows Server operating systems. The knowledge and technologies gained from working with 3Com's networking solutions contributed to the evolution of Microsoft's network and server software capabilities, helping them become a dominant force in the networking and server industry.
For a decade, Banyan's OS competitors, Novell and Microsoft, dismissed the utility of directory services. Consequently, VINES dominated what came to be called the "directory services" space from 1985 to 1995. While seeming to ignore VINES, Novell and eventually Microsoft—companies with a flat server or domain-based network model—came to realize the strategic value of directory services. With little warning, Novell went from playing down the value of directory services to announcing its own: NetWare Directory Services (NDS). Eventually, Novell changed NDS to mean Novell Directory Services, and then renamed that to eDirectory.[3]
For Windows 2000 however, Microsoft included Active Directory, an LDAP directory service based on the directory from its Exchange mail server.[3] While VINES is limited to a three-part name, user.company.org, like Novell's NDS structure, Active Directory is not bound by such a naming convention. Active Directory features an additional capability that both NDS and VINES lack, its "forest and trees" organizational model. The combination of better architecture and with marketing from a company the size of Microsoft doomed StreetTalk, VINES as an OS, and finally Banyan itself.
Decline
By the late 1990s, VINES's once-touted StreetTalk Services's non-flat, non-domain model had lost ground to newer technology, despite its built-in messaging, efficiency and onetime performance edge. Banyan was unable to market its product far beyond its initial base of multi-national and government entities.
The company lost ground in the networking market, and VINES sales dropped. Banyan increasingly turned to StreetTalk as a differentiator, eventually porting it to NT as a stand-alone product and offering it as an interface to LDAP systems. [citation needed]
Banyan continued to operate a closed OS. This required hardware manufacturers to submit hardware and driver requirements so that Banyan could write drivers for each peripheral. When more open systems with published APIs began to appear, Banyan did not alter their model. This made it difficult for client-side support to handle the explosive growth in, for example, printers. As competitors began to adopt some of VINES's outstanding wide area networking protocols and services, manufacturers were less inclined to send a unit to Banyan for VINES specific drivers when competitors allowed them to write their own.
Dropping the Banyan brand for ePresence in 1999, as a general Internet services company, the firm sold its services division to Unisys in late 2003 and liquidated its remaining holdings in its Switchboard.com subsidiary.
Version history
1984: Banyan VINES 1.0
1989: Banyan VINES 2.1
1990: Banyan VINES 3.0
1991: Banyan VINES 4.11
1992: Banyan VINES 5.0
1994: Banyan VINES 5.50
1997: Banyan VINES 7.0
Related Research Articles
AppleTalk is a discontinued proprietary suite of networking protocols developed by Apple Computer for their Macintosh computers. AppleTalk includes a number of features that allow local area networks to be connected with no prior setup or the need for a centralized router or server of any sort. Connected AppleTalk-equipped systems automatically assign addresses, update the distributed namespace, and configure any required inter-networking routing.
A local area network (LAN) is a computer network that interconnects computers within a limited area such as a residence, school, laboratory, university campus or office building. By contrast, a wide area network (WAN) not only covers a larger geographic distance, but also generally involves leased telecommunication circuits.
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.
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.
Novell, Inc. was an American software and services company headquartered in Provo, Utah, that existed from 1980 until 2014. Its most significant product was the multi-platform network operating system known as Novell NetWare.
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.
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.
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.
Network-attached storage (NAS) is a file-level computer data storage server connected to a computer network providing data access to a heterogeneous group of clients. The term "NAS" can refer to both the technology and systems involved, or a specialized device built for such functionality.
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.
LAN Manager is a discontinued network operating system (NOS) available from multiple vendors and developed by Microsoft in cooperation with 3Com Corporation. It was designed to succeed 3Com's 3+Share network server software which ran atop a heavily modified version of MS-DOS.
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.
cc:Mail is a discontinued store-and-forward LAN-based email system originally developed on Microsoft's MS-DOS platform by Concentric Systems, Inc. in the 1980s. The company, founded by Robert Plummer, Hubert Lipinski, and Michael Palmer, later changed its name to PCC Systems, Inc., and then to cc:Mail, Inc. At the height of its popularity, cc:Mail had about 14 million users, and won various awards for being the top email software package of the mid-1990s.
A network socket is a software structure within a network node of a computer network that serves as an endpoint for sending and receiving data across the network. The structure and properties of a socket are defined by an application programming interface (API) for the networking architecture. Sockets are created only during the lifetime of a process of an application running in the node.
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.
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.
MS-Net, sometimes stylized as MS-NET, was a network operating system sold by Microsoft in the 1980s, the earliest days of local area networking.
The Sniffer was a computer network packet and protocol analyzer developed and first sold in 1986 by Network General Corporation of Mountain View, CA. By 1994 the Sniffer had become the market leader in high-end protocol analyzers. According to SEC 10-K filings and corporate annual reports, between 1986 and March 1997 about $933M worth of Sniffers and related products and services had been sold as tools for network managers and developers.
This page is based on this Wikipedia article Text is available under the CC BY-SA 4.0 license; additional terms may apply. Images, videos and audio are available under their respective licenses.
