After installation, you can change the port. You do not have to use the same port number throughout the site hierarchy. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No. Any additional feedback? Important These are default port numbers that can be changed in Configuration Manager.
Important If there is a firewall between the site system servers and the client computer, confirm whether the firewall permits traffic for the ports that are required for the client installation method that you choose.
Submit and view feedback for This product This page. The Ports and protocols section includes a table that summarizes the information from the System services ports section. The table is sorted by the 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 the article uses these terms:. This article doesn't specify which services rely on other services for network communication. A full discussion of the architecture of the Windows operating systems is beyond the scope of this article. Although many services may rely on a particular TCP or UDP port, only one service or process at a time can listen on that port.
These ports are also informally known as random RPC ports. In these cases, RPC clients rely on the RPC endpoint mapper to tell them which dynamic port or ports were assigned to the server. 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. 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.
Although this information may also apply to Windows XP and to Microsoft Windows Professional, this article is focused on server-class operating systems. Therefore, this article describes the ports that a service listens on instead of the ports that client programs use to connect to a remote system.
This section provides a description of each system service, includes the logical name that corresponds to the system service, and displays the ports and the protocols that each service requires. Active Directory runs under the Lsass. Domain controllers, client computers, and application servers require network connectivity to Active Directory over specific hard-coded ports.
Additionally, unless a tunneling protocol is used to encapsulate traffic to Active Directory, a range of ephemeral TCP ports between to and to are required. If your computer network environment uses only Windows Server R2, Windows Server , Windows 7, or Windows Vista, you must enable connectivity over the high port range of through If your computer network environment uses Windows Server R2, Windows Server , Windows 7, or Windows Vista together with versions of Windows earlier than Windows Server and Windows Vista, you must enable connectivity over both port ranges: High port range of through Low port range of through If your computer network environment uses only versions of Windows earlier than Windows Server and Windows Vista, you must enable connectivity over the low port range of through In this encapsulated scenario, you must allow the following items through the router instead of opening all the ports and protocols listed in this topic:.
Finally, you can hard-code the port that is used for Active Directory replication by following the steps in Restricting Active Directory RPC traffic to a specific port. The following settings are LDAP session options:. FTP is the only network protocol that has a plug-in that is included with Windows Server.
The ALG FTP plug-in supports these sessions by redirecting all traffic that meets the following criteria to a private listening port in the range of to on the loopback adapter:. NET out-of-process session states. NET State Service stores session data out-of-process.
The service uses sockets to communicate with ASP. NET that is running on a web server. Certificate Services is part of the core operating system. By using Certificate Services, a business can act as its own certification authority CA. It lets the business issue and manage digital certificates for programs and protocols such as:. For more information, see 3.
The Cluster service controls server cluster operations and manages the cluster database. A cluster is a collection of independent computers that act as a single computer. Managers, programmers, and users see the cluster as a single system.
The software distributes data among the nodes of the cluster. If a node fails, other nodes provide the services and data that were formerly provided by the missing node. When a node is added or repaired, the cluster software migrates some data to that node. By default, DTLS is enabled. The Computer Browser system service maintains an up-to-date list of computers on your network and supplies the list to programs that request it.
The Computer Browser service is used by Windows-based computers to view network domains and resources. Computers that are designated as browsers maintain browse lists that contain all shared resources that are used on the network. Earlier versions of Windows-based programs, such as My Network Places, the net view command, and Windows Explorer, all require browsing capability.
For example, when you open My Network Places on a computer that is running Microsoft Windows 95, a list of domains and computers appears. To display this list, the computer obtains a copy of the browse list from a computer that is designated as a browser. If you are running only Windows Vista and later versions of Windows, the browser service is no longer required.
You can use this service to adjust the advanced network settings of DHCP clients. The Distributed File System Replication DFSR service is a state-based, multi-master file replication engine that automatically copies updates to files and folders between computers that are participating in a common replication group. It is not used on a Windows Server domain controller. The Distributed Link Tracking Server system service stores information so that files that are moved between volumes can be tracked to each volume in the domain.
The Distributed Link Tracking Server service runs on each domain controller in a domain. This service enables the Distributed Link Tracking Client service to track linked documents that are moved to a location in another NTFS file system volume in the same domain.
The Distributed Transaction Coordinator DTC system service coordinates transactions that are distributed across multiple computer systems and resource managers, such as databases, message queues, file systems, or other transaction-protected resource managers.
DNS servers are required to locate devices and services that are identified by using DNS names and to locate domain controllers in Active Directory. The Event Log system service logs event messages that are generated by programs and by the Windows operating system. Event log reports contain information that you can use to diagnose problems. You view reports in Event Viewer. The Event Log service writes events that are sent to log files by programs, by services, and by the operating system.
New remote shell connections will be rejected if they exceed the specified limit. The default is 5. Specifies the maximum time, in milliseconds, that the remote command or script is allowed to execute. Changing the value for MaxShellRunTime will have no effect on the remote shells.
Specifies the maximum number of processes that any shell operation is allowed to start. A value of 0 allows for an unlimited number of processes. Specifies the maximum amount of memory allocated per shell, including the shell's child processes.
The default is MB. Specifies the maximum number of concurrent shells that any user can remotely open on the same computer. If this policy setting is enabled, then the user won't be able to open new remote shells if the count exceeds the specified limit. If this policy setting is disabled or is not configured, the limit will be set to 5 remote shells per user by default.
Starting in WinRM 2. WinRM listeners can be configured on any arbitrary port. If a computer is upgraded to WinRM 2. WinRM isn't dependent on any other service except WinHttp. If two listener services with different IP addresses are configured with the same port number and computer name, then WinRM listens or receives messages on only one address. If the driver fails to start, then you might need to disable it.
Plug and Play support might not be present in all BMCs. To do this, type the following command at a command prompt: Rundll32 ipmisetp. If you uninstall the Hardware Management component, then the device is removed.
For more information, see Hardware Management Introduction. For a normal or power non-administrator user to be able to use the WMI plug-in , you need to enable access for that user after the listener has been configured. First, you must set up the user for remote access to WMI through one of these steps. To do this, run wmimgmt. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Please rate your experience Yes No.
Any additional feedback? You can also obtain hardware and system data from WS-Management protocol implementations running on operating systems other than Windows in your enterprise. The intended audience for Windows Remote Management is IT Pros, who write scripts to automate the management of servers, and ISV Independent Software Vendor developers, who want to obtain data for management applications.
WinRM is part of the operating system. However, to obtain data from remote computers, you must configure a WinRM listener.
0コメント