Announcement

Collapse
No announcement yet.

Not able to connect to vSphere (ESX4) from vSphere VI Client

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Not able to connect to vSphere (ESX4) from vSphere VI Client

    Hi all,

    I have VMware workstation and I am running windows server 2008 R2 as VM on it. I’ve installed Vsphere (ESX4) as VM also. I am not able to connect to ESX server via VI Client from windows machine. This is what I’ve checked so far –

    ESX server has been assigned a static IP address
    ESX (A) record is seen in DNS
    I am able to ping the ESX machine
    I am able to open the open initial web page for ESX server in a browser
    I am able to login to the ESX server from the ESX server console itself
    Both the machines are running on vmnet 0, I’ve tried them on host only // bridging but no go

    When I try connecting to the ESX via VI client, this is the error message that I get. Snap shot attached. Please guide on what I can try to get this fixed.



    Thank you in advance,
    Vaibhav


    Also I have edited the configuration vmx file and added the command monitor_control.restrict_backdoor = TRUE
    Attached Files
    Last edited by lvaibhavt; 3rd August 2011, 17:12.

  • #2
    Re: Not able to connect to vSphere (ESX4) from vSphere VI Client

    I don't have enough posts to post external links but try kb 1022611 on vmwares web site. It looks like it addresses your problem and you need to update your vSphere client.

    Comment


    • #3
      Re: Not able to connect to vSphere (ESX4) from vSphere VI Client

      Thank you for replying buddy .... lemme check this and I'll let you know

      Comment


      • #4
        Re: Not able to connect to vSphere (ESX4) from vSphere VI Client

        Are you using VCenter or just trying to connect to the ESX machine directly?

        There is a common error when connecting to VCenter.

        Remote into the vcenter system and open services. Then look for Vcenter Server and stop and start it (although it is probably already stopped).

        If this fixes your issue there is a kb on how to delay the start of the service.

        Hobie

        Comment

        Working...
        X