Quantcast
Channel: VMware Communities: Message List - vCenter™ Server
Viewing all articles
Browse latest Browse all 15787

Re: [Could Not Connect:vSphere Client could not connect to "172.17.9.100".]-(The operation has timed out);esxi & vsa on wm workstation though

$
0
0

Hi, OscarDavey

Thanks for commenting and really appreciated that.

I actually tried to install MS .NET Framework 3.5 SP 1 or later as below;

(1) Windows7 Home premium K(64bit) - Notebook

Windows6.1-KB958488-v6001-x64.msu (Cant be installed, Message popped up that it cant be installed in this system)

Windows6.1-KB979900-x64.msu (Installed)

 

64bit_regedit_NET_Ver.jpg

 

(2)Winodows7 Enterprise K (32bit) - VM

Windows6.1-KB958488-v6001-x86.msu (Installed)

Windows6.1-KB979900-x86.msu (Cant be installed, Message popped up that it cant be installed in this system)

 

32bit_regedit_NET_Ver.jpg

 

Two kinds of try-out led me to get same result.... same error message from vSphere Client.

///[Could Not Connect:vSphere Client could not connect to "172.17.9.100".]-(The operation has timed out)///

If any suggestion for resolving, please let me know anytime!

 

Many Thanks!!!!

Jeff!


Viewing all articles
Browse latest Browse all 15787

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>