HPE ProLiant iLO: Connection with iLO cannot be established. If you recently made changes to the network configurations, you may need to refresh this page to re-negotiate an SSL connection.

The following error message is shown at the iLO login page and prevents sign in:

Connection with iLO cannot be established. If you recently made changes to the network configurations, you may need to refresh this page to re-negotiate an SSL connection.

To resolve:

1. First clear any cached browser data for the iLO IP address / hostname and try signing in again.

2. Use PuTTY and ssh to the iLO hostname or IP address.

Login as: Administrator

Administrator@ILOHOSTNAME's password: ************

User:Administrator logged-in to ILOHOSTNAME (IP4v Address / IPv6 Address)

iLO Advanced 2.73.

Server Name: HOSTNAME

Server Power: On

</>hpiLO->  

3. Run the command reset /map1 to reset the iLO.

VMware vSphere 6.5: Failed to power on virtual machine. The attempted operation cannot be performed in the current state (Powered off)

After editing a virtual machine to detach an ISO or disconnect the CD-ROM the VM powers off and the following error message is shown when attempting to power on:

Failed to power on virtual machine. The attempted operation cannot be performed in the current state (Powered off).

To resolve:

1. Unregister the virtual machine from the virtual machine inventory list.

2. Re-register the virtual machine by browsing to the datastore and locating the VM configuration file (.vmx) file.

Veeam Backup & Replication 10: Replication job error: permission to perform this operation was denied.

Following an in-place upgrade to Veeam 10 a replication job fails with the error:

Processing VMName Error: Permission to perform this operation was denied.

The job log contains the following entries:

Error    Failed UpdateNetworkAdapter2Vm. VmRef: [vm-9150], Nic: [4000], PortGroup: [Not connected], ConnectAtPowerOn: [False]. (System.Exception)

Error    Fault "NoPermissionFault", detail "<NoPermissionFault xmlns="urn:vim25" xsi:type="NoPermission" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"><object type="Network">network-15280</object><privilegeId>Network.Assign</privilegeId></NoPermissionFault>" (Veeam.Backup.ViSoap.ViServiceFaultException)

Error    VimApi.NoPermission

To resolve:

1. Edit the replication job and enable Network remapping on the first page of the job configuration.

2. Specify the Source and Target networks on the Network page.

QNAP NAS: Restart services

To restart the services running on a QNAP NAS:

1. Using PuTTY ssh to the IP address of the NAS and login using the admin account.

2. Enter the command /etc/init.d/services.sh stop to stop the services.

3. Enter the command /etc/init.d/services.sh start to start the services.

VMware Workstation 15: The network bridge on device VMnet0 is temporarily down because the bridged Ethernet interface is down

The message "The network bridge on device VMnet0 is temporarily down because the bridged Ethernet interface is down" is displayed in VMware Workstation when starting a virtual machine guest with bridged networking configured.

To resolve, first verify that VMware Bridge Protocol is enabled for the network adapter in Control Panel > Network and Internet > Network Connections.

Alternatively, open a command prompt or PowerShell prompt and run the command ncpa.cpl to open the Network Connections window.

The message can also be shown if the VMnet0 network is missing from Virtual Network Editor in VMware Workstation.

Open Virtual Network Editor via Edit > Virtual Network Editor...
Select Change Settings

The default network configuration is:

- VMnet0 : Bridged : Auto-bridging
- VMnet1 : Host-only
- VMnet8 : NAT : NAT

If VMnet0 is missing repair the VMware Workstation installation in Settings > Apps > Apps & features or Control Panel > Programs > Programs and Features.