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

Connecting to vCenter Server using the vSphere Client fails (1031039)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 42203Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Cannot connect to vCenter Server using the vSphere Client

The VMware VirtualCenter Server service is running

You may have separate VMware or 3rd party solutions connected to the vCenter Server

Running the netstat -a command on vCenter Server shows a large number of CLOSE_WAIT entries

In the vpxd.log file, you see entries similar to:

Note: For the default location of vCenter Server logs, see Location of vCenter Server log files (1021804).

vpxd-19.log:2010-11-10T17:20:37.359-08:00 [10180 error 'HttpConnectionPool'] [ConnectComplete] Connect error Only one usage of each socket address (protocol/network address/port) is normally permitted.
vpxd-19.log:2010-11-10T17:20:37.359-08:00 [10584 error 'Default' opID=4c7bcb32] [VpxdClientAdapter] Got vmacore exception: Only one usage of each socket address (protocol/network address/port) is normally permitted.

Cause

This issue occurs due to the large number of CLOSE_WAIT entries in vCenter Server.

Resolution

To resolve this issue, change the registry setting to allow more local ports.

To change the registry setting to allow more local ports:

Stop the VMware VirtualCenter Server service.

Open the vpxd.cfg file using a text editor.

Add the following <soap> elements within the <vmacore> </vmacore> tags:

<soap>

<sessionTimeout>30</sessionTimeout>

<maxSessionCount>1000</maxSessionCount>
</soap>

Change the registry setting to allow more local ports.

To modify the registry setting:

Note: This procedure modifies the Windows registry. Before making any registry modifications, ensure that you have a current and valid backup of the registry and the virtual machine. For more information on backing up and restoring the registry, see the Microsoft Knowledge Base article 136393.

Click Start > Run, type regedit, and click OK. The Registry Editor window opens.

Locate this key in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters

Right-click Parameters and click New > DWORD Value.

Type MaxUserPort for Name.

Right click MaxUserPort and click Modify.

Type 65534 for Value, select Decimal, and then click OK.

Note: The default value for the MaxUserPort is 5000 (Decimal).

Close the Registry Editor window.

Start the VMware VirtualCenter Server service.

Note: A restart of the vCenter Server may be required for the registry changes to be applied.

Related Information

Location of vCenter Server log files
vSphere Client を使用して vCenter Server に接続しようとすると失敗します
使用 vSphere Client 连接到 vCenter Server 失败

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

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

KB
•
增加分配给虚拟机的 CPU 量 (1004060)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-3 of 3

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.0.x

VMware vCenter Server 4.0.x

Take Our Survey

Support Assistant