Partager via

Network Ports Used by Message Queuing

  • Article

Applies To: Windows Server 2008

Message Queuing uses different network ports depending on the message delivery mechanism that is specified when sending and receiving messages. This topic describes the network ports that are used by the specified delivery mechanisms and the relative performance of each delivery mechanism.

TCP/IP ports used by Message Queuing

This version of Message Queuing requires that the following TCP, UDP, and RPC ports to be opened for the indicated delivery mechanism:

Delivery mechanism Relative performance Required ports

Direct send only access for Message Queuing servers and independent clients

This is the fastest delivery mechanism because there is no overhead associated with Active Directory Domain Services lookup or web server processing. Use of this mechanism requires a direct connection to the target computer and therefore is not as flexible as other mechanisms.
  • TCP port 1801 - for message traffic and internal session management traffic between Queue Managers.

    Note
    If traffic is restricted to this port, outside clients can only send messages, and can only do so by using a direct format name.

Sending messages with Active Directory Domain Services access

This delivery mechanism is not as fast as "direct send only" delivery but is more flexible because this does not require a direct connection to the target computer.
  • TCP port 1801

  • UDP port 1801 - to allow remote clients to send a multicast broadcast message to automatically determine their site.

  • RPC port 2101 - default port for Active Directory Domain Services lookups. If this port is in use then the actual port number may be incremented by 11.

  • RPC port 135 - initial port used to discover ports in the 2xxx range that will be used subsequently for Active Directory Domain Services lookups.

  • RPC port 2103 - default port used to read public queues. If this port is in use then the actual port number may be incremented by 11.

  • RPC port 2105 - default port used to read private queues. If this port is in use then the actual port number may be incremented by 11.

Dependent clients sending messages through a supporting server.

This delivery mechanism is not as fast as "direct send only" delivery but offers the added flexibility of dependent client support and does not require a direct connection to the target computer.
  • TCP port 1801

  • RPC port 135 - initial port used to discover ports in the 2xxx range that will be used by dependent clients to use their supporting server.

  • RPC port 2103 - required for dependent clients to use their supporting server for send and receive. If this port is in use then the actual port number may be incremented by 11.

  • RPC port 2105 - required for dependent clients to use their supporting server for send and receive. If this port is in use then the actual port number may be incremented by 11.

HTTP

This delivery mechanism offers great flexibility but is not as fast as "direct send only" or sending/receiving with Active Directory Domain Services access.
  • TCP port 1801

  • The TCP port that is used for HTTP traffic by the Message Queuing Server which has the HTTP Support feature enabled. By default, Internet Information Services (IIS) uses TCP port 80 for HTTP traffic.

For more information about delivering Message Queuing messages using the HTTP or HTTPS protocols, see HTTP/HTTPS messages.

HTTPS

This delivery mechanism offers great flexibility and SSL encryption but is not as fast as "direct send only" or sending/receiving with Active Directory Domain Services access.
  • TCP port 1801

  • The TCP port that is used for HTTPS traffic by the Message Queuing Server which has the HTTP Support feature enabled. By default, Internet Information Services (IIS) uses TCP port 443 for HTTPS traffic.

For more information about delivering Message Queuing messages using the HTTP or HTTPS protocols, see HTTP/HTTPS messages.