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

Error: "IP Address of the host changed", while adding ESXi to vCenter server (1035944)

Last Updated: 8/21/2019Categories: TroubleshootingTotal Views: 11491Language:
English

4 like this article

Subscribe to get an email
newsletter with new updates

4 people found this helpful Please provide article feedback:

Symptoms

Copying files using the datastore browser with vSphere Client connected to vCenter Server fails.

You see the error:

Datastore Browser: Cannot connect to host

This issue does not occur with vSphere client direct connection to the ESXi host.

The vSphere Client logs contain the errors:

viclient:SoapTran:W:17] <YYYY-MM-DD>T<time>Z Invoke 203 Finish WaitForUpdates on PropertyCollector:propertyCollector [utility] - Serial:0.000, Server:000.005
[viclient:SoapTran:M: 6] <YYYY-MM-DD>T<time>Z Invoke 204 Start Destroy on PropertyFilter:session[1FAA4D2F-E2DA-41C3-9F4F-7A077A2C864A]A5E400D3-950C-4F43-8FA6-F787B6CBBAFD [utility]. [operationID:CBBE6ABC-000000CC][Caller: VirtualInfrastructure.Updates.PollerDispatcherImpl.RemoveAssociatedFilters]
viclient:SrvMsg :M: 6] <YYYY-MM-DD>T<time>Z RMI Request Vmomi.Core.PropertyCollector+Filter.Destroy - 204
[ :ShowExcp:M: 6] <YYYY-MM-DD>T<time>Z Datastore Browser: Cannot connect to host.
Vmomi.Fault.HostConnectFault: Cannot connect to host

Adding the host to vCenter Server fails. 

You see the error:

Ip address of the host changed from <IP1> to <IP2>

After adding the ESX host to vCenter Server fails, the vCenter Server vpxd logs contain entries similar to:

<YYYY-MM-DD>T<time>Z 07456 warning 'App'] [VpxdInvtHost] IP address change detected from <IP1> to <IP2>
<YYYY-MM-DD>T<time>Z 06780 info 'App' opID=HB-host-47@270] [VpxLRO] -- BEGIN task-internal-278 -- host-47 -- VpxdInvtHostSyncHostLRO.Synchronize --
<YYYY-MM-DD>T<time>Z  06780 info 'App' opID=HB-host-47@270] [VpxdInvtHostSyncHostLRO] Ip address of the host changed from <IP1> to <IP2>
<YYYY-MM-DD>T<time>Z  06780 info 'vmomi.soapStub[33]' opID=HB-host-47@270] Resetting stub adapter for server TCP:<IP1>:443 : Closed
<YYYY-MM-DD>T<time>Z 06780 info 'App' opID=HB-host-47@270] [VpxdHostSync] Synchronizing host: <IP2> (<IP2>)

Note: IP2 is the gateway of the DMZ router.

Removing and re-adding the vpxuser account and vpxa agent does not resolve this issue.

Re-installing vCenter Server database and adding host entries for manual DNS resolution does not resolve this issue.

Cause

This issue occurs if the IP address of the ESXi host is changed via Network Address Translation (NAT) by the firewall/router as its traffic passes from the DMZ network to the internal network. This makes the vCenter Server initiate future sessions to the internal router IP when connecting to the ESXi host, which are then not properly routed.

Resolution

Using NAT between the vCenter Server system and ESXi hosts is an unsupported configuration. For more information, see Using NAT between the vCenter Server system and ESXi/ESX hosts (1010652).

To resolve this issue, do not NAT the ESX host IP from the DMZ to the internal network. Alternatively, configure direct routing on your router.

For a list of ports that are required for vCenter Server and ESX host communications, see TCP and UDP Ports required to access vCenter Server, ESXi/ESX hosts, and other network components (1012382).

Related Information

Using NAT between the vCenter Server system and ESXi/ESX hosts

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 を 6.5 にアップグレードした後に PSC Client に接続すると、"An error occurred while sending an authentication request to the PSC Single Sign-On server - null" というメッセージが表示される (52541)

KB
•
Windows 2008 R2 上の vCenter Server にて、FLEX クライアント名が cis.vsphere-client.serviceName と表示される (52644)

KB
•
升级到 vCenter Server 6.0 时报错：ODBC error [Oracle] - ORA-22275: invalid LOB locator specified (2145276)

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 vCenter Server

Related Versions:

Take Our Survey

Support Assistant