Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

VMware Remote Console 11.x requires port 443 on ESXi hosts (76672)

Last Updated: 6/22/2021Categories: TroubleshootingTotal Views: 42093Language:
Chinese (Simplified)Portuguese (Brazil)JapaneseSpanishEnglish

68 like this article

Subscribe to get an email
newsletter with new updates

68 people found this helpful Please provide article feedback:

Learn how VMware Skyline Advisor and Skyline Health Diagnostics work together to provide proactive intelligence and self-service log analysis.

Use Skyline Advisor to avoid issues before they occur across VCF, vSphere, vSAN, NSX, vROps & Horizon. Skyline Findings are based on top KBs, VMSAs/CVEs and design best practices.

Use Skyline Health Diagnostics to root cause vSphere & vSAN logs when an issue occurs. Skyline Health Diagnostic Findings are based on top KBs and VMSA/CVEs. You can use the Skyline Health Diagnostics tool in online or offline mode.

If you require additional help from technical support, please use Skyline Advisor to initiate a Log Assist to reduce time to upload logs. TSEs can also initiate logs to reduce effort.

Symptoms

After upgrading to VMware Remote Console 11.x, you are no longer able to access or pass through a remote device to your virtual machines through VMware Remote Console.

Cause

Default transfer protocol/WebSocket per VMRC Versions:

VMRC switched its default transfer protocol to WebSocket in recent releases, which results in the port of daemon service in the host changed as well:

VMRC Version

<11.0

11.0

>11.0

Default protocol & port for Mouse/Keyboard/Screen connection

TCP 902

WebSocket 443

WebSocket 443

Default protocol & port for "remote device" connection

TCP 902

TCP 902

WebSocket 443

Mouse, Keyboard, Screen (MKS):

A process that is responsible for rendering the guest video and handling guest operating system user input.

And considering the support of WebSocket in vSphere releases are different:

vSphere Version

<7.0

>=7.0

Support WebSocket based Mouse/Keyboard/Screen connection

Yes

Yes

Support WebSocket based"remote device" connection

No

Yes

Combined Matrix:

The combined matrix is:

<VMRC 11.0

VMRC 11.0

>VMRC 11.0

MKS

Remote Device

MKS

Remote Device

MKS

Remote Device

>= vSphere 7.0

902

902

443

902

443

443

< vSphere 7.0

902

902

443

902

443

902

For those combinations fall into the 443 (port) category, by default, VMware Remote Console requires direct access to port 443 on ESXi hosts. If VMware Remote Console cannot reach port 443 on a host, for example due to firewall rules, VMware Remote Console will be unable to access or pass through a remote device to virtual machines on that host.

Resolution

The issue can be resolved by using either one of the below methods:

Modify your firewall configuration to ensure that VMware Remote Console can reach port 443 on ESXi hosts before attempting to access virtual machines on those hosts.

Configure VMware Remote Console 11.x to use the legacy connection mode. To do so, open the VMware preferences file on the host machine and add the following parameters:

pref.preferWebMKS = "FALSE"

pref.preferWebRemoteDevice = "FALSE"

Preferences file location:

The preferences file can be found in the following location:

Windows: %APPDATA%\VMware\preferences.ini

macOS (standard install): ~/Library/Preferences/VMware Remote Console/preferences

macOS (App Store install):~/Library/Containers/com.vmware.vmrc/Data/Library/Preferences/VMware Remote Console/preferences

Linux: ~/.vmware/preferences

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (Brazil)JapaneseSpanishEnglish

Attachments

Additional Resources

KB
•
ライセンスのアップグレード後に、vRA Code Stream サービスがユーザー インターフェイスに表示されない (76642)

KB
•
削除されたクラスタ ノードの構成の残りをクリーンアップする (76662)

KB
•
「vracli license usage」コマンドが機能しない - Flex ライセンスの仮想マシンの使用量が報告されない (76673)

KB
•
许可证升级后，vRA Code Stream 服务在 UI 中不可见 (76642)

Results 1-4 of 4

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vSphere ESXi

VMware vSphere

VMware vSphere

Related Versions:

VMware vSphere ESXi 7.0.0

VMware vSphere ESXi 7.0.0

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.7

VMware vSphere ESXi 6.5

VMware vSphere ESXi 6.5

VMware vSphere 7.0.x

VMware vSphere 7.0.x

Take Our Survey

Support Assistant