https://login.veeam.com/en/oauth?client_id=nXojRrypJ8&redirect_uri=https%3A%2F%2Fwww.veeam.com%2Fservices%2Fauthentication%2Fredirect_url&response_type=code&scope=profile&state=eyJmaW5hbFJlZGlyZWN0TG9jYXRpb24iOiJodHRwczovL3d3dy52ZWVhbS5jb20va2IyMzMyIiwiaGFzaCI6ImI1MTRjOTc5LTkxNmEtNGIxNy1iM2IyLTAzZDI4OGJiZjE1ZSJ9
1-800-691-1991 | 9am - 8pm ET
EN

Configuring Veeam Agent for Microsoft Windows on servers with Microsoft DirectAccess enabled

Challenge

The backup job ​on Microsoft Windows Server OS with DirectAccess server enabled fails with the following error message:
 
Error: The remote procedure call failed and did not execute RPC function call failed. Function name: [GetSvcVersion]. Target machine: [xxx.xxx.xxx.xxx]

Cause

Microsoft DirectAccess locks ports 6000-47000. You can use the following PowerShell command to verify this:
 
Get-NetNatTransitionConfiguration

Solution

Change the custom port for RPC_transport to any idle port, which is outside the 6000-47000 range by editing the following registry key:
 
HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Endpoint Backup\EndPoint_Rpc_Transport_Port
KB ID:
2332
Product:
Veeam Agent for Microsoft Windows
Version:
2.x
Published:
2017-09-07
Last Modified:
2020-08-13
Please rate how helpful this article was to you:
5 out of 5 based on 1 ratings
Thank you for helping us improve!
An error occurred during voting. Please try again later.

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

Knowledge base content request
By submitting, you agree that your personal data will be managed by Veeam in accordance with the Privacy Policy.

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please go back try again later.