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

My Subscriptions

Loading

Knowledge Base

Error: "Unable to Connect to the MKS : Could not connect to pipe" while Connecting to Remote Console (2150981)

Last Updated: 4/7/2021Categories: TroubleshootingTotal Views: 42840Language:
Chinese (Simplified)Portuguese (Brazil)JapaneseSpanishEnglish

28 like this article

Subscribe to get an email
newsletter with new updates

28 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

When attempting to connect to the remote console you see this error:

Unable to connect to the MKS: Could not connect to pipe \\. \pipe\vmware-authdpipe: The system cannot find the file specified.

The VMRC logs located at %TEMP%\vmware-USERNAME\vmware-vmrc-####.log contain messages similar to:

YYYY-MM-DDTHH:MM:SS-00:00| vmrc| I125: CnxOpenTCPSocket: Cannot connect to server SERVERNAME:902: No connection could be made because the target machine actively refused it
YYYY-MM-DDTHH:MM:SS-00:00| vmrc| I125: CnxAuthdConnect: Returning false because CnxAuthdConnectTCP failed
YYYY-MM-DDTHH:MM:SS-00:00| vmrc| I125: CnxConnectAuthd: Returning false because CnxAuthdConnect failed
YYYY-MM-DDTHH:MM:SS-00:00| vmrc| I125: Cnx_Connect: Returning false because CnxConnectAuthd failed
YYYY-MM-DDTHH:MM:SS-00:00| vmrc| I125: Cnx_Connect: Error message: Failed to connect to server SERVERNAME:902
YYYY-MM-DDTHH:MM:SS-00:00| vmrc| I125: VMClient_ConnectMksClientEx - Remote socket connection failed.
YYYY-MM-DDTHH:MM:SS-00:00| vmrc| I125: VMClient_ConnectMksClientEx - trying local socket connection to /vmfs/volumes/DATASTORE/VM/VM.vmx
YYYY-MM-DDTHH:MM:SS-00:00| vmrc| I125: VMClientConnectSocketEx
YYYY-MM-DDTHH:MM:SS-00:00| vmrc| I125: CnxAuthdConnectPipe: Returning false because we ran out of retries when CreateFileW
YYYY-MM-DDTHH:MM:SS-00:00| vmrc| I125: CnxAuthdConnect: Returning false because CnxAuthdConnectPipe failed
YYYY-MM-DDTHH:MM:SS-00:00| vmrc| I125: Cnx_Connect: Error message: Could not connect to pipe \\.\pipe\vmware-authdpipe within retry period
YYYY-MM-DDTHH:MM:SS-00:00| vmrc| I125: VMClient_ConnectMksClientEx - Local socket connection failed.
...
YYYY-MM-DDTHH:MM:SS-00:00| vmrc| I125: DlgUI: Unable to connect to the MKS: Could not connect to pipe \\.\pipe\vmware-authdpipe within retry period.
YYYY-MM-DDTHH:MM:SS-00:00| vmrc| I125: VMMgr: Finished opening VM at /vm/#_56EBAA8_vm-###/ from SERVERNAME:vm-###

Cause

The error "Unable to Connect to the MKS" occurs when:

Attempting to connect to the remote console from vCenter Server to a virtual machine.

When connecting to the remote console from different subnets through a firewall.

When name resolution for the ESXi or vCenter FQDN does not return the correct or valid IP address.

Resolution

To resolve the issue allow the VM Remote Console port-902 to vCenter and the ESXi hosts.

Process to allow the VM Remote Console port-902 to vCenter and the ESXi hosts:

If the user is in a different layer 3 subnet, check firewall settings:

In other words, validate the Port connectivity from the desktop machine that you have logged in to the vCenter Server(from where the Host Client or Web Client is launched), it could be that the Firewall in the environment is blocked for port 902
The connection is as follows: User --> TCP/UDP 902 --> vCenter

Remote Console access from the ESXi Host directly as below

The connection is as follows: User redirect --> TCP/UDP 902 --> ESXi Host

Note: If the host is added by DNS, it must have DNS resolution for both vCenter Server and the ESXi hosts. Use the NSLOOKUP command from both the client and the vCenter Server to confirm a valid forward and reverse DNS entry exists.

Related Information

For translated version of this article, see:

リモート コンソール接続が「MKS に接続できません (Unable to connect to the MKS)」エラーで失敗する

中文简体：远程控制台连接失败：无法连接到 MKS

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)Portuguese (Brazil)JapaneseSpanishEnglish

Attachments

Additional Resources

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

Result 1 of 1

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere

Related Versions:

VMware vSphere 7.0.x

VMware vSphere 6.x

Take Our Survey

Cookie Preference Center

General Information on cookies

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‎

Please confirm your settings by refreshing the page.

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‎

Please confirm your settings by refreshing the page.

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

Support Assistant