Yes, that's true.
If your kerberos authentication is broken but your NTLM not, your
observation is usual.
This is what I've seen once:
Your client requests a ticket for your server.
If your client gets one it tries to authenticate against your server.
That's the failure case.
If your client requests a ticket for e.g. 192.168.1.1 the Kerberos (AD)
Server responses with an "I've no ticket for this server" response.
Than your client falls back to NTLM.
So in most cases you'll have to look for kerberos problems when you face
this situation.
~ Martin
Aders andersson wrote:
yes of course i´v tried that, i can resolve both FQDN throgh DNS and also
netbios name if i add a ref in hosts file =)
After turn on debug level 10 and using nework mointoring .. it seems like the client is trying to use Kerberos to authenticate when i+m trying to access the share with hostname but NTLM when using IP ??? anyone know why i get this behavior ?
/ Johnny
> _________________________________________________________________
Prova Live.com - din snabba, personliga hemsida med allt du kan önska dig på
ett enda ställe.
http://www.live.com/getstarted--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
