ForensiT Homepage
Forum Home Forum Home > ForensiT Support > Domain Migration
  New Posts New Posts RSS Feed - Binding to AD Fails - Remote Procedure Call failed
  FAQ FAQ  Forum Search   Events   Register Register  Login Login

Binding to AD Fails - Remote Procedure Call failed

 Post Reply Post Reply
Author
Message
fred3 View Drop Down
Newbie
Newbie
Avatar

Joined: 26 Oct 2019
Status: Offline
Points: 2
Post Options Post Options   Thanks (0) Thanks(0)   Quote fred3 Quote  Post ReplyReply Direct Link To This Post Topic: Binding to AD Fails - Remote Procedure Call failed
    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.
Back to Top
Support View Drop Down
Moderator Group
Moderator Group


Joined: 09 Nov 2006
Location: United Kingdom
Status: Offline
Points: 1844
Post Options Post Options   Thanks (0) Thanks(0)   Quote Support Quote  Post ReplyReply Direct Link To This Post 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
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down

Forum Software by Web Wiz Forums® version 12.03
Copyright ©2001-2019 Web Wiz Ltd.

This page was generated in 0.078 seconds.