VMware Cloud Community
princox
Enthusiast
Enthusiast

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

Hi, Experts

Sooner or later, we are going to deploy vSphere and vCenter to LTE Datacenter server so that I'd like to self-experiment on its function(HA, vMotion) in VMware Workstation

because I , sadly , don't have enough equipment on the hands. Welcome any technical advice~!!! :smileygrin:

[Status]

Notebook has 8GB memory now.

I allocated 4GB on ESXi_1 and 2GB on ESXi_2 vm and installed vCneter Server Appliance on ESXi_1.

By installing vSphere(vCSA) client on host computer, conneting to vCSA encountered with some below issues.

[Obstacle]

[1]. Error message when I tried to connect vCenter

Could Not Connect:vSphere Client could not connect to "172.17.9.100".

An unknown connection error occurred.(The request failed because the remote server took too long to respond. (The operation has timed out)

vCommunity001.jpg

[2]. Ping to vCenter from Notebook(Host) sometimes showed fluctuation of response time. Is it the root cause?? I wish I don't think so.

vCommunity002.jpg

[Details]

vCenter Server Appliance Image

VMware-vCenter-Server-Appliance-5.1.0.10200-1235310_OVF10.ovf

VMware-vCenter-Server-Appliance-5.1.0.10200-1235310-data.vmdk

VMware-vCenter-Server-Appliance-5.1.0.10200-1235310-system.vmdk

ESXi Image

VMware-VMvisor-Installer-5.1.0.update01-1065491.x86_64.iso

VMware Workstation

9.0.0 build-812388

Physical Notebook

Windows 7 Home Premium, 64-bit 6.1.7601, Service Pack 1(8108 MB)

Assigned IP address (STATIC)

ESXi_1 : 172.17.9.10

ESXi_2 : 172.17.9.20

vCenter : 172.17.9.100

Notebook : 172.17.9.1

Warmest Regards,

Happy New Year!!!

Jeff

4 Replies
OscarDavey
Hot Shot
Hot Shot

To resolve this issue, Install/Reinstall Microsoft .NET Framework 3.5 Service Pack 1 or later.

Best regards

Yours, Oscar

princox
Enthusiast
Enthusiast

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!

0 Kudos
princox
Enthusiast
Enthusiast

Hi,

I re-installed VM workstation10 and MS .NET 4.5 package.

Unfortunately the symptom is exactly same as before.... --;;

Thanks

Jeff D. LEE

Welcome any technical advice on that

0 Kudos
julienvarela
Commander
Commander

Hi,

1- Did you have already configured your vCenter Appliance using the web management interface?

2 - If step 1 is ok, did you check your firewall? because if you are able to ping your vCenter, i think it is a firewall issue. You can test the vSphere Web client too.

Regards,

Julien.

Regards, J.Varela http://vthink.fr
0 Kudos