The server using version 4.1 has the exact same problem, while the server using version 5.0 used to have it. We have three other vSphere servers using version 4.1, 5.0 and 5.5. I’ve seen this exact problem several times before, and according to the Internet I’m not alone. The error message using the checkbox is “A general system error occurred: gss_acquire_cred failed”. The authentication between the vSphere Server and the AD is obviously working, but the automation of it isn’t.
![untangle firewall manually set ntp server in ntp.conf untangle firewall manually set ntp server in ntp.conf](https://passportbdd.ru/uploads/4285e499741728a3b249b241c2fc2f99.jpg)
Untangle firewall manually set ntp server in ntp.conf windows#
At first everything worked perfectly, but after a host restart I had to enter my domain credentials manually in vSphere Client instead of using the checkbox Use Windows session credentials. I joined the server to our Windows domain to be able to manage permissions using our AD and to enable SSO for our users.
![untangle firewall manually set ntp server in ntp.conf untangle firewall manually set ntp server in ntp.conf](https://3.bp.blogspot.com/-x1E7gaiSkKE/TsOvRWf4TdI/AAAAAAAAAbg/Qv-gJrcInAE/s1600/ntpdiagram.png)
As last time, I used HP’s customized version. Last week, when 6.0 was released, I decided to give the new version a try. Everything was working flawlessly, and I was just waiting for some disks before starting to use the server in our production environment.
![untangle firewall manually set ntp server in ntp.conf untangle firewall manually set ntp server in ntp.conf](https://techprojournal.com/wp-content/uploads/2020/08/ng-firewall-laptop-300x155.jpg)
A couple of weeks ago I installed a fresh vSphere 5.5 U2 from HP on a completely new HP ProLiant D元80 Gen9 without any problems.