Operations << >>

MTA Transport Stack

An MTA transport stack contains configuration information about the network software and hardware on the local computer running the Microsoft Exchange Server. The network software and hardware are responsible for routing messages between two sites or from one site to a foreign X.400 system. Multiple transport stacks and X.400 Connectors can be installed on other servers in the same site to provide load balancing and fault-tolerant connections for the remote Microsoft Exchange Server site.

The following MTA transport stacks can be used.

TP0/X.25 using an Eicon port adapter   TP0/X.25 provides both dial-up and direct communication in compliance with the OSI X.25 Recommendation. Eicon X.25 network software (and possibly hardware) must be installed and running on the server before installing the MTA transport stack. You can install multiple X.25 transport stacks on a server, and you can install multiple Eicon X.25 port adapters on one server. A separate MTA transport stack is required for each X.25 port on an adapter.

TCP/IP   TCP/IP using the RFC 1006 specification is a mechanism for running OSI software, such as X.400 messaging systems, on a TCP/IP network. Microsoft Exchange Server uses Windows NT TCP/IP services. The Microsoft Exchange Server MTA uses port 102 as specified by RFC1006.

TP4/CLNP   OSI transport layer protocol TP4/CLNP provides an OSI interface across a local area network (LAN). Microsoft Exchange Server has an interface that allows it to work with the Windows NT TP4 driver. It uses this interface to communicate with other systems using TP4 during message transport. In CLNP, data is transferred without using a connection request. In Windows NT, TP4 is designed for use in a connectionless mode network. TP4 network address information is determined by the server running the transport stack. The network service access point (NSAP) address used by TP4 is configured in the Windows NT Control Panel on that server.