Processing COMPUTERNAME.DOMAIN.DOMAIN Error: Host is unreachable

[Porfavor]

Hello,

I have setup Backup & Replication Community Edition and added a domain group to which I added one client machine.

When testing the credentials ("Guest credentials test") it tells me that the host is unreachable and the credentials are incorrect.

I have used the server's and domain's administrator by adding the user account while creating the AD group in Veeam. Logging in to the client's Windows OS with these credentials works without issues.

Errors are:

"Processing COMPUTERNAME.DOMAIN.DOMAIN Error: Host is unreachable"

and

"Checking Windows credentials error: RPC connection failed"

Client's firewall is disabled. Might be the router firewall a problem?

I have no idea what I can do.

Could you provide any help on this?

Thank you in advance.

Case-ID: 03832552

[Gostev]

Hello, you should check for DNS issues as well. Thanks!

[Porfavor]

Hello,

thank you for your reply.

What I tried, as well, is to add a new group of computers (not domain) and add the client with its IP. I also disabled the client and the server firewalls. That brought up the same error.

I am also able to access admin$-share with these credentials.

Any ideas?

[Porfavor]

I found out by myself. I had to disable UAC at the client. I don't feel comfortable with that, though.

Is that an expected behaviour?

[Dima P.]

Hello Porfavor,

Sorry for the delay - was checking this issue with our QA department. We were unable to reproduce the mentioned behavior and can confirm that enabled UAC should not affect agent installation. If you can confirm that this issue still persists please rely back to your support engineer (I've asked them to reopen the support case). Thank you in advance!

[scottmlew]

Was there a resolution on this? I'm seeing the same issue on B&R 10. I currently have the host firewall completely disabled on the machine that will be receiving the agent. I've tried by domain name and by IP, with the same results.

[Mildur]

If you want to deploy veeam Agent to „non domain joined“-computers with your Veeam VBR Server, you need to create the following registry key. After that, veeam can connect to the admin share.
Before that, it‘s not possible because of windows system restrictions.

Code: Select all

 
 
1. Open the Registry Editor (regedit.exe)

2. Go to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System

3. Create a new DWORD (32-bit) parameter with the name
   LocalAccountTokenFilterPolicy
4. Specify the LocalAccountTokenFilterPolicy parameter value equal to 1

5. Reboot Workstation

http://woshub.com/enable-remote-access- ... workgroup/

[scottmlew]

If you want to deploy veeam Agent to „non domain joined“-computers with your Veeam VBR Server, you need to create the following registry key. After that, veeam can connect to the admin share.

OMG, I feel so silly now. Thank you so much...yes, this is the exact solution. For anyone reading this, you also need to make sure the File and Printer Sharing (SMB-In) rule allows access...by default, on a "Private" connection, it allows only local subnet access.

Of course, now that I can connect, I am having other issues but I haven't started to diagnose those yet.

[Dima P.]

Hi folks,

Thanks for sharing the solution and for confirming that it works in your environment!

[Mildur]

Happy to help