Unable to obtain Veeam Agent for Windows license from Veeam backup server

[mohamed.UBX]

Hi,

Veeam agent for windows unable to connect with Veeam Backup server. I'm getting this below error in VAW when I'm trying to connect with local VBR server

"Unable to obtain Veeam Agent for Windows license from Veeam backup server , unable to establish authenticated client-server connection. Authentication failed on remote side"

VBR server version 9.5.0.1536 and VAW version 2.2.0.589. VAW licenses installed on the VBR server. All ports are allowed between VBR and VAW servers and user account has administrator permission to access both servers including repository access.

Any idea what will be the issue?

[HannesK]

Hello,
I'm quite sure that I had that issue in my lab some time ago and it was a DNS issue. Support should be able to figure out the exact reason (please share the case number).

With update 4 / agent 3.0 there were some improvements in this field.

Best regards,
Hannes

[Dima P.]

mohamed.UBX,

Please check that you have at least one repository with agent permissions set to Allow to everyone (or Allow to the following accounts or groups only). Thanks!

[mohamed.UBX]

I have already tried with VBR server name and IP, and repository permission set to allow everyone/groups but still the same error

[Dima P.]

Thanks! Somehow missed the versions from your original post.

VAW 2.2.0.589 is newer that VBR 9.5.0.1536, so the issue might be related to backwards compatibility. It's strongly recommended to use Veeam Agent for Windows 2.2 with Veeam B&R 9.5.0.1922 (Update 3a) or above.

[mohamed.UBX]

Sorry for the delayed response.

I figured that recent windows updates on the Windows server 2008 R2 caused this issue. KB4480970 update was causing issues with SMB network shares and it has been fixed by uninstall the particular update from VBR server.

[Dima P.]

Good to know, thank you for sharing! As I can see Microsoft has shared a hot fix for the mentioned issue, so you can install it on top of KB4480970. Cheers!

[albech]

I am experiencing same issue on Windows 2016. Any recommendations?

[HannesK]

Hello Thomas,
and welcome to the forum.

The recommendation is to ask support for help and post the case number here for reference. It also helps others to post the solution after the case was resolved.

Best regards,
Hannes