[Developer]

Microsoft Server Ports

This is a great resource if you are new to System Administration or Firewalls.

Overview

The following list provides an overview of the information that this article contains:

• The "System services ports" section of this article contains a brief description of each service, displays the logical name of that service, and indicates the ports and protocols that each service requires for correct operation. Use this section to help identify the ports and protocols that a particular service uses.
• The "Ports and protocols" section of this article includes a table that summarizes the information from the "System Services Ports" section. The table is sorted by port number instead of by the service name. Use this section to quickly determine which services listen on a particular port.

This article uses certain terms in specific ways. To help avoid confusion, make sure that you understand how this document uses these terms. The following list describes these terms:

• System services: The Windows server system includes many products, such as the Microsoft Windows 2000 Server family, Microsoft Windows Server 2003 family, Microsoft Exchange 2000 Server, and Microsoft SQL Server 2000. Each of these products include many components; system services is one of those components. System services that are required by a particular computer are either started automatically by the operating system during startup or are started as required during typical operations. For example, some system services that are available on computers that are running Windows Server 2003, Enterprise Edition, include the Server service, the Print Spooler service, and the World Wide Web Publishing Service. Each system service has a friendly service name and a service name. The friendly service name is the name that appears in graphical management tools such as the Services Microsoft Management Console (MMC) snap-in. The service name is the name that is used with command-line tools and with many scripting languages. Each system service may provide one or more network services.
• Application protocol: In the context of this article, an application protocol is a high-level network protocol that uses one or more TCP/IP protocols and ports. Examples of application protocols include Hypertext Transfer Protocol (HTTP), server message blocks (SMBs), and Simple Mail Transfer Protocol (SMTP).
• Protocol: Operating at a lower level than the application protocols, TCP/IP protocols are standard formats for communicating between devices on a network. The TCP/IP suite of protocols includes TCP, User Datagram Protocol (UDP), and Internet Control Message Protocol (ICMP).
• Port: This is the network port that the system service listens on for incoming network traffic.

This article does not specify which services rely on other services for network communication. For example, many services rely on the remote procedure call (RPC) or DCOM features in Microsoft Windows to assign them dynamic TCP ports. The Remote Procedure Call service coordinates requests by other system services that use RPC or DCOM to communicate with client computers. Many other services rely on network basic input/output system (NetBIOS) or SMBs, protocols that are actually provided by the Server service. Others rely on HTTP or on Hypertext Transfer Protocol Secure (HTTPS). These protocols are provided by Internet Information Services (IIS). A full discussion of the architecture of the Windows operating systems is beyond the scope of this article. However, detailed documentation on this subject is available on Microsoft TechNet and on the Microsoft Developer Network (MSDN). While many services may rely on a particular TCP or UDP port, only a single service or process can be actively listening on that port at any one time.

When you use RPC with TCP/IP or with UDP/IP as the transport, inbound ports are frequently dynamically assigned to system services as required; TCP/IP and UDP/IP ports that are higher than port 1024 are used. These are frequently informally referred to as "random RPC ports." In these cases, RPC clients rely on the RPC endpoint mapper to tell them which dynamic port(s) were assigned to the server. For some RPC-based services, you can configure a specific port instead of letting RPC assign one dynamically. You can also restrict the range of ports that RPC dynamically assigns to a small range, regardless of the service. For more information about this topic, see the "References" section of this article.

This article includes information about the system services roles and the server roles for the Microsoft products that are listed in the "Applies to" section at the end of this article. While this information may also apply to Microsoft Windows XP and to Microsoft Windows 2000 Professional, this article is intended to focus on server-class operating systems. Because of this, this article describes the ports that a service listens on instead of the ports that client programs use to connect to a remote system.

Check it here at source (Microsoft):
Code:

PHP Code:

   http://support.microsoft.com/default.aspx?scid=kb;en-us;832017