checking windows credentials error rpc connection failed veeam
Checking windows credentials error rpc connection failed veeam
Настройка veeam backup
Добрый день уважаемые читатели блога pyatilistnik.org, сегодня столкнулся с ошибкой в Veeam: Сервер RPC недоступен. (Исключение из HRESUALT: 0X800706BA). При попытке добавить хост виртуализации Hyper-v. Ранее я рассказывал как настраивается Veeam Backup & Replication 7: 1 часть. Добавление сервера виртуальной инфраструктуры Hyper-V, но как видите бывают и ошибки.
Ошибка в Veeam Сервер RPC недоступен. (Исключение из HRESUALT 0X800706BA)-01
Сама ошибка сразу говорит что либо хоста нету либо firewall лочит попытки подключиться. В моем случае это был второй вариант.
Существует таблица портов от компании veeam для брандмауэра Windows. Вот она поподробнее
Ошибка в Veeam Сервер RPC недоступен. (Исключение из HRESUALT 0X800706BA)-02
Теперь давайте их откроем на нашем брандмауэре. Для этого идем Пуск-Панель управления-Брандмауэр
Ошибка в Veeam Сервер RPC недоступен. (Исключение из HRESUALT 0X800706BA)-03
Ошибка в Veeam Сервер RPC недоступен. (Исключение из HRESUALT 0X800706BA)-04
Нажимаем дополнительные параметры
Ошибка в Veeam Сервер RPC недоступен. (Исключение из HRESUALT 0X800706BA)-5
Нажимаем создать новое правило
Ошибка в Veeam Сервер RPC недоступен. (Исключение из HRESUALT 0X800706BA)-06
Ошибка в Veeam Сервер RPC недоступен. (Исключение из HRESUALT 0X800706BA)-07
И пишем список портов.
Ошибка в Veeam Сервер RPC недоступен. (Исключение из HRESUALT 0X800706BA)-08
Veeam R&D Forums
Technical discussions about Veeam products and related data center technologies
RPC connection fails with local administrator account
RPC connection fails with local administrator account
Post by aj_potc » Apr 11, 2019 4:58 pm this post
I just had an interesting experience and wanted to ask the group for some feedback.
I’m running B&R 9.5 with two Hyper-V guests (all Windows Server 2016). After applying the latest Windows updates, Veeam could no longer connect to one of the two Hyper-V guests via RPC (similar to the error described here: https://www.veeam.com/kb1230).
To fix this, I had to change the credentials being used by Veeam. Instead of using the local Administrator account to connect to the guest system, I had to use the domain Administrator account. This is now the only way to connect to the server’s admin share.
Re: RPC connection fails with local administrator account
Post by Mike Resseler » Apr 12, 2019 5:55 am this post
I believe (but I can be wrong) that a change has been made to the local token policy. Can you check the following:
Key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\System
Value: LocalAccountTokenFilterPolicy
Data: 1 (to disable, 0 enables filtering)
Type: REG_DWORD (32-bit)
That said, to answer your questions:
* Isn’t it better to connect using the local Administator account for backups?
I’m not sure why. With a good design I would think that a domain account (doesn’t have to be a domain administrator) is more secure than a local account
* If my domain controller is down during the backup, won’t this make backups impossible?
Most likely caching will kick in so it can continue with cached credentials for a certain amount of time.
Re: RPC connection fails with local administrator account
Post by aj_potc » Apr 12, 2019 9:11 am this post
Thanks a lot for the reply.
In any case, if you don’t see a problem with using a domain account, then I’ll go with that. I just had the idea that backing up a a local VM from the hypervisor would be using a local account. However, I suppose that’s not true, and there’s no good reason not to use the domain controller for all authentication.
Who is online
Users browsing this forum: No registered users and 7 guests
DISCLAIMER: All feature and release plans are subject to change without notice.
Powered by phpBB® Forum Software © phpBB Limited
Veeam Backup & Replication 8: RPC error:Access is denied Fix
I recently set up a new Veeam Backup & Replication v8 demo lab, and my intial small job that consisted of two different Linux VMs and one Windows Server 2012 R2 Domain Controller was chugging along nicely. I had one minor from the start though, and that was that file indexing consistently failed for the Windows VM. No big deal, but I thought it was strange at the time.
After all, the Linux VMs were indexed just fine.
Fast forward a few days, and all of a sudden Veeam B&R was unable to back up the Windows VM at all, failing with the following error:
Nothing had changed in my environment, no patches had been installed, no changes made to the backup job or the credentials used. I even tried deleting the job, this is a demo environment after all, and re-creating it, but with the same end result.
As the Access is denied message clearly states, this had to be related to permissions somehow, but I was using domain administrator credentials (again, this is a lab), so all the required permissions should be in place, and the credentials test in the backup job also checked out just fine. It has also worked fine for 5 or 6 days, so I was a bit baffled.
In the end, I tried changing from using User Principle Name (UPN) connotation of administrator@domain.local in the credentials for the VM, to using Down-Level Logon Name aka domain\administrator and retried the job.
That did the trick, and it also fixed the indexing problems I’ve had since setting up the job in the first place.
According to this Veeam Community Forum thread this was also a problem in v7 and has something to do with how the Microsoft API’s work.
So, if your Veeam Backup & Replication jobs fail with access denied messages, and/or can’t index the VM files, check your credentials. They may work, but they might just be entered in the wrong format.
«Access is Denied.» when using a local account to add Windows machine to Veeam Backup & Replication
| KB ID: | 4185 |
| Product: | Veeam Agent for Microsoft Windows, Veeam Backup & Replication |
| Published: | 2022-06-23 |
| Last Modified: | 2022-07-30 |
Challenge
While attempting to perform one of the following actions the error «Access is Denied.» occurs:
When rescanning an entire Protection Group the log file for that action can be found here: C:\ProgramData\Veeam\Backup\Rescan\Rescan_of_
Cause
When a Windows Server is added as a Managed Server or added to a Protection Group, Veeam Backup & Replication checks if the Veeam Installer Service (VeeamDeploySvc) is present on the server. If the service is not accessible Veeam Backup & Replication will attempt to connect to the machine via the admin$ share to deploy the service.
The «Access is Denied» error occurs because the user account specified is a local account, and UAC restricts remote access for local accounts.
If this error is encountered while using a Domain account that is a member of the Local Administrators group on the remote Windows machine, please create a Veeam Support case mentioning this article.
Solution
For Veeam Backup & Replication to add a remote Windows machine as a managed server or as part of a Protection Group, the user account used to connect to that remote machine must work with the UAC remote restrictions. The account must be either:
Use Case Examples:
Note: If the Administrator account has been renamed, it can be used as the unique SID that bypasses Remote UAC Restrictions is still valid.
Troubleshooting Guest Processing «Test Now» issues
| KB ID: | 3225 |
| Product: | Veeam Backup & Replication 11, Veeam Backup & Replication 10, Veeam Agent for Microsoft Windows 5.0, Veeam Agent for Microsoft Windows 4.0 |
| Published: | 2020-07-23 |
| Last Modified: | 2022-08-13 |
Challenge
Note: The solutions to RPC and Win32 errors apply to the Credentials Tester when used with vSphere, Hyper-V, and Veeam Agent for Windows. The VIX Connection issues section of this article is related to VMware only.
Regarding Warning in VMware Environments
In VMware environments, Veeam Backup & Replication can use two methods to connect to a guest: RPC or VIX. If RPC is testing successfully, it is generally acceptable for the VIX test to fail as it will not likely be used. However, if it is desired to have VIX succeed, please see the relevant section at the bottom of the solutions section.
Solution
Important notes about the Account shown in the error:
This is not an exhaustive list of potential errors. If you have an error not listed here, please use the «KB Feedback/Suggestion» button at the bottom of this article to notify Veeam Support.
If the error you see is not listed here and you need help, please open a support case.
Testing admin share accessibility via RPC Errors
The following is a few of the possible errors which may be seen in the Guest Credentials Test in the line after «Testing admin share accessibility via RPC»
Right-click on the line item and copy it to the clipboard so that you can paste it somewhere else to see the full error.
Найдите фразы, похожие на 1 Вин Автоматы 1win Ygc ищут:
- 1win Автоматы 1win Ttt
- 1win Casinos Top Casino 1win
- 1 Вин Автоматы 1winbookmaker
- 1 Win Игровые Автоматы 1win Ygc Xyz
- 1 Вин Casino Официальный Сайт Скачать
- Слоты Которые Дают Выиграть 1 Вин
- Игровые Автоматы 1 Вин