# No way to get kerberos working. How to troubleshoot ?

**URL:** <https://forum.ansible.com/t/no-way-to-get-kerberos-working-how-to-troubleshoot/36348>\
**Category:** AWX Project\
**Tags:** azure, windows, vmware, awx, ee\
**Created:** [February 21, 2022, 7:28am UTC](https://forum.ansible.com/t/no-way-to-get-kerberos-working-how-to-troubleshoot/36348 "2022-02-21T07:28:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Pierluigi\_Frullani](https://avatars.discourse-cdn.com/v4/letter/p/b19c9b/32.png) [@Pierluigi\_Frullani](https://forum.ansible.com/u/Pierluigi_Frullani)\
**Post date:** [February 21, 2022, 7:28am UTC](https://forum.ansible.com/t/no-way-to-get-kerberos-working-how-to-troubleshoot/36348/1 "2022-02-21T07:28:10Z")

</div>

Hello all,  
I have a 19.2 installation I have inherited and been tasked to make her work.  
I’v managed to get inventories from Azure and vmware working, and so it works for every playbook I run toward linux machines.  
Windows machine are a problem.  
I have created an ee image from the default one ( awx-ee:0.3.0 ) and added krb5.conf and resolv.conf but stil cannot get a valid ticket to make the winping ( or everything else ) works.  
My question is: how can I troubleshoot such problem, being that the ee has no persistent storage nor I can get any logs ( by nature ) ?  
From the awx-ee I have no problem getting a kticket but unfortunally, if I’m not wrong, the docker image that get called is a different one.

Any hint on this ( which seems to be a FAQ, btw ) ?

Thanks in advance.  
Pierluigi

---

<div class="post-metadata">

**Author:** ![Pierluigi\_Frullani](https://avatars.discourse-cdn.com/v4/letter/p/b19c9b/32.png) [@Pierluigi\_Frullani](https://forum.ansible.com/u/Pierluigi_Frullani)\
**Post date:** [February 21, 2022, 1:13pm UTC](https://forum.ansible.com/t/no-way-to-get-kerberos-working-how-to-troubleshoot/36348/2 "2022-02-21T13:13:25Z")

</div>

I’ve found that the problem was in inventory itself.  
vmware inventory has still some problems to me, but if you get the right hostname ( and not the ip address ) kerberos should work.
