
What Is Internet Packet Exchange (IPX)? History, How It Worked and Why It Disappeared
If you have ever read about old Novell NetWare networks, or seen the letters IPX in an old networking textbook, you have met Internet Packet Exchange. In the 1980s and 1990s, Internet Packet Exchange (IPX) was one of the most widely used network protocols in the world — the protocol that carried file and print traffic for millions of office networks long before TCP/IP became the universal standard. Today it is almost gone from production networks, but it still appears in certification study, in legacy system migrations, and — confusingly — under the same initials in modern telecom.
This guide explains what Internet Packet Exchange was, how it worked, why it lost to TCP/IP, what the same name means in telecom today, and whether you still need to know about it.
What Is Internet Packet Exchange (IPX)?
Internet Packet Exchange (IPX) is a connectionless network-layer protocol developed by Novell for its NetWare network operating system. It was based on Xerox’s Xerox Network Systems (XNS) Internet Datagram Protocol (IDP), and it provided the addressing and packet delivery that let NetWare clients and servers communicate across a local area network and, with routers, across multiple networks.
In the OSI model, IPX sits at the network layer (Layer 3), in the same role that IP plays in the TCP/IP stack. Above it sat transport protocols — most importantly Sequenced Packet Exchange (SPX), which added reliability, and NetWare Core Protocol (NCP), which handled file and print services. Together, the stack was usually written as IPX/SPX, in the same way people write TCP/IP.
IPX was fast and simple, which was exactly what local networks of its era needed. It had no handshake, no retransmission and no flow control of its own, so it added very little overhead. That made it ideal for a busy office LAN, where a file server was a few metres away and a lost packet was cheap to recover at a higher layer — and it made it a poor choice for the wide-area internet, for reasons we will come to.
A Short History of IPX
The story of IPX is the story of the local area network itself.
- Early 1980s: Xerox developed the XNS protocol suite at its Palo Alto Research Center. Its Internet Datagram Protocol became the template for several later protocols.
- 1983: Novell introduced NetWare, using IPX as its native network protocol. As NetWare became the dominant network operating system of the decade, IPX became the dominant LAN protocol with it.
- Late 1980s to mid-1990s: IPX was everywhere. Novell NetWare ran in a large share of corporate networks, and IPX carried their file, print and directory traffic. Games of the era, including Doom and Warcraft II, also used IPX for multiplayer play over a LAN.
- Mid-1990s: the public internet, built on TCP/IP, exploded. Organisations that had run separate NetWare networks now needed to connect to the internet, and running two protocol stacks on every machine was expensive and complicated.
- 1998: NetWare 5 shipped with native TCP/IP support, and Novell began the shift away from IPX as the default protocol.
- 2000s onwards: IPX faded from new deployments. Microsoft removed IPX support from Windows, Novell moved on, and TCP/IP became the single standard for almost every network. IPX survives today mainly in legacy systems, in museums of computing history, and in the telecom meaning described below.
How Internet Packet Exchange Worked
Understanding IPX starts with its addressing, because IPX addresses were very different from IP addresses — and the difference explains both its strengths and its limits.
IPX addressing
An IPX address has three parts:
- Network number (32 bits): a number identifying the network segment. Unlike IP subnetting, this was usually assigned by the network administrator, and every device on the same segment shared it.
- Node number (48 bits): the unique address of the device on that network — in practice, the device’s MAC address. Because the MAC address was already unique, IPX needed no equivalent of DHCP or manual host addressing.
- Socket number (16 bits): identifies the process or service on the device, similar to a port number in TCP/IP. Well-known sockets were reserved for services such as NCP, RIP and SAP.
A complete IPX address therefore looked something like 00000001.00A0243F5B12.0451: network, node and socket, written in hexadecimal. That self-configuring addressing was one of IPX’s great conveniences — a workstation could join the network and be reachable without any address configuration at all.
The IPX packet
An IPX packet carried a small header: a checksum, the packet length, a transport control field that counted how many routers the packet had crossed, a packet type, and the destination and source addresses described above. The header was only 30 bytes, which kept overhead low.
IPX was connectionless and unreliable by design. It made a best effort to deliver each packet, once, and if the packet was lost or damaged, IPX itself did nothing about it. Reliability was the job of the protocol above it: SPX provided connection-oriented, reliable delivery where it was needed, and NCP had its own acknowledgement and retry logic. This division of labour was deliberate — not every application needs guaranteed delivery, and a protocol that does not provide it can be faster.
IPX Routing: RIP and SAP
IPX could not have worked across a large organisation without routing, and its routing protocols are a large part of why it eventually lost.
Routing Information Protocol (RIP)
IPX RIP was a distance-vector routing protocol, similar in concept to the RIP used with IP, but with its own implementation. Routers exchanged their whole routing table with neighbouring routers every 60 seconds, and measured distance in hops, with a maximum of 15 hops — a 16th hop meant the destination was unreachable. For a small office network, that was simple and adequate. For a large, multi-site network, the constant broadcast of full routing tables consumed a noticeable share of bandwidth, and the 15-hop limit put a hard ceiling on network size.
Service Advertising Protocol (SAP)
SAP solved a different problem: how does a client find a service? NetWare servers, printers and other resources advertised themselves with SAP broadcasts, again every 60 seconds, and routers and servers kept tables of available services. A client that needed a file server could look it up by name instead of knowing its address. This was convenient, and it also meant SAP broadcasts added to the traffic problem on large networks — in an era when a WAN link might be only 64 kbit/s, a flood of routing and service broadcasts was a real cost.
Both protocols broadcast frequently and carried complete tables, rather than sending small updates only when something changed. That design choice, reasonable on a fast LAN, did not scale to the internet.
IPX vs SPX: What Is the Difference?
IPX and SPX are often named together, but they do different jobs:
- IPX is the network-layer, connectionless protocol that addresses and delivers individual packets. It is the equivalent of IP in TCP/IP.
- SPX is the transport-layer, connection-oriented protocol that runs on top of IPX. It establishes a connection, numbers packets, acknowledges receipt, retransmits lost packets and controls flow. It is the equivalent of TCP in TCP/IP.
An application that needed reliability used SPX; an application that valued speed over reliability — or that handled its own acknowledgements, as NCP did — used IPX directly. The pair, IPX/SPX, was therefore the full Novell stack, just as TCP/IP is the full internet stack.
Internet Packet Exchange vs TCP/IP
The comparison that decided IPX’s fate is worth making directly, because it shows that TCP/IP did not win by being faster on a LAN — it won by being better at the things that mattered once networks grew.
- Addressing: IPX used a fixed network + MAC-address node structure; no configuration, but no flexibility either. IP used hierarchical, configurable addresses that could be aggregated, subnetted and routed efficiently at internet scale.
- Routing: IPX RIP broadcast full tables every 60 seconds and capped at 15 hops. IP routing protocols such as OSPF and BGP send updates only when things change and scale to millions of routes.
- Scalability: IPX SAP broadcasts grew with the number of services on the network. TCP/IP’s DNS and directory services scaled far better, and did not rely on constant broadcast.
- Interoperability: TCP/IP was an open standard supported by every vendor and every operating system. IPX was closely tied to Novell, even though it was licensed to others.
- The internet: above all, the internet itself ran on TCP/IP. A network that spoke only IPX could not connect to it directly. Once internet connectivity became essential, every organisation needed TCP/IP anyway, and keeping a second stack for the LAN stopped making sense.
IPX was, in many ways, the better LAN protocol of its time — simpler, faster to set up and with less administrative overhead. TCP/IP was the better internet protocol, and the internet changed what “better” meant.
Why Internet Packet Exchange Disappeared
Several forces combined to end IPX in production networks:
- The internet became the network: email, the web and remote access all ran on TCP/IP. Dual-stack networks were costly and confusing to support.
- Novell moved on: NetWare 5’s native TCP/IP support, and Novell’s later focus on other products, removed the platform that had made IPX necessary.
- Operating system support ended: Microsoft dropped IPX from Windows Vista and later versions, and other vendors followed, so new systems simply could not speak it.
- Scaling limits: the broadcast-heavy RIP and SAP design, and the 15-hop limit, made IPX unsuitable for the large, multi-site, multi-vendor networks organisations were building.
- No security model for the open internet: IPX had no equivalent of the security ecosystem that grew around IP — no mature firewalls, NAT, IPsec or site-to-site VPN standards. As networks connected to the outside world, that gap mattered.
IPX Today: A Different Meaning in Telecom
Today, if you see the initials IPX in a telecom or mobile context, it almost certainly does not mean Novell’s protocol. It means IP Exchange — the GSMA-standard interconnection framework that lets mobile operators exchange IP-based services such as voice over LTE (VoLTE), roaming data, SMS and signalling between networks, through a private, managed IP backbone rather than the public internet.
Telecom IPX is about secure, quality-guaranteed interconnection between carriers. It provides service-level agreements, end-to-end quality of service and a single point of interconnection for each operator, instead of a mesh of bilateral agreements. The shared name is a coincidence of acronyms: both are ways of exchanging packets over IP networks, but one is a 1980s LAN protocol and the other is a modern carrier interconnection model. When you read a source about IPX, check the date and the context — a 1995 source means Novell, a 2025 source about roaming means telecom.
Do You Still Need to Know About IPX?
For most working network engineers, IPX is history, not a daily skill. But it is still worth knowing about in four situations.
- Legacy systems: some industrial, medical or government systems still run old NetWare applications. If you inherit one, you need to understand what it is and how to isolate it safely, because it cannot be patched like a modern system.
- Migration projects: retiring a legacy system means understanding what protocols it depends on before you switch it off. An unrecognised IPX dependency can break a service that nobody realised was still running.
- Study and certification: protocol history still appears in networking study, because IPX illustrates — better than most examples — how addressing, routing and service discovery work, and how design trade-offs that seem right on a LAN can fail at scale.
- Security thinking: using network security software to monitor which protocols are actually running on a network is a good habit. A legacy protocol nobody remembers is also a legacy protocol nobody is monitoring, and that is exactly the kind of blind spot an attacker can use.
Frequently Asked Questions
What does IPX stand for?
In Novell networking, IPX stands for Internetwork Packet Exchange — the full formal name, sometimes written without the “work”. In modern telecom, IPX stands for IP Exchange, a carrier interconnection framework. Both are usually shortened to IPX, which is why context matters.
What is Internet Packet Exchange used for?
Historically, IPX was used to carry file, print and directory traffic on Novell NetWare local area networks. It addressed and delivered packets between clients, servers and routers. In modern telecom, IP Exchange is used to interconnect mobile operators for roaming, VoLTE voice, data and signalling services.
Is IPX still used today?
Novell’s IPX is no longer used in new networks and has been removed from modern operating systems. It survives only in some legacy systems. The telecom IP Exchange of the same name is current and widely used by mobile operators.
What is the difference between IPX and TCP/IP?
IPX was a simple, fast, connectionless protocol designed for a local area network, with addressing based on the device’s MAC address. TCP/IP is a suite of open standards designed to scale to a global internet, with hierarchical addressing, scalable routing and a mature security ecosystem. TCP/IP replaced IPX once internet connectivity and large multi-site networks became the norm.
What replaced IPX?
TCP/IP replaced IPX for general networking, with IP taking over the network-layer role and TCP taking over the reliable transport role that SPX had provided. Novell made TCP/IP native in NetWare 5 in 1998, which was the turning point.
Conclusion
Internet Packet Exchange was the right protocol for the network of its time: simple, self-configuring and fast on a local area network. It lost not because it was badly designed, but because the network it was designed for stopped being the network that mattered. The internet’s growth rewarded scalable addressing, efficient routing and open standards — qualities TCP/IP had and IPX did not. IPX’s story is a useful reminder for every network decision today: the protocol that wins is not always the fastest on the bench, but the one that scales, interoperates and can be secured as the world changes around it.


