Unable to log into VSphere Client

[LuckyFabian]

Hi Ladies & Gents,

  After resolving my storage issue where I was unable to boot my vm, I am not faced with a different problem on my HP Gen 8 Microserver.

I turn on the Microserver, select it to boot from the internal USB stick with ESXi 6.0 on it and watch it boot into the black and yellow VMWare screen. It gets to the point where it terminates as I do not have an ILO4 license so that disappears and I enter in the user/pass that I've always successfully logged in with before, but now it won't let me at all... Screen shot as follows :

I cannot fathom why this is happening, can somebody shed any light on this issue please?

Thanks in advance,

LuckyFabian

[ITaaP]

Can you ping the IP address? You also don't need "https://". Just the IP address will work. If you can ping 192.168.1.20, what happens if you open a browser and go to http://192.168.1.20?

[LuckyFabian]

I pinged 192.168.1.20 and it did not return :smileysad: (wish I'd done that sooner!)

I cannot figure out WHY...

Go to 192.168.1.20 in my browser and it it does not load or respond at all...

Looks like 192.168.1.20 has been sucked up by a black hole...

I changed the ILO to 192.168.1.20 to .25 and tried that, still no ping response or browser.

I just changed it back to .20... But I know now I should be able to change the ILO IP in the web console under ILO Dedicated Network Port (and have been resetting changes when I submit them).

Regardless I get a response from pinging the Gateway address 192.168.0.1

Any more help would be most appreciated...

Current settings are :

DHCPv4 Status:

Disabled

Address	192.168.1.20
Subnet Mask	255.255.255.0
Default Gateway	192.168.0.1

Use iLO Dedicated Network Port
NIC	LOM    FlexibleLOM
Port
Link State	Automatic 1000BaseT, Full-duplex 1000BaseT, Half-duplex 100BaseT, Full-duplex 100BaseT, Half-duplex 10BaseT, Full-duplex 10BaseT, Half-duplex
Enable VLAN
VLAN Tag

Reset 

Thanks in advance,

Lucky

[ITaaP]

That networking doesn't make sense. The subnet mask 255.255.255.0 is a /24. Therefore your settings should be.

Address: 192.168.1.20

Subnet Mask: 255.255.255.0

Default Gateway: 192.168.1.1

If you are really running a /23 network, then the subnet mask would be 255.255.254.0.

[LuckyFabian]

I just realised as the

Default Gateway	192.168.0.1

I then changed the ILO IP to 192.168.0.20

THIS returns a PING successfully!

Although...

Trying to connect with the VSphere Client returns the error :

VSphere Client could not connect to 192.168.0.20

An unknown connection error occurred.(The Server could not interpret

the client's request. (The remote server returned an error (404) Not Found)).

I don't understand, my original IP had not changed or been altered at ALL... :/

[LuckyFabian]

Hello mate,

Are you saying I should configure these settings based upon the subnet mask?

Address: 192.168.1.20

Subnet Mask: 255.255.255.0

Default Gateway: 192.168.1.1

I have not altered any other of the addresses from before so I don't know why it stopped letting me in :smileysad:

So you want me to alter the IP and Default Gateway?

[LuckyFabian]

...altering now!

[LuckyFabian]

Nope... :smileysad:

Did not work....

C:\Users\Lucky>ping 192.168.1.1

Pinging 192.168.1.1 with 32 bytes of data:

Request timed out.

Request timed out.

Request timed out.

Ping statistics for 192.168.1.1: (pinging gateway)

    Packets: Sent = 3, Received = 0, Lost = 3 (100% loss),

[ITaaP]

Based on your previous post, Unable to Start VM in ESXi 6.5 your ESXi host is definitely 192.168.1.20. So make sure iLO is NOT set to the same IP address. And what are your network settings on your computer?

[LuckyFabian]

Original ILO4 IP : 192.168.1.25

VMware Server https://192.168.1.20/  <--- I presume this is the IP address I can log onto the VM Server to boot the Win2012 R2 Server via the VSphere Client?

[LuckyFabian]

ok changed the ILO IP to 192.168.1.25 which is was originally

VMware 2012 R2 Server https://192.168.1.20/

Set the default Gateway on the ILO back to 192.168.0.1 and this returns ping.

So currently right now I am pointing the VSphere Client to 192.168.1.20 and cannot connect to it.

I ping 192.168.1.20 and it times out...

[LuckyFabian]

Sorry as I am bloody frustrated here...

[Harishtoy]

Can you share IP details of  your "VMware 2012 R2 Server "

IP =192.168.1.20

Subnet=?

Gateway=?

Are you able to access webclient within the server? if you didn't tried, please do.

[LuckyFabian]

I ping the ILO

Pinging 192.168.1.25 with 32 bytes of data:

Request timed out.

Request timed out.

Request timed out.

Request timed out.

which is what I don't understand, the console reports the ILO is this IP address and it is set as the Network ILO IP address in the IPv4 Summary under the ILO Dedicated Network Port in the web console.

Once it has completed the POST function, the ILO bombs me out. So from here, I should be able to log onto the console of the 2012 VM in the VSphere Client using the IP address 192.168.1.20 which is what I was doing before.

[ragmyn]

Can i assume Windows machine and ESXi server are on same network?

The ping timeouts  are from a Windows machine.  Looks like the Windows machine is on different network.

As you are able to login to ILO and can access the ESXi DCUI, try ping form the invoking ESXi shell from DCUI. Here's the link.

vSphere Documentation Center

RAG

[LuckyFabian]

yes the win VM and the esxi are on the same network...

im trying to ping the ilo and that doesnt respond either.

Not sure how I can access the DCUI, tried hitting F2 after selecting boot to USB stick no joy

[ITaaP]

The network settings are based on your firewall/router. 192.168.1.1 is a fairly standard gateway. Also, you can't use vSphere to log into your iLO. You need to log into the IP address set on the ESXi server. from your first screen shot it almost looks like 192.168.1.28. Hopefully you are not using the same IP address for iLO and the ESXi host.

[ragmyn]

i was presuming that you could able to access the ESXi DCUI based on the screenshot of ESXi DCUI console pasted at the beginning this discussion.

Well.

ESXi shell can be accessible only when you could get in to ESXi console (yellow-grey UI) from ILO.

[LuckyFabian]

Hi Ragmyn,

I get to the DCUI yellow black screen and as soon as the Server reaches POST the ILO cuts me off as I do not have an ILO License.