Microsoft KB Archive/178517

= TCP ports, UDP ports, and RPC ports that are used by Message Queuing =

Article ID: 178517

Article Last Modified on 10/26/2007

-

APPLIES TO


 * Microsoft Message Queue Server 1.0
 * Microsoft Message Queuing 2.0
 * Microsoft Message Queuing 3.0

-



This article was previously published under Q178517



SUMMARY
The following ports are used for Microsoft Message Queuing operations:
 * TCP: 1801
 * RPC: 135, 2101*, 2103*, 2105*
 * UDP: 3527, 1801

The following is new for Message Queuing 3.0:

While Message Queuing uses the same ports that are used in earlier versions of the product, Message Queuing also introduces TCP port 389. TCP port 389 has to be open for MQIS queries that are made directly against Active Directory. Additionally, Message Queuing 3.0 introduces HTTP Messaging that requires that the port that is specified for the Message Queuing virtual directory be open also.

This information is useful for interpreting the following:
 * Netstat -a output
 * A network trace
 * Configuring a firewall



MORE INFORMATION
Message Queuing message traffic and internal session management traffic between Queue Managers is delivered over Winsock through reserved TCP port 1801.

The Message Queuing Independent Client multicasts a server discovery broadcast over reserved UDP port 1801.

Message Queuing Servers listen on TCP port 2101* for RPC-based MQIS and Active Directory lookups. Message Queuing 3.0 independent clients and Message Queuing servers make MQIS requests directly to Active Directory by using LDAP on TCP port 389.

Message Queuing Independent Clients and Servers listen on fixed TCP port 2103* and 2105* for RPC-based remote reads of their public queues and private queues. Also, the Dependent Client uses these two ports to communicate with its server for send and for receive.

There is a dynamic RPC port that is assigned by the RPC layer for handshaking with an Independent Client or with an RPC server for the Message Queuing Server to determine the fixed ports. This is typically port 135.

The internal "ping" mechanism for Message Queuing operates over reserved UDP port 3527.

When you use HTTP messaging in Message Queuing 3.0, Message Queuing message traffic and internal session management traffic between Queue Managers is delivered over Winsock through reserved TCP port 1801.


 * These port numbers may be incremented by 11 if the initial choice of RPC port is being used when Message Queuing initializes. A connecting QM queries port 135 to discover the 2xxx ports.

Additional query words: MSMQ

Keywords: kbproductlink kbtshoot kbfaq kbinfo KB178517

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.