Standalone backup agent for Microsoft Windows servers and workstations (formerly Veeam Endpoint Backup FREE)
Post Reply
FrancWest
Veteran
Posts: 536
Liked: 111 times
Joined: Sep 17, 2017 3:20 am
Full Name: Franc
Contact:

CBT installation fails.

Post by FrancWest » 1 person likes this post

Hi,

Case #06177255. After the upgrade from Veeam V11 to Veeam V12, the agent backup of the Veeam server itself fails with the following error:

Task failed. Error: Connection problems.

Uninstalling the agent and reinstalling it, fails on the installation the CBT driver. The error reported isL

Failed [vbr] Failed to install Veeam CBT Driver: Connection problems. I’m installing it from the console on the Veeam server itself.

A rescan gives:

Failed Failed to send certificate, but certificate is required for remote agent management Error: Failed to establish connection: no valid IP addresses were found.
HannesK
Product Manager
Posts: 14968
Liked: 3159 times
Joined: Sep 01, 2014 11:46 am
Full Name: Hannes Kasparick
Location: Austria
Contact:

Re: CBT installation fails.

Post by HannesK »

Hello,
as I don't find a question in the thread, I would make the suggestion to continue with support. It's not a well known issue and guessing on that type of problem on a forum makes little sense.

Best regards,
Hannes
FrancWest
Veteran
Posts: 536
Liked: 111 times
Joined: Sep 17, 2017 3:20 am
Full Name: Franc
Contact:

Re: CBT installation fails.

Post by FrancWest » 1 person likes this post

Sorry, I understand, but we found the issue. We had to add the server by IP instead of the FQDN even though the FQDN resolves fine to the correct IP. After doing that, the driver installed fine and the job also runs fine. According to support this has something to do with Kerberos vs NTLM authentication which changed in the latest agent included in V12. When using an IP is uses NTLM, while when using a FQDN it uses Kerberos. The Veeam server is not joined to a domain, so it's still a bit strange why it wants to use Kerberos.
HannesK
Product Manager
Posts: 14968
Liked: 3159 times
Joined: Sep 01, 2014 11:46 am
Full Name: Hannes Kasparick
Location: Austria
Contact:

Re: CBT installation fails.

Post by HannesK » 1 person likes this post

hmm thanks, I agree, that makes no sense. Let me check that.
FCU_JE
Novice
Posts: 6
Liked: 3 times
Joined: Oct 09, 2024 6:17 pm
Contact:

Re: CBT installation fails.

Post by FCU_JE »

I'm necromancing this thread. :) See my saga in the below Veeam post.

https://reddit.com/r/Veeam/comments/1g6 ... etup_help/

This issue/bug in the Veeam code still exists. I tried searching for the source of my problem and almost gave up on getting it to work until I tried one more time and was fortunate enough to find this thread with the solution to my issue (add the device using IP address instead of FQDN).

In my saga above I was doing this for my personal homelab/community edition use case and as such I don't have logs I can (or frankly wish to) submit to Veeam support (not that I'd be entitled to anyway).

I will also apply a word of caution - MS has clearly put out there that NTLMv2 is not in the cards long-term. I'd be surprised if they have little more than a compatibility layer in Windows 12 for it (or maybe enabled via an optional feature like SMBv1 was). Kerberos and LocalKDC is the way of the future. Veeam has to upgrade everything that does authentication to NEGOTIATE at the very least.

HannesK is this feedback/thread something you can triage towards the right dev team/group?
Post Reply

Who is online

Users browsing this forum: No registered users and 16 guests