Print Page | Close Window

Binding to AD Fails - Remote Procedure Call failed

Printed From: ForensiT
Category: ForensiT Support
Forum Name: Domain Migration
Forum Discription: User Profile Wizard questions, suggestions, comments and bug reports
Printed Date: 12 Jul 2020 at 6:53am

Topic: Binding to AD Fails - Remote Procedure Call failed
Posted By: fred3
Subject: Binding to AD Fails - Remote Procedure Call failed
Date Posted: 26 Oct 2019 at 1:03pm
I've not found much to resolve "The remote procedure call failed and did not execute. Migration Fails."
It appears that DNS is working.
The Domain Controller is identified properly by name.

I'm simply trying to migrate a user profile on a machine that is already domain joined.

Posted By: Support
Date Posted: 28 Oct 2019 at 5:54am
Windows uses DNS to find the addresses of RPC endpoints and Windows Services like Active Directory.

You can test connectivity to the new target domain by running the Microsoft dcdiag tool from the workstation. (This is installed with the Remote Server Administration Tools if you turn on the Active Directory Domain Services Tools feature.)

There is a DNS test (dcdiag /test:DNS) and you can also run tests against a specific DC:

dcdiag /s: domain_controller

Print Page | Close Window