I’ve had several issues when I could not connect to vmWare ESXi. The vSphere Client only reported connection failure. The server was running as it should and none of the virtual mashines was affected by this, only the login.
Since the server is hosted in a remote location there has been no other way of fixing it than to do a hardware reboot. Not the nicest way of solving it.
But since it happen regulary, I’ve turned the SSH as default. So I had one way in to the server when this happen. And there was no problem to log in with a SSH client.
I’ve tried to find a way to reset the service that vSphere Client connected to, but could not find anything. Some posts at the VMware site suggested that some processes should be restarted, but that was no luck. One suggestion was even that there was a problem with the local network, didn’t even try that.
After a while I gave up and decided to reboot the whole vmWare host with shutdown -r now. But in the vmWare host I could not find the shutdown command. Instead there was a shutdown.sh in the bin (sbin) folder.
Maybe there was some clues in the shutdown.sh script.? It sure was! One of the lines in shutdown.sh was /sbin/services.sh stop. I just had to try and do a restart instead of a stop on that script. My backup plan was that if anything went terribly wrong, I would have to call the off site and have them do a physical power down on the server.
And it turned out a success! After the script had finished there was no problem at all to log in with the vSphere Client. None of the virtual mashines was affected and none of the web site neither.
After automatic update of Windows 10 build 9926 of Windows 10 I could no longer acces the new Synology Diskstation.
“\\share is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.
The account is not authorized to login from this station”
After lots of searching on the net it turned out that Microsoft has increased the security in this new build. And it seems that there is only a registry hack to let build 9926 connect like any other versions of Windows.
You have to add:
AllowInsecureGuestAuth (DWORD 32-bit) and set it to 1
That would let me connect as the guest account on my Synology Diskstation again.
Yesterday I did a clean install of Windows XP Professional SP3 on a virtual machine for testing. First thing after installing is running Windows Update.
But the Windows Update web page did not load properly and only showed the error “The website has encountered a problem and cannot display the page you are trying to view. The options provided below might help you solve the problem.”. Of course, none of the options provided did say anything about this problem. The only help was an error code “Error number: 0x8024D001” up in the right corner of the page.
To solve this I had to make Windows XP download and install the first updates without using the web page, by installing it from the notification area.
Fist I had to make sure Windows Update was set to check for new updates automatically. This is selected in Automatic Updates in Control Panel.
To get Windows Update to check for updates quicker i started a command prompt and typed:
That made the notification balloon with “Updates are ready for your computer.” popup after less than a minute. This made it possible to install the first update without using the web page.
When that was done, and the computer was rebooted once (or twice) the Windows Update web page worked again. And then that Windows Update wanted to install the “Windows Genuine Advantage Validation Tool” (which for some reason took several minutes to find), and after that there was the rest of the 123 updates…
When installing VMware.
You will get the error “Service VMware Authorization Service (VMAuthdService) failed to start.” when installing VMware (I’ve tried Player and Workstation) and have Avast installed.
Disabling Avast will not do any difference. Uninstalling Avast will work, but there is an easier solution.
In Avast click Settings and then Troubleshooting. There uncheck “Enable hardware-assisted virtualization”. After that you have to reboot your computer.