Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Configuring Windows Server 2008 to allow a smaller range of ports for Linked Mode communications (1036180)

Last Updated: 8/5/2015Categories: How toTotal Views: 21215Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Establishing a Linked Mode configuration between vCenter Server instances is not feasible due to the large number of ports that need to be opened between them.

You have modified the registry on both vCenter Server instances as per the Microsoft Knowledge Base article 154596 but still see port communication outside of the range that is selected.

Note: The preceding link was correct as of May 13, 2015. If you find the link is broken, please provide feedback and a VMware employee will update the link.

Purpose

This table contains the ports that need to opened through the firewall for Linked Mode.

Note: All ports need to be opened for bi-directional communication.

Port

Protocol

Description

135

TCP/UDP

Used by ADAM for RPC communications between vCenter Servers in Linked Mode.

389

TCP/UDP

This port must be open in 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.

636

TCP

This is the SSL port of the local instance for vCenter Server Linked Mode. If another service is running on this port, it might be preferable to remove it or change its port. You can run the SSL service on any port from 1025 through 65535.

1024

TCP

RPC communication on dynamic TCP ports is required between all vCenters that need to replicate (via ADAM).

7500

UDP

vCenter Inventory Service Groups diagnostics port for Inventory Service instances.

8443

TCP

VMware Web Management Services Linked Mode Communication port.

10111

TCP

vCenter Inventory Service Linked Mode Communication.

10443

TCP

vCenter Inventory Service Linked Mode Communication between Inventory Service instances.

This can be changed during the vCenter Server installation and should be adjusted in the firewall settings as needed.

Notes:

For more information on the ports used for ADAM, see Network Ports Used by ADAM.

For more information, see TCP and UDP Ports required to access vCenter Server, ESX hosts, and other network components (1012382).

These ports are used for establishing communication between the vCenter Server instances. Ephemeral (dynamic) port values between 49152 and 65535 are also required to be open for subsequent communication to function properly. This article details changes that can be made in the Windows Server 2008 operating system to reduce the range of ephemeral ports used.

Resolution

In Windows Server 2008, the netsh command can be used to limit the number of ephemeral (dynamic) ports used for outgoing RPC communication. The number of ports used can be as low as 256 and as high as 64510 (1025 through 65535).

The syntax of the netsh command is:

Note: Run the netsh commands as Administrator, from an elevated command prompt.

netsh int ipv4|ipv6 set dynamic tcp|udp start=number num=range

Where the starting port to be used is number and the total number of ports is range. For our purposes, ipv4 would be used for the protocol and both tcp and udp would need to be used via separate netsh commands.

These examples limit the port range to values between 60100 and 60356:

netsh int ipv4 set dynamic tcp start=60100 num=256
netsh int ipv4 set dynamic udp start=60100 num=256

Each Windows Server 2008 system where this change is made needs to be rebooted for the change to take effect.

For more information see the Microsoft Knowledge Base article 929851.

Note: The preceding link was correct as of November 4, 2011. If you find the link is broken, please provide feedback and a VMware employee will update the link.

Related Information

If there is a physical firewall between the vCenter Servers in the Linked Mode configuration, configure the firewall to allow traffic on ports 389, 636, 135 and the dynamic port range configured to pass between the vCenter Server instances. TCP and UDP Ports required to access VMware vCenter Server, VMware ESXi and ESX hosts, and other network components

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
vCenter Server をリンク モードに参加させるためのベスト プラクティス (2005481)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCenter Server

Related Versions:

VMware vCenter Server 5.5.x

VMware vCenter Server 5.1.x

VMware vCenter Server 5.0.x

VMware vCenter Server 4.1.x

VMware vCenter Server 4.0.x

Take Our Survey

Support Assistant