Microsoft Network Adapter Multiplexor Protocol (NAMEP) is a Microsoft proprietary protocol that runs on top of the common network transports. It provides separate virtual channels for multiple protocols to run simultaneously without interfering with each other. The NAMEP, which appears as an Internet Assigned Numbers Authority (IANA)-registered UDP port number, can be used by any application or device that needs to send data over one connection and use it for several different types of traffic at the same time.
Network Adapter Multiplexor Protocol was introduced in Windows Server 2003 R2 Infrastructure Update and has become part of the operating system feature set since then. Several years later, Microsoft released Windows Server 2008 R2 Service Pack 1 with significant changes to this protocol. The NAMEP infrastructure was fully rewritten for this version of the operating system. The new implementation provides much better performance, scalability, stability, and security.\
The protocol's NIC Teaming is one component. That is to say, the Network Adapter Multiplexor Protocol is only utilized when two or more adapters are connected to a single PC using a NIC Teaming configuration. Windows will turn off any standalone adapter on your computer if you don't use it.
As long as you meet these requirements, you can use the Network Adapter Multiplexor Protocol to provide network fault tolerance and increased bandwidth performance between servers and their clients.
Network Adapter Multiplexor Protocol has been around for years so chances are pretty high to find it on almost any modern Windows server infrastructure. Network Adapter Multiplexor Protocol (NAMEP) is indeed a very easy way to boost your network performance between your servers. The networking industry however today still doesn't use the protocol as much as it could or should do. Let's have a look at NAMEP and why you might want to think about using it more widely.

The list of major changes goes as follows:

Dynamic service instance allocation to each protocol session based on dynamic port ranges in use by the protocols

  • Support for IPv6 in addition to IPv4.
  • Protocol sessions can communicate with other sessions running on the same machine or in another network node in the cluster group through loopback addresses without using an external network address translation (NAT) interface between nodes.
  • Signed drivers provided by Microsoft digitally sign all client and server components statically linked with them. This enables customers who run Network Load Balancing to load balance traffic destined to the loopback address.
  • A new filter driver provides more flexible packet filtering capabilities from user mode and an even higher level of security for operating system components, applications, and users by implementing a mandatory access control policy.
  • The protocol stack does not require any modifications to be made in Windows Filtering Platform (WFP) hooking procedures for this version of the NAMEP protocol stack.
  • Fully compatible with IPv4.
  • Support of non-IP protocols over separate channels through a single virtual connection provides additional flexibility of using traffic offload on many different types of physical networks without having to add new transport support inside NAMEP itself.