Last year, I ran into an issue with B&R v11 when I disabled NTLM in the domain. Turned out v11 can't operate while NTLM is disabled. And v12 should not need NTLM. So this week I upgraded the installation (including Agents) from v11 to v12, disabled NTLM and.... No go. As soon as I disable NTLM (Restrict NTLM: NTLM authentication in this domain: Deny all) the B&R console lists the Agents as Offline in the Physical Infrastructure.
When I check on how to configure Kerberos, there isn't much to configure, except the list of requirement? I guess I'm overlooking something?
-
- Novice
- Posts: 4
- Liked: never
- Joined: Jun 15, 2022 6:39 pm
- Full Name: Simon Weel
- Contact:
-
- Chief Product Officer
- Posts: 31749
- Liked: 7252 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: B&R v12 still needs NTLM?
No, B&R v12 does not need NTLM. This is documented in the What's New in V12 document.
You're correct in that there's nothing to configure on the Veeam side except ensuring you're using FQDN for everything.
If you do and Veeam is still unable to leverage Kerberos, then this could only indicate some issues with your Active Directory domain itself, which is (apparently) unable to serve Kerberos authentication requests and transparently failed over to NTLM before you disabled it.
You're correct in that there's nothing to configure on the Veeam side except ensuring you're using FQDN for everything.
If you do and Veeam is still unable to leverage Kerberos, then this could only indicate some issues with your Active Directory domain itself, which is (apparently) unable to serve Kerberos authentication requests and transparently failed over to NTLM before you disabled it.
-
- Novice
- Posts: 4
- Liked: never
- Joined: Jun 15, 2022 6:39 pm
- Full Name: Simon Weel
- Contact:
Re: B&R v12 still needs NTLM?
Right, FQDN it is. I defined the agents with their NetBIOS name I'll try https://www.veeam.com/kb1905 to correct it
Who is online
Users browsing this forum: No registered users and 22 guests