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

Unable to join ESXi 6.0 host to domain through authentication proxy, fails with error : "The specified vSphere Authentication Proxy Server is not reachable, or has denied access to the service" (67596)

Last Updated: 4/3/2019Categories: TroubleshootingTotal Views: 7406Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Symptoms

While joining ESXi 6.0 host to domain through authentication proxy, fails with below error :

"The specified vSphere Authentication Proxy Server is not reachable, or has denied access to the service."

You will find similar log snippet in VPXD.log

-->    msg = "The specified vSphere Authentication Proxy server is not reachable, or has denied access to the service."
error vpxd[7F95FBC62800] [Originator@6876 sub=OsLayer_linux] [VpxOsLayer] Failed to write to config: FileIO error: Permission denied for file  : /etc/vmware-vpx/vpxd.cfg.tmp
-->    msg = "The specified vSphere Authentication Proxy server is not reachable, or has denied access to the service."

info vpxd[7F95ED8BC700] [Originator@6876 sub=Default opID=AuthJoinDomainFormMediator-apply-253820-ngc:70023638-e] [VpxLRO] -- ERROR task-43878 -- activeDirectoryAuthentication-29 -- vim.host.ActiveDirectoryA
Authentication.joinDomainWithCAM: vim.fault.CAMServerRefusedConnection:
--> Result:
--> (vim.fault.CAMServerRefusedConnection) {
-->    faultCause = (vmodl.MethodFault) null,
-->    faultMessage = ,
-->    errorCode = 1225,
-->    camServer = "x.x.x.x"
-->    msg = "The specified vSphere Authentication Proxy server is not reachable, or has denied access to the service."
--> }
--> Args:
-->
--> Arg domainName:
--> "example.org"
--> Arg camServer:
--> "x.x.x.x"
YYYY-MM-DDTHH:MM:SS.275-04:00 warning vpxd[7F95ECE9A700] [Originator@6876 sub=VpxProfiler opID=AuthJoinDomainFormMediator-apply-253820-ngc:70023638-e-TaskLoop-47e13d0a] TaskLoop [TotalTime] took 75062 ms

From messages.log you may see as below

YYYY-MM-DDTHH:MM:SS.414646-05:00 shemp vmcamd: t@140133709772544: [../../../server/vmcam/httpserv.c,231]
YYYY-MM-DDTHH:MM:SS.414903-05:00 shemp vmcamd: t@140133709772544: VmCam HTTPS request Handler failed with 5

The error number (5) corresponds to ERROR_ACCESS_DENIED.

Hostd.log

=======
error hostd[2A381B70] [Originator@6876 sub=ActiveDirectoryAuthentication opID=AuthJoinDomainFormMediator-apply-220088-ngc:70021834-63-4c-9e52 user=vpxuser:example.ORG\abc] vmwauth ConnectionRefusedException: Exception 0x000004c9: The remote computer refused the network connection.
info hostd[2A381B70] [Originator@6876 sub=Vimsvc.ha-eventmgr opID=AuthJoinDomainFormMediator-apply-220088-ngc:70021834-63-4c-9e52 user=vpxuser:example.ORG\abc] Event 1546 : Join domain failed.
info hostd[2A381B70] [Originator@6876 sub=Vimsvc.TaskManager opID=AuthJoinDomainFormMediator-apply-220088-ngc:70021834-63-4c-9e52 user=vpxuser:example.ORG\abc] Task Completed : haTask-ha-host-vim.host.ActiveDirectoryAuthentication.joinDomainWithCAM-209160 Status error

Purpose

To join the ESXi 6.0 host to vCenter via authentication proxy.

Cause

This issue occurs if the user_id that is used to join the CAM Server to Authentication Proxy doesn't have all the required permissions.

Impact / Risks

None

Resolution

Check  output of command. You will see as below

/usr/lib/vmware-vmcam/bin/camconfig status

Default Domain Name: <domain name>
Default Domain User: vsphere_auth_proxy
vCenter Server Address: localhost
vCenter Server User: [email-masked]
vCenter Server Port: 80

From vmcam.reg file

/opt/likewise/bin/lwregshell export '[HKEY_THIS_MACHINE\Software\vmcam\Parameters\Domains]' ./vmcam.reg

[HKEY_THIS_MACHINE\Software\vmcam\Parameters\Domains\<domain name>-YYYY-MM-DDTHH:MM:SS281Z]
"DomainName" = {
"value"="<domain name>"
}
"User" = {
"value"="vsphere_auth_proxy"
}

NOTE: vSphere Authentication Proxy interoperability between 6.0x hosts and 6.5x VC is not supported . You would need to upgrade the ESXi  hosts from 6.0 to 6.5 or 6.7.

Workaround

Add the host to domain manually, without using authentication proxy.

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 Appliance 6.5 へのパッチ適用中に「post-install.sh を正常に実行できません」(Unable to successfully execute post-install.sh) というエラーが記録される (67978)

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 vSphere ESXi

VMware vCenter Server Appliance

Related Versions:

VMware vSphere ESXi 6.0

VMware vCenter Server Appliance 6.7.x

VMware vCenter Server Appliance 6.5.x

Take Our Survey

Support Assistant