Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
Search the VMware Knowledge Base (KB)   View by Article ID

Required ports for vCenter Server 5.1.x (2031843)


This article provides information on the required ports for vCenter Server 5.1.x.

Note: For information on the required ports for the vCenter Server Appliance 5.x, see Required ports for vCenter Server Appliance 5.x (2012773).


The VMware vCenter Server system must be able to send data to every managed host and receive data from every vSphere Client. To enable migration and provisioning activities between managed hosts, the source and destination hosts must be able to receive data from each other.

VMware uses designated ports for communication. Additionally, the managed hosts monitor designated ports for data from the vCenter Server system. If a firewall exists between any of these elements and the Windows firewall service is in use, the installer opens the ports during the installation process. For custom firewalls, you must manually open the required ports. If you have a firewall between two managed hosts and you want to perform source or target activities such as migration or cloning, you must configure a means for the managed hosts to receive data.

Note: In Microsoft Windows Server 2008, a firewall is enabled by default.

This table outlines the ports required for communication between components:

80TCPvCenter Server requires port 80 for direct HTTP connections. Port 80 redirects requests to HTTPS port 443. This redirection is useful if you accidentally use http://server/ instead of https://server/.

Note: Microsoft Internet Information Services (IIS) also use port 80. For more information, see Conflict Between vCenter Server and IIS for Port 80 in the vSphere Installation and Setup guide.
389TCP/UDPThis port must be open on the local and all remote instances of vCenter Server. This is the LDAP port number for the Directory Services for the vCenter Server group. The vCenter Server system needs to bind to port 389, even if you are not joining this vCenter Server instance to a Linked Mode group. If another service is running on this port, it might be preferable to remove it or change its port to a different port. You can run the LDAP service on any port from 1025 through 65535.

If this instance is serving as the Microsoft Windows Active Directory, change the port number from 389 to an available port from 1025 through 65535.
443TCPThe default port that the vCenter Server system uses to listen for connections from the vSphere Client. To enable the vCenter Server system to receive data from the vSphere Client, open port 443 in the firewall.

The vCenter Server system also uses port 443 to monitor data transfer from SDK clients.

If you use another port number for HTTPS, you must use ip-address:port when you log in to the vCenter Server system.
636TCPFor vCenter Server Linked Mode, this is the SSL port of the local instance. If another service is running on this port, it might be preferable to remove it or change its port to a different port. You can run the SSL service on any port from 1025 through 65535.
902TCP/UDPThe default port that the vCenter Server system uses to send data to managed hosts. Managed hosts also send a regular heartbeat over UDP port 902 to the vCenter Server system. The port is also used for transmitting virtual machine consoles for ESXi 4.x and 5.x hosts. This port must not be blocked by firewalls between the server and the hosts or between hosts.
903TCPPort 903 must be open between the vSphere Client and ESX / ESXi hosts. The vSphere Client uses this port to display virtual machine consoles on ESX / ESXi hosts.
8080TCPWeb Services HTTP. Used for the VMware VirtualCenter Management Web Services.
Internal Service Diagnostics/SDK
8443TCPWeb Services HTTPS. Used for the VMware VirtualCenter Management Web Services.
60099TCPWeb Service change service notification port
6501TCPAuto Deploy Service
6502TCPAuto Deploy management
7444TCPvCenter Single Sign-On HTTPS
7005TCPvCenter Single Sign-On Base shutdown port
7080TCPvCenter Single Sign-On HTTP port
7009TCPvCenter Single Sign-On AJP port. For more information, see Configuring VMware Tomcat Server Settings in vCenter Server 5.1.
9443TCPvSphere Web Client HTTPS
9090TCPvSphere Web Client HTTP
9875 - 9877TCPvSphere Web Client Java Management Extension (JMX). Dynamically acquired upon the vSphere Web Client service starting.
10080TCPvCenter Inventory Service HTTP
10443TCPvCenter Inventory Service HTTPS
10109TCPvCenter Inventory Service Management
10111TCPvCenter Inventory Service Linked Mode Communication

Note: To have the vCenter Server system use a different port to receive vSphere Client data, see the vCenter Server and Host Management documentation. For a discussion of firewall configuration, see the vSphere Security Guide.

Additional Information

For information on port requirements for vCenter Server 5.0, see Required ports for vCenter Server 5.0 (2005105).

See Also

Update History

11/09/2012 - Minor formatting changes. 10/17/2012 - Added additional SSO ports 02/13/2013 - Added protocol column to table 03/26/2013 - Added UDP to Protocol column for port 902

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.


  • 23 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
  • 23 Ratings